Intermittent comm/mail/base/test/browser/browser_threadTreeDeleting.js | selected row should be above the last visible row - 299 > 299
Categories
(Thunderbird :: Folder and Message Lists, defect, P5)
Tracking
(thunderbird138 fixed)
| Tracking | Status | |
|---|---|---|
| thunderbird138 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: freaktechnik)
References
Details
(Keywords: intermittent-failure, intermittent-testcase)
Attachments
(1 file, 1 obsolete file)
Filed by: elizabeth [at] thunderbird.net
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=439773586&repo=comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/dM2IgbArTOy76hKtR3Jtbw/runs/0/artifacts/public/logs/live_backing.log
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 43•1 year ago
|
||
This is a tricky one. The test is already waiting extra time for the
additional scroll events, but the screenshot of the fail shows the
threadTree to be in a wrong scroll position. This patch resets that
timeout after each late scroll event to better catch all of them. This
basically forces the UI to be idle for the requested timeout. Maybe
that helps.
The test also adds two more asserts which might help with better
understanding what is going wrong.
Updated•1 year ago
|
| Comment hidden (Intermittent Failures Robot) |
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 46•1 year ago
|
||
This issue is apparent for me when running the test with --verify. The race this solves is that we set the
selected message in the thread tree after the deletion has completed in the database. Sometimes this selection
would happen after we had manually altered the selected index in the test, and as such would reset it to an
earlier state. This resolves the race by waiting for that selection with every keypress that is expected to
update the selected message. We might want to address the selection override race by only applying the
selection if there haven't been any interactions since the deletion was triggered or by blocking interaction
while the deletion is pending.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 47•1 year ago
|
||
Pushed by alessandro@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/1552a1dbcc79
Fix selection race when deleting in browser_threadTreeDeleting. r=john.bieling
| Comment hidden (Intermittent Failures Robot) |
Description
•