Bug 44928 - commit-queue gets stuck if rollout fails and tree is red
Summary: commit-queue gets stuck if rollout fails and tree is red
Status: RESOLVED DUPLICATE of bug 37553
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 44924
  Show dependency treegraph
 
Reported: 2010-08-30 20:49 PDT by Eric Seidel (no email)
Modified: 2010-08-30 20:52 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2010-08-30 20:49:05 PDT
commit-queue gets stuck if rollout fails and tree is red

Recent Status

Patch 64903 from bug 44196: Landing patch 5 minutes ago
Unable to successfully build and test [results] 5 minutes ago
Patch 66003 from bug 44924: Landing rollout patch 17 minutes ago
Unable to successfully build and test [results] 17 minutes ago
Patch 66003 from bug 44924: Landing rollout patch 26 minutes ago
Unable to successfully build and test [results]

failure message:
http://webkit-commit-queue.appspot.com/results/3826166

I believe this is what's happening:

Normally the cq tries 3 times when landing a patch:

1.  applies patch, tries to build, run tests, if successful lands, stops processing.
2.  builds and tests w/o patch applied.  if fails, assumes tree is busted, stops processing, sleeps 2 minutes.
3.  applies patch, tries to build, run tests, if succeeds, lands.  if fails, rejects patch.

this allows us to deal with flaky tests better.


I believe we already have a bug about svn-apply failures going through these steps when instad they should fail out early.  Build errors should also fail early since they're never flaky.  That would solve the case seen today where the apply failed.
Comment 1 Mihai Parparita 2010-08-30 20:50:49 PDT
I think bug 37553 is about svn-apply failing.
Comment 2 Eric Seidel (no email) 2010-08-30 20:51:53 PDT
Yup, this will basically end up being a duplicate of bug 37553.  We just need bug 37553 to handle the build case too.
Comment 3 Eric Seidel (no email) 2010-08-30 20:52:26 PDT

*** This bug has been marked as a duplicate of bug 37553 ***