[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus updated JENKINS-53499 Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Change By: Baptiste Mathus Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus updated JENKINS-53499 Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus started work on JENKINS-53499 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Change By: R. Tyler Croy Sprint: Evergreen - Milestone 1 , Evergreen - Milestone 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-10 20:56 Labels: evergreen testing Priority: Major Reporter: Baptiste Mathus During shUnit2 tests, it can happen that there will be 3 or 4 Git commits related to the updates that happened. This is due to a race condition: when docker-compose starts everything, if the instance starts quickly enough to hit the backend before it received the curl call for pushing the ingest.json then there will be two updates: one from UL0 to UL1, with UL1 an actually first default and empty UL served by the backed one from UL1 to UL2, once the ingest.json with actual plugins and so on has been received. If the ingest.json is pushed before the instance first requests the backend, then the bump will be directly from UL0 to UL2. We need to work out a solution that avoids this source of test flakiness, or we will suffer from it for sure in the upcoming weeks.
