Open philou opened 2 weeks ago
I'm assuming this is not python-specific, as same behaviour should occur with any toolchain as long as the build or the test commands enter an infinite loop (TCR is currently assuming that these commands will eventually come to an end).
The concern I'm having with using a timeout is that this depends on many factors (speed of the machine running TCR, size of the code to be built, number of tests, speed of tests, etc.). Another option could be to provide users with an "abort" shortcut, that would allow them to interrupt a TCR cycle if they observe that it's taking too long. WDYT?
I confirm that this behaviour can be observed with any language/toolchain as soon as there is an infinite loop somewhere while the tests are running
Contact Details
No response
Describe the bug
Whenever the python code gets into an infinite loop in the test, TCR stays there and we have no choice but to kill and restart it.
To Reproduce
Steps to reproduce the behavior:
while
loop in a testExpected behavior
I would expect that TCR would kill the tests after a timeout period
Working Environment
Additional Context
Additional information
Code of Conduct