Closed Bug 1042233 Opened 11 years ago Closed 11 years ago

TBPL often shows "Unknown - Pushlog failed to load" in place of pushlog

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1030020

People

(Reporter: botond, Unassigned)

References

Details

STR: Open a link to a Try server push, such as https://tbpl.mozilla.org/?tree=Try&rev=4065a71ad092 Expected: TBPL displays a log of commits in the push. Actual: TBPL shows "Unknown - Pushlog failed to load" instead The problem is intermittent, but it started to happen much more frquently in the past week or so.
This is an IT issue, not a TBPL issue.
Assignee: nobody → network-operations
Component: Tinderboxpushlog → NetOps
Product: Webtools → Infrastructure & Operations
QA Contact: jbarnell
Version: Trunk → other
Can you please provide some further details? What would be most helpful would be: source IP address(es) dest IP address(es) port numbers Thanks.
Flags: needinfo?(botond)
(In reply to Dave Curado :dcurado from comment #2) > Can you please provide some further details? > > What would be most helpful would be: > source IP address(es) > dest IP address(es) > port numbers > > Thanks. I assume the relevant information here concerns the request the TBPL server (or JS on the TBPL site, I'm not sure how it's architected) is making to hg.mozilla.org to get the pushlog. Someone who works on TBPL would be able to provide that.
Flags: needinfo?(emorley)
Nick Thomas suggested on IRC that this belongs under bug 1042210.
Blocks: 1042210
Flags: needinfo?(botond)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
The full error message in TBPL shows what is failing to load from the client: hg.mozilla.org This is a dupe of bug 1030020 - ie for the try repo hg.mozilla.org frequently doesn't respond in a timely fashion.
Flags: needinfo?(emorley)
Resolution: WONTFIX → DUPLICATE
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.