Closed fenchu closed 1 year ago
If you don't want the stacktrace, why use pytest-timeout? The entire reason it exists is to get stacktraces.
for me it is to timeout before gitlab kills the pod. so the pipeline can perform its logging and cleanup stages. but I can write my own plugin
do you not want to know what the state of the test was at the time of the timeout? how do you debug this failure case?
I just want to run an exit command before the container is hard deleted. There is another challenge. the report.xml is not finished. this is what our quality system needs.
I use timeout on tests running in ci-runner containers, so they timeout and create reports just before the runners timeout and kill everything. Works fine, but how Do I get rid of the stacktrace?
pytest -s --capture=tee-sys --log-cli-level=INFO --durations=0 --tb=short --junitxml=report.xml .\tests\