ci: publish the bazel test logs #476
Merged
Conversation
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
|
do we always want the test logs or only on failure? |
moritzkiefer-da
approved these changes
Apr 15, 2019
|
I don't think anyone cares if they succeeded. What's the cost of doing it always though? In terms of cash/time or whatever. |
|
@neil-da it adds another 57s to the build |
ghost
force-pushed
the
ci-bazel-testlogs
branch
from
1d40a66 to
521fa12
Compare
|
changed it to only publish on failure |
As a developer I want to be able to inspect the detailed test logs when those are failing.
ghost
force-pushed
the
ci-bazel-testlogs
branch
from
521fa12 to
0dee48a
Compare
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a developer I want to be able to inspect the detailed test logs when those are
failing.
Pull Request Checklist
NOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines runtotrigger the build.