-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testament: timeout
doesn't work: it waits for process to complete
#17407
Labels
Comments
this is not just about here's another example:
if a test is buggy and never returns, testament will just wait for it until CI times out. the fix is to cap each test with a (customizable) timeout |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example
Current Output
doesn't terminate
Expected Output
fail with
reTimeout
after specified timeout (0.1 seconds)Possible Solution
the current implementation is naive: it calls
execCmdEx2
and waits for process to complete (and only then compares test duration to timeout), but instead should use a timeout and abort process when timeout expires. Side note:epochTime
is used, but this is incorrect, see #17405.This could explains why CI sometimes times out after 90 minutes due.
Additional Information
1.5.1 b8b67ad
EDIT: added medium priority; this bug potentially explains cryptic errors of the form:
in CI eg https://dev.azure.com/nim-lang/Nim/_build/results?buildId=14599&view=logs&jobId=a0440cd6-2060-5545-8b53-639e777de0c6&j=a0440cd6-2060-5545-8b53-639e777de0c6&t=e8126762-32e4-52a6-97de-95cf0bedbe3d
TODO
The text was updated successfully, but these errors were encountered: