We have noticed that - for newly uploaded patch sets -the same build might get aborted multiple times. We assume that each build is aborted n times if the corresponding changeset has triggered n builds

The second/third/... abortion may unfortunately act on an exit handler triggered by the initial (correct) abortion, cancelling the exit handler itself.

In our case, this issue results in severe resource leakage, because essential teardown actions cannot run.

This issue seemed to have have been solved by PR#361, unfortunately we are experiencing it yet again.

An exemplary log might look like this:

15:21:14  Aborted by new patch set.
15:21:14  Aborted by new patch set.
15:21:14  [Pipeline] // node
15:21:14  Aborted by new patch set.
15:21:14  [Pipeline] nodesByLabel
15:21:14  Found a total of 1 nodes with the '...' label
15:21:14  Aborted by new patch set.
15:21:14  [Pipeline] node
15:21:14  Aborted by new patch set.
15:21:14  Running on ... in /.../...
15:21:14  [Pipeline] // node
15:21:14  Aborted by new patch set.
15:21:14  Aborted by new patch set.
15:21:14  Aborted by new patch set.