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
Testament has a timeout property in test specs, but it's only checked after the process is done. It doesn't terminate the test process early if it passes the timeout duration.
The process is created in callNimCompiler but I could not get it to work with waitForExit. Test code that just does sleep(100_000) is not treated as timed out on Windows either by waitForSingleObject or getExitCodeProcess, which gives an exit code of 0 after 1.2 seconds. It would be better than the current situation if it at least worked on other OSes but I don't know if it would.
I was hoping to add a default 5 minute timeout for every test, in #24252 I accidentally wrote an infinite loop in the compiler and it didn't show which test failed because it ran indefinitely and the entire CI was cancelled.
The text was updated successfully, but these errors were encountered:
Testament has a
timeout
property in test specs, but it's only checked after the process is done. It doesn't terminate the test process early if it passes the timeout duration.The process is created in
callNimCompiler
but I could not get it to work withwaitForExit
. Test code that just doessleep(100_000)
is not treated as timed out on Windows either bywaitForSingleObject
orgetExitCodeProcess
, which gives an exit code of 0 after 1.2 seconds. It would be better than the current situation if it at least worked on other OSes but I don't know if it would.I was hoping to add a default 5 minute timeout for every test, in #24252 I accidentally wrote an infinite loop in the compiler and it didn't show which test failed because it ran indefinitely and the entire CI was cancelled.
The text was updated successfully, but these errors were encountered: