-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
java_test does not report about skipped tests #6688
Comments
cc: @hmemcpy |
I just parachuted into this, but it looks like we are explicitly not writing the @cushon , is this the correct diagnosis? |
Maybe, I'm not very familiar with this code. There's some related discussion about test reporting here: #3201 |
Reading some of these discussions and seeing that updates were made however none were to generate the Would that be accepted? |
@or-shachar I haven't started on it yet because we decided that we didn't really care about this until there can be changes made to our internal CI that can alert us when a certain percentage of tests suddenly start being skipped. (this was inspired by a configuration mistake we made outside of Bazel that caused a bunch of tests to be skipped). |
Fixes bazelbuild#6688 (after java tools release)
Fixes bazelbuild#6688 (after java tools release)
Fixes bazelbuild#6688 (after java tools release)
Fixes bazelbuild#6688 (after java tools release)
Fixes bazelbuild#6688 (after java tools release)
Fixes bazelbuild/bazel#6688 (after java tools release) Closes #13717. PiperOrigin-RevId: 385953369
Problem:
When running bazel
java_test
target with junit test with annotation@Ignore
- the test doesn't show up in the resultingtest.xml
Report:
Simple test class:
Running with
java_test
target.I made a repro here:
result will show
(The skipped
testcase
is listed with time 0 and is not counted asskipped
)OTH if you run mvn clean install you'd get:
(the skipped
testcase
is marked withskipped
and is counted asskipped
)OS I tested on:
OS X and Linux
Releases:
release 0.19.1
release 0.18.1
Additional info
The bug propagates to rules_scala Specs2Junit test runner (cc: @ittaiz )
The text was updated successfully, but these errors were encountered: