Closed CampGareth closed 6 years ago
Tested on timed-out sims, works there, should work everywhere else due to being added to the base job
. All dependencies are merged, so this is ready to merge
whats a good way to test this?
I've been using simulations with an infinite loop somewhere in them. e.g. in the addition example:
// Print the value we got from the FPGA
for {
fmt.Printf("%d\n", ret)
}
Run a simulation of it and wait (1 hour timeout for simulations), then run reco test list
This has been giving me output like this:
421a623c-bc7b-4829-8f1c-44294f533ac8 timed-out 3 days ago 1h0m11s
0cbe0195-4c7e-47d0-8e3a-4cbe7b3d8cb1 completed 3 days ago 18m43s
84b291cf-3a38-4b0d-9afc-6cb1708feef2 timed-out 3 days ago 1h0m31s
This should cause builds to show status
timeout
instead oferror
when a timeout has occurred. It does this by looking at thecode
field of the events of a job.