Skip to content

Eliminate checkpoint at the end of tests in Jenkins #165

Closed

Description

@joaocgreis

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,

  1. Is this the only reason for this checkpoint?
  2. Is it consensual that this is useless for our use case?
  3. Is there a way to eliminate it?

Activity

  1. orangemocha commented on Aug 24, 2015

    @orangemocha

    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.

  2. orangemocha commented on Aug 28, 2015

    @orangemocha

    It looks like we are going to have to modify the TAP plugin: https://issues.jenkins-ci.org/browse/JENKINS-29650

  3. orangemocha commented on Aug 28, 2015

    @orangemocha
  4. jbergstroem commented on Aug 31, 2015

    @jbergstroem
    Member

    @orangemocha how do you suggest we proceed here? Doesn't look like upstream jenkins/tap plugin is moving forward anytime soon.

  5. orangemocha commented on Aug 31, 2015

    @orangemocha
  6. Trott commented on Oct 24, 2016

    @Trott
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions