-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Summary: Similarly to the check-contents test, the coverage test was also using `2>&1` to record stderr. This is dangerous, since status messages can show up on stderr. Looking more into `flow coverage`, it's actually doing some silly things: 1. Not properly respecting `--quiet` 2. Exiting with exit code 0 on `--json --color` or `--json --debug` 3. Only checking for invalid flag combinations after connecting to the server 4. Not documenting which flags can't be used together. Reviewed By: mroch Differential Revision: D6277951 fbshipit-source-id: 1f97c76d2bdc358cbe3dafc068cc1e4b3aeab0db
- Loading branch information
1 parent
4360d49
commit f6ae791
Showing
3 changed files
with
41 additions
and
41 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters