Skip to content

Eliminate checkpoint at the end of tests in Jenkins #165

@joaocgreis

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?

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