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
{{ message }}
Repository navigation
Don’t show traceback on 'breeze tests' subprocess returning non-zero #23868
Currently, if any tests fail when breeze tests is run, Breeze 2 would emit a traceback pointing to the docker-compose subprocess call. This is due to Docker propagating the exit call of the underlying pytest subprocess. While it is technically correct to emit an exception, the traceback is useless in this context, and only clutters output. It may be a good idea to add a special case for this and suppress the exception.
A similar situation can be observed with breeze shell if you run exit 1 in the shell.
Committer
I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Activity
Avoid printing exception when exiting tests command
potiuk commentedon May 24, 2022
Yep. Most of the commands had it already. Also I tihnk
shellhas it already (but maybe there is another case):potiuk commentedon May 24, 2022
Fix in #23897
Avoid printing exception when exiting tests command (#23897)
Avoid printing exception when exiting tests command (#23897)
pull master (#25)