Closed mlarraz closed 1 year ago
Just glanced over. I don't quite get the spec change. Is it indicative that --backtrace
will be respected now?
Just glanced over. I don't quite get the spec change. Is it indicative that
--backtrace
will be respected now?
This PR changes the order of the "examples"
key in the output. Failures will always be last now since the code is iterating through them after the non-failures.
The spec relied implicitly on the order, so I changed it to instead look for the first failure, and re-arranged the expected output.
If for some reason ordering is really important here, I can try to find a way to make the same change while preserving it.
Ordering is not that important as "respect the --backtrace flag" is. A spec that would assure in this is.
I think these failures are unrelated to my changes, as I can reproduce them in a new branch cut directly from main
Thank you, I fixed an issue with the build elsewhere to get this green.
Released in 3.13.0, apologies it has taken so long.
Currently the JSON formatter does not respect the
--backtrace
flag (it will always print the full backtrace).I believe this should behave the same as other formatters and respect the config.