-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Don't mask error in cquery
transitions output formatter
#23210
Conversation
All errors used to be wrapped in an `InterruptedException` instead of being reported with a message. Also show a warning when an incompatible target is skipped instead of failing the build.
@keith @illicitonion Do you think this handling of incompatible targets is reasonable? |
|
||
options.transitions = Transitions.LITE; | ||
AnalysisProtosV2.CqueryResult cqueryResult = | ||
getProtoOutput("deps(//test:my_target)", AnalysisProtosV2.CqueryResult.parser()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume getProtoOutput
before would trigger the InterruptedException
that auto-failed this test? Could we, just for clarity, add a line verifying the result isn't null and/or checking the warning message?
Also, what are you distinctly testing here compared to the shell test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was just a leftover from an earlier attempt at a Java test that ultimately failed. I removed it.
tested and it seems to work for our case, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very reasonable - thanks!
@bazel-io fork 7.4.0 |
All errors used to be wrapped in an `InterruptedException` instead of being reported with a message. Also show a warning when an incompatible target is skipped instead of failing the build. Work towards bazelbuild#21010 Closes bazelbuild#23210. PiperOrigin-RevId: 660116656 Change-Id: I22651110984e471a6b31dcc59a387f3f85ad49bc
…3351) All errors used to be wrapped in an `InterruptedException` instead of being reported with a message. Also show a warning when an incompatible target is skipped instead of failing the build. Work towards #21010 Closes #23210. PiperOrigin-RevId: 660116656 Change-Id: I22651110984e471a6b31dcc59a387f3f85ad49bc 300c586 Co-authored-by: Fabian Meumertzheim <[email protected]>
The changes in this PR have been included in Bazel 7.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
All errors used to be wrapped in an
InterruptedException
instead of being reported with a message. Also show a warning when an incompatible target is skipped instead of failing the build.Work towards #21010