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
Currently all of the content is printed to stdout, including the final list of failing cases. This causes some issues with other tooling like meson, in which we might want to run lizard as a build target, like...
If we have any failures, lizard will exit with a non-zero code, which meson then uses to break the build. meson will then print out the stderr contents to help the user diagnose what went wrong, but in this case that's empty. It would be convenient to pass in an option which causes the final failures summary to be printed to stderr instead, so that cases like the above would integrate nicely.
The text was updated successfully, but these errors were encountered:
Currently all of the content is printed to stdout, including the final list of failing cases. This causes some issues with other tooling like
meson
, in which we might want to run lizard as a build target, like...If we have any failures,
lizard
will exit with a non-zero code, whichmeson
then uses to break the build.meson
will then print out thestderr
contents to help the user diagnose what went wrong, but in this case that's empty. It would be convenient to pass in an option which causes the final failures summary to be printed tostderr
instead, so that cases like the above would integrate nicely.The text was updated successfully, but these errors were encountered: