-
Notifications
You must be signed in to change notification settings - Fork 166
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
Eliminate checkpoint at the end of tests in Jenkins #165
Comments
For things like our jobs that test and land pull requests, it's certainly useless. Computing the delta in failures between different PRs, and across multiple branches doesn't add a lot of value. The failure delta might make more sense in more traditional type of CI jobs that run periodically on the same branch. In that category we currently have only node-daily-master. But if the side effect is that a job needs to block on other runs just to report the results, I am definitely in favor of removing that feature. |
It looks like we are going to have to modify the TAP plugin: https://issues.jenkins-ci.org/browse/JENKINS-29650 |
Also relevant: https://issues.jenkins-ci.org/browse/JENKINS-9913 |
@orangemocha how do you suggest we proceed here? Doesn't look like upstream jenkins/tap plugin is moving forward anytime soon. |
|
Closing as this has been inactive for over a year and I believe we intend to move off the TAP plugin. Feel free to re-open or comment if I am mistaken to close this. |
After running all the tests, Jenkins test jobs block until the previous job is complete. As seen on the output of job 277:
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,
The text was updated successfully, but these errors were encountered: