Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: 53b5e90aa60cebc7d2910b863ab1147ccff8f72e
https://github.com/jenkinsci/jenkins/commit/53b5e90aa60cebc7d2910b863ab1147ccff8f72e
Author: Scott K Logan <log...@cottsay.net>
Date: 2024-05-10 (Fri, 10 May 2024)
Changed paths:
M core/src/main/java/hudson/model/Cause.java
M test/src/test/java/hudson/model/CauseTest.java
Log Message:
-----------
[JENKINS-21605] Further reduce number of recorded upstream causes (#9248)
* Fix non-determinism in nested cause tests
For deeplyNestedCauses, quickly triggering a jobs with no quiet period
runs the possibility that a job is triggered while it is still in the
queue. Triggering and waiting for the jobs to execute synchronously
avoids this and also simplifies the code.
The broadlyNesstedCauses test suffers from the same problem, but is
additionally not structured in the way the original issue describes to
reproduce the issue. Using the quiet period argument to scheduleBuild2,
we can reliably produce a graph where each build is triggered by the
other two jobs. An additional final job outside of the loop cuts off the
1 second quiet period from the last loop's iteration so that the test is
never waiting for the quiet period of any jobs even though half of the
schedule operations specify one.
* Re-work nested cause trimming algorithm
To unsubscribe from these emails, change your notification settings at
https://github.com/jenkinsci/jenkins/settings/notifications
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/jenkins/push/refs/heads/master/57d646-53b5e9%40github.com.
