Closed Bug 574590 Opened 15 years ago Closed 15 years ago

mozilla-central builds not being triggered since bug 574557

Categories

(Release Engineering :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: nthomas)

Details

After the push that caused bug 574557 was manually put in the pushlog db, we got mozilla-central builds for that one, but then the next two, 15 minutes and almost an hour later (c13c4f35a17b and b51803f3fdef), haven't triggered builds at all. Tree's closed.
From the scheduler master log: 2010-06-24 21:18:55-0700 [-] Polling Hg server at http://hg.mozilla.org//mozilla-central/pushlog?fromchange=21ee5212a53728c6b443c5e123774455d3064e97 2010-06-24 21:18:55-0700 [-] Starting factory <HTTPClientFactory: http://hg.mozilla.org//mozilla-central/pushlog?fromchange=21ee5212a53728c6b443c5e123774455d3064e97> 2010-06-24 21:19:00-0700 [HTTPPageGetter,client] adding change, who Callek@gmail.com, 0 files, rev=, branch=mozilla-central, repository=, comments http://hg.mozilla.org/mozilla-central/rev/, category None 2010-06-24 21:19:00-0700 [HTTPPageGetter,client] last changeset on http://hg.mozilla.org/mozilla-central 2010-06-24 21:19:00-0700 [HTTPPageGetter,client] Stopping factory <HTTPClientFactory: http://hg.mozilla.org//mozilla-central/pushlog?fromchange=21ee5212a53728c6b443c5e1237 74455d3064e97> 21ee5212a537 is the revision before bug 574557 hit, it detects Callek's change but claims 'rev=' instead of 'rev=51bd519736c4'. Then it starts making a bogus request: 2010-06-24 21:19:55-0700 [-] Polling Hg server at http://hg.mozilla.org//mozilla-central/pushlog?fromchange= 2010-06-24 21:19:55-0700 [-] Starting factory <HTTPClientFactory: http://hg.mozilla.org//mozilla-central/pushlog?fromchange=> I've reconfig'd the scheduler master and now it's look for changes after the current tip, b51803f3fdef. Working on getting builds for c13c4f35a17b and b51803f3fdef.
Builds running on both those revisions, mozilla-central reopened.
Assignee: nobody → nrthomas
Status: NEW → RESOLVED
Closed: 15 years ago
Priority: -- → P1
Resolution: --- → FIXED
Nick, any idea why that happened? I can't see anything in the feed that would look off.
Not that I can see, unless the feed was bogus at the time as a result of the manual insert in the pushlog db.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.