1766331 - Treeherder UI is slow to load "Failure Summary" of a job, deceives you into thinking it has updated when it hasn't

Status: RESOLVED DUPLICATE of bug 1756406

(Tree Management :: Treeherder: Frontend, defect)

Description

[Botond Ballo [:botond]]

STR

1. Load a Treeherder revision with multiple failed jobs, such as https://treeherder.mozilla.org/jobs?repo=try&revision=42639403dfa7a5f9ad10c3b214541948e0136e67
2. Click on one of the failed jobs, such as https://treeherder.mozilla.org/jobs?repo=try&revision=42639403dfa7a5f9ad10c3b214541948e0136e67&selectedTaskRun=T7O02XzOTtyIQqAq68FbNA.0
3. Wait until the Failure Summary view appears and is loaded
4. Click on another failed job, such as https://treeherder.mozilla.org/jobs?repo=try&revision=42639403dfa7a5f9ad10c3b214541948e0136e67&selectedTaskRun=I3UbvgFORsi6aY-WmR791w.0

Actual results

The contents of the "Failure Summary" view "blink", i.e. the opacity decreases and then increases again, which suggests to the user that the view has updated to reflect the contents of the newly clicked job.

But it hasn't! The view is still showing the contents of the previously selected job, even though in the main view the new job is now marked as selecte4d.

This is very deceptive -- it's super easy to be fooled into thinking you're looking at the summary of the newly selected job, when you're not.

Several seconds later, the "Failure Summary" view is finally updated again, to show the contents of the newly selected job.

Expected results

The main view and the "Failure Summary" view are in sync -- if the main view has updated to mark a new job as selected, the contents of the "Failure Summary" should be updated as well.

Alternatively, if it takes a while to load the new "Failure Summary", that view should show a spinner wheel or something until the correct contents are loaded. It should not continue showing the contents of the previously selected job while the new job is marked as selected in the main view.

Comment 1

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

There might be two issues here with the second aggravating the first one: The race between bug suggestions getting loaded and other loads, and issues to generate the failure suggestions yesterday.