Repository navigation
Conversation
Move logging into common.py Fix lint issues Update expected action number (since we added an extra parse action) Undo changes to codechecker script
Move logging into common.py Fix lint issues Update expected action number (since we added an extra parse action) Undo changes to codechecker script
furtib
force-pushed
the
parse-in-bazel-testlog
branch
from
October 9, 2026 07:11
e9e5f4c to
74c7999
Compare
nettle
reviewed
Oct 9, 2026
nettle
left a comment
nettle
left a comment
Collaborator
There was a problem hiding this comment.
Hi @furtib, @Szelethus,
May I beg you stop submitting such radical changes without verifying usage compatibility in real projects? I'm afraid you may already broke output format for our major users...
Contributor
Author
|
Okay, let's slow down a bit. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why:
Users want to access the parsed results after the test runs.
Exposing the parsed results under
bazel-testlogsmakes sure that these files are always downloaded from the remote cache.What:
bazel-testlogs.Addresses:
Fixes: #237
Depends on: #315