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

Feature request: allow undeclared test outputs to be collected unzipped #16024

Closed
paullewis opened this issue Aug 2, 2022 · 2 comments
Closed
Assignees
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) team-Local-Exec Issues and PRs for the Execution (Local) team type: feature request

Comments

@paullewis
Copy link

Description of the feature request:

I currently have some test runners that output XML reports, which can be collected in TEST_UNDECLARED_OUTPUTS_DIR. However these files are always zipped as per https://github.com/bazelbuild/bazel/blob/master/tools/test/test-setup.sh#L409-L419

I was wondering if it would be possible to add a flag/option that bypasses the zipping process and instead puts the files as-is in the testlogs dir where the outputs.zip file would have been?

What underlying problem are you trying to solve with this feature?

I don't always want the unspecified test outputs to be zipped to outputs.zip as I end up having to unzip them again to do further processing on their contents.

Which operating system are you running Bazel on?

Mac

What is the output of bazel info release?

release 5.2.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

N/A

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

9c00adcf27f75cb9d606c3d90fc0b0307830b952

Have you found anything relevant by searching the web?

A few items, but all the stuff I found assumes that there will always be an outputs.zip (which tallies with how I read the Bazel source).

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

N/A

@sgowroji sgowroji added type: feature request untriaged team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website team-Local-Exec Issues and PRs for the Execution (Local) team and removed team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website labels Aug 2, 2022
@wilwell wilwell self-assigned this Aug 9, 2022
@wilwell wilwell added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) and removed untriaged labels Aug 9, 2022
@benjaminp
Copy link
Collaborator

#14568

@paullewis
Copy link
Author

Woo! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) team-Local-Exec Issues and PRs for the Execution (Local) team type: feature request
Projects
None yet
Development

No branches or pull requests

4 participants