Closed
Bug 1490071
Opened 6 years ago
Closed 5 years ago
Updated job results take longer to appear in the UI than before
Categories
(Tree Management :: Treeherder: Frontend, defect, P1)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bhearsum, Unassigned)
Details
For at least the past week or so I've found that Treeherder is much slower to update than before. It used to be that I could keep pages like https://treeherder.mozilla.org/#/jobs?repo=try&author=bhearsum@mozilla.com open, and results would show up quickly. Now, I often end up refreshing and finding more up-to-date results than were being shown.
Comment 1•6 years ago
|
||
Hi! Apart from a deploy on Friday that was rolled back after 2 hours, we haven't had a prod push since 13th August. I'm presuming either the issue started earlier than a week ago but happened to not be visible until then, or else it could be a Firefox regression?
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Ed Morley [:emorley] from comment #1) > Hi! Apart from a deploy on Friday that was rolled back after 2 hours, we > haven't had a prod push since 13th August. I'm presuming either the issue > started earlier than a week ago but happened to not be visible until then, > or else it could be a Firefox regression? Either of those are possible, I guess. I've been using Treeherder a lot more the past week than in awhile, so I may not have noticed if something changed before that. I'm also on Firefox Nightly. I'm trying to reproduce with the developer console open to get some more info.
Comment 3•5 years ago
|
||
We've made a number of changes in the frontend over the last 4 months.
Does this still occur?
Component: Treeherder → Treeherder: Frontend
Flags: needinfo?(bhearsum)
Priority: -- → P1
Summary: treeherder is slower to update than before → Updated job results take longer to appear in the UI than before
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(bhearsum)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•