Skip to content

Fix the warning test by checking stderr#30997

Merged
liyuqian merged 1 commit intoflutter:masterfrom
liyuqian:fix_warning_test
Apr 15, 2019
Merged

Fix the warning test by checking stderr#30997
liyuqian merged 1 commit intoflutter:masterfrom
liyuqian:fix_warning_test

Conversation

@liyuqian
Copy link
Contributor

Description

Previously, I used the Android emulator for testing and everything
seemed to work fine with stdout (if I remember correctly). But our
devicelab uses real Android devices and the warnings are routed to
stderr. Hence change stdout to stderr in the test.

Related Issues

#30625

Tests

drive_perf_debug_warning devicelab test

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I signed the CLA.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I updated/added relevant documentation (doc comments with ///).
  • All existing and new tests are passing.
  • The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flutter developers to manually update their apps to accommodate your change?

  • Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
  • No, this is not a breaking change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will be out, so don't let this hold too much up - but would it be worth just getting both stdout and stderr, concatenating them (perhaps with a dividing message) and returning that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't do that because I'm afraid of breaking all the existing tests that may rely on matching the full stdout...

Copy link
Contributor

@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Previously, I used the Android emulator for testing and everything
seemed to work fine with stdout (if I remember correctly). But our
devicelab uses real Android devices and the warnings are routed to
stderr. Hence change stdout to stderr in the test.
@liyuqian liyuqian merged commit b0937a1 into flutter:master Apr 15, 2019
@liyuqian liyuqian deleted the fix_warning_test branch April 18, 2019 21:10
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants