-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Change Bazel XML support to depend upon BAZEL_TEST #2459
Conversation
856080f
to
1db5fd5
Compare
Codecov Report
@@ Coverage Diff @@
## devel #2459 +/- ##
==========================================
+ Coverage 91.53% 91.67% +0.14%
==========================================
Files 159 159
Lines 7512 7435 -77
==========================================
- Hits 6876 6816 -60
+ Misses 636 619 -17 |
Thanks, but the old approach should be kept around for backwards compatibility, until next release that breaks backcompat. This means that Catch2 should check the environment variable for path to write the JUnit XML report to if either it was compiled with You should then add a deprecation notice to the description of |
Understood, I think these are fair points. I will make the changes and update the PR. Thanks for taking a look. |
9e55cc0
to
b0ad5c3
Compare
eed01db
to
8db7c2a
Compare
8db7c2a
to
ceddb58
Compare
looks good now, thanks. |
Relating to the original issue #2399 here;
Bazel has now been updated to have a cleaner environment variable for catch2 to know when to output to JUnit XML.
Seen here: bazelbuild/bazel#15393
Instead of relying on
CATCH_CONFIG_BAZEL_SUPPORT
we can now inspect the environment variableBAZEL_TEST
. This is better as it allows for 'native' detection of both JUnit XML and Bazel. Originally not done as the detection mechanism was using too generic of a environment name.