| Issue 92109: | Buildbot misses a trigger when it restarts | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Restricted
Sign in to add a comment
|
So when bots restart after a completed build we often notice that they don't start building any queued commits after the restart. Here's an example: Build 125 of the x86 generic PFQ finished at 16:44:31. It rebooted after that and connected at 16:47:08. However it did not start building even though it had plenty of queued commits that it needed to test. At 16:55:02 I hit the force build button and it started testing things. You can see the build logs here: http://build.chromium.org/p/chromiumos/builders/x86%20generic%20PFQ/builds/125 http://build.chromium.org/p/chromiumos/builders/x86%20generic%20PFQ/builds/126 One such commit that was queued up was here: http://build.chromium.org/p/chromiumos/changes/39398
Aug 8, 2011
#1
bdavi...@chromium.org
Labels:
-Restrict-View-InfraTeam -Restrict-EditIssue-InfraTeam
Aug 14, 2011
I think we might have the same problem on the chromium watefall. Sometimes testers are not triggered.
Status:
Available
Labels: Pri-2 Type-Bug
Sep 16, 2011
This is happening often and stalling the ChromeOS tree.
Sep 20, 2011
This happens consistently on the Chrome OS waterfall. x86-generic PFQ does not kick off unless a commit comes in while it's not doing anything. Someone has to manually kick it, or wait until someone else checks in. Can someone on either chrome-infra or the cros build team look at this this week? It slows us down.
Cc:
mal@chromium.org bdavi...@chromium.org
Labels: -Pri-2 Pri-0
Sep 20, 2011
I'll get someone on it. -Brad
Sep 29, 2011
Here is another example of a trigger that was missed after restart: http://build.chromium.org/p/chromiumos/changes/54499 Separately, sometimes the commits are misparsed, such as this one: http://build.chromium.org/p/chromiumos/changes/54505 "Branch: master fd79ed4af90a7cb1004115365b918f066b17436a 2cdd2a2e48016ff83dde47fc8dde76141bba57e3 refs/heads/release-1011.B" The first bug (where commits are parsed correctly, and the trigger sent, but then discarded after reboot), is much more common.
Jan 6, 2012
Was this fixed after buildbot upgrade?
Labels:
Area-Build
Jan 7, 2012
Yes this was FIXED by the buildbot upgrade. Thanks!!
Status:
Fixed
Cc: maruel@chromium.org
Oct 13, 2012
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
Labels:
Restrict-AddIssueComment-Commit
Mar 10, 2013
(No comment was entered for this change.)
Labels:
-Area-Build Build
Jul 2, 2013
(No comment was entered for this change.)
Labels:
-Build-Infrastructure Infra
|
||||||||||
| ► Sign in to add a comment | |||||||||||