-
-
Notifications
You must be signed in to change notification settings - Fork 171
Closed
Labels
Description
After running all the tests, Jenkins test jobs block until the previous job is complete. As seen on the output of job 277:
Publish TAP Results is waiting for a checkpoint on node-test-commit-arm » pi1-raspbian-wheezy #276
It this case, a previous job (273) was compiling and for some reason ccache did not seem to help. It took 9h35m, and jobs started afterwards had to wait for it to finish before they could publish the results.
I don't know why this checkpoint is there, the only reason I can think of is to display the comparison in the TAP output, such as TAP Test Results (2 failures / +2)
.
So,
- Is this the only reason for this checkpoint?
- Is it consensual that this is useless for our use case?
- Is there a way to eliminate it?