Closed
Bug 1485080
Opened 6 years ago
Closed 6 years ago
Tree status in treeherder does not update automatically
Categories
(Tree Management :: Treeherder: Frontend, defect)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: apavel, Assigned: camd)
Details
When closing one of the repos for a failure, then opening it again, the status in treeherder does not change. In https://mozilla-releng.net/treestatus the tree is open, but the status in treeherder is still closed: https://imagebin.ca/v/4CyoD8LB1ime. It does not refresh automatically, it refreshes only when I refresh the page. Also, SV sheriffs use 2 stations, 1 main and 1 secondary. If we classify failures on our main station, it takes about ~10m, maybe more until the treeherder details are updated on our secondary pcs. On Sunday for example, we did not refresh treeherder on the secondary station for about ~6h, the info on the tree at 08:00 RO was the same as it was at 14:00 RO even if there were changes on the trees. Small ones, but there were. Please ni? me for any other info.
Comment 1•6 years ago
|
||
Hi! Thank you for filing :-) If/when this happens next, could you open the devtools console and keep an eye out for the periodic (every 2 minutes) XHR requests to https://treestatus.mozilla-releng.net/* and see what their response code and content is?
Component: Treeherder → Treeherder: Frontend
Flags: needinfo?(apavel)
Comment 2•6 years ago
|
||
(In reply to Andreea Pavel [:apavel] from comment #0) > Also, SV sheriffs use 2 stations, 1 main and 1 secondary. If we classify > failures on our main station, it takes about ~10m, maybe more until the > treeherder details are updated on our secondary pcs. This will be a separate issue - could you open another bug?
Reporter | ||
Comment 3•6 years ago
|
||
(In reply to Ed Morley [:emorley] from comment #1) > Hi! Thank you for filing :-) > > If/when this happens next, could you open the devtools console and keep an > eye out for the periodic (every 2 minutes) XHR requests to > https://treestatus.mozilla-releng.net/* and see what their response code and > content is? I opened inbound about ~45 min ago, i still see it closed (i did not refresh the page) If i open it in another tab, it's updated. From the inspector, in the console i have https://irccloud.mozilla.com/file/tKSLkr4Q/image.png and in the Networking tab i have https://irccloud.mozilla.com/file/Y3U1n4YQ/image.png I will also file a different bug for the second issue.
Flags: needinfo?(apavel)
Comment 4•6 years ago
|
||
And note that this is only true of the treestatus in the fake tab inside the page: in the actual browser tab, the status does update.
Updated•6 years ago
|
Flags: needinfo?(cdawson)
Assignee | ||
Comment 5•6 years ago
|
||
I believe this to be fixed on stage. I re-wrote this code recently, so next deploy should fix it. I tested it by every time I poll for the latest treestatus, I switch being setting it open or closed and it works great there.
Assignee: nobody → cdawson
Status: NEW → ASSIGNED
Flags: needinfo?(cdawson)
Assignee | ||
Comment 6•6 years ago
|
||
I believe this to be fixed. Please reopen if you see this again.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•6 years ago
|
||
(In reply to Cameron Dawson [:camd] from comment #6) > I believe this to be fixed. Please reopen if you see this again. it is, i have seen no occurrences in the last month. thanks for working on it.
You need to log in
before you can comment on or make changes to this bug.
Description
•