You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using doctest with JUnit reports in our pipeline and if something goes wrong, then sometimes it's helpful to see the contexts of the failure as well.
I have extended JUnitReporter with log_contexts in my fork, based on the similar functionality of ConsoleReporter - please feel free to accept the pull request.
example failure with contexts:
<failuremessage="1 != 1"type="CHECK">
logging.cpp(0):
CHECK( vec[i] != (1 << i) ) is NOT correct!
values: CHECK( 1 != 1 )
logged: current iteration of loop:
i := 0
</failure>
The text was updated successfully, but these errors were encountered:
Description
We are using doctest with JUnit reports in our pipeline and if something goes wrong, then sometimes it's helpful to see the contexts of the failure as well.
I have extended
JUnitReporter
withlog_contexts
in my fork, based on the similar functionality ofConsoleReporter
- please feel free to accept the pull request.example failure with contexts:
The text was updated successfully, but these errors were encountered: