Closed
Bug 518829
Opened 15 years ago
Closed 15 years ago
pushloghtml is unreliable
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: sgautherie, Assigned: aravind)
References
()
Details
I have noticed that pushlog can: * Take a moment to acknowledge new pushes. While I felt like it always was immediate "before". (Though maybe I just didn't notice.) (Noticed this for some time now.) * Lastest pushes can be displayed then forgotten then redisplayed again... This is even more painful on http://tests.themasta.com/tinderboxpushlog/ where builds move from one push to another :-( (Noticed this recently only.)
Comment 1•15 years ago
|
||
I've also seen this a lot lately when I've been landing patches on multiple Hg repos. It's very frustrating, and it greatly confuses tbpl.
Reporter | ||
Comment 2•15 years ago
|
||
Pike and ted told me to check: http://dm-hg01.mozilla.org/mozilla-central/pushloghtml?startdate=1+day+ago&enddate=now and http://dm-hg02.mozilla.org/mozilla-central/pushloghtml?startdate=1+day+ago&enddate=now which are behind http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=1+day+ago&enddate=now Results of reloading both pages: Both dm-hg0? "randomly" include/miss (my) lastest checkin. Seems like the issue is at a "lower" level. (Some stuck http/database connection/cache?)
Assignee | ||
Updated•15 years ago
|
Assignee: server-ops → aravind
Reporter | ||
Comment 3•15 years ago
|
||
Fwiw, comm-central push log has this bug too.
Assignee | ||
Comment 4•15 years ago
|
||
I am unable to reproduce this issue. Can I get a reproducible test case? I have an idea on what could be going on, but I'd like to have a reproducible test case that I can use.
Reporter | ||
Comment 5•15 years ago
|
||
Right now, I can reproduce with http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=1+day+ago&enddate=now though not with http://hg.mozilla.org/mozilla-central/pushloghtml
Assignee | ||
Comment 6•15 years ago
|
||
Found that one of the backend webheads had the wrong timestamp on it. Enabled time-sync options in vmware, so it should be good now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•15 years ago
|
||
Can't reproduce anymore atm, let's V.Fixed it.
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•