-
Notifications
You must be signed in to change notification settings - Fork 0
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
Address how and where we end the AsynchronousExecution #3
Address how and where we end the AsynchronousExecution #3
Conversation
As an amendment to jenkinsci#27. |
Precisely. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very close to what I had initially, and it does not work, as explained in 18d78f3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK. Do tests pass with this?
} | ||
} else if (execution == null) { | ||
} else if (execution == null && completed != Boolean.TRUE) { | ||
needsToPersist = true; // Make sure we save toggled state |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really related to changes in JEP-210, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not as such, but more correcting for some issues in the logic.
@@ -580,6 +596,7 @@ private void finish(@Nonnull Result r, @CheckForNull Throwable t) { | |||
setResult(r); | |||
completed = Boolean.TRUE; | |||
duration = Math.max(0, System.currentTimeMillis() - getStartTimeInMillis()); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could revert
Passes for me, with some flakes such as
from r.waitForCompletion(b);
assertFalse(b.executionLoaded); // here which I suspect are due to a race condition between |
@jglick Still sorting out some test oddities |
Still getting some flakes:
and
|
…gered CI-only failures
For whatever reason, what should be a trivial fix is not, and oddly the original does not trigger failures (CI only for me, see to be locally irreproducible), so... I guess we roll with it. |
Corrects for cases where the AsynchronousExecution could be left dangling inadvertently.