Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--test_filter and --test_output flags cannot both be used at the same with with bazel test. #11529

Closed
collinbarnwell opened this issue Jun 1, 2020 · 2 comments
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request

Comments

@collinbarnwell
Copy link

collinbarnwell commented Jun 1, 2020

#5640 # Description of the problem / feature request:

--test_filter and --test_output flags cannot both be used at the same with with bazel test.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

This command outputs relevant test logs:
bazel test :file_test --test_output=errors

This command allows me to only run a few tests in a given file:
bazel test :file_test --test_filter=OpenFileTest

When I use both together, the test filter does not work, and I get output for all tests in the file.

bazel test :file_test --test_filter=OpenFileTest --test_output=errors

What operating system are you running Bazel on?

Linux

What's the output of bazel info release?

release 0.27.0

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

N/A

Have you found anything relevant by searching the web?

No

Any other information, logs, or outputs that you want to share?

None

@aiuto aiuto added the P3 We're not considering working on this, but happy to review a PR. (No assignee) label Jun 4, 2020
@sventiffe sventiffe added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request labels Feb 10, 2021
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Apr 26, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request
Projects
None yet
Development

No branches or pull requests

3 participants