Intermittent browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out -
Categories
(Firefox :: Keyboard Navigation, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | --- | unaffected |
firefox67 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: Jamie)
References
Details
(Keywords: intermittent-failure, regression, Whiteboard: [stockwell disable-recommended])
Attachments
(1 file, 1 obsolete file)
Filed by: dvarga [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=221160878&repo=mozilla-inbound
[task 2019-01-10T20:28:30.746Z] 20:28:30 INFO - TEST-START | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js
[task 2019-01-10T20:29:15.828Z] 20:29:15 INFO - TEST-INFO | started process screentopng
[task 2019-01-10T20:29:16.549Z] 20:29:16 INFO - TEST-INFO | screentopng: exit 0
[task 2019-01-10T20:29:16.549Z] 20:29:16 INFO - Buffered messages logged at 20:28:30
[task 2019-01-10T20:29:16.550Z] 20:29:16 INFO - Entering test bound testAppMenuButtonPress
[task 2019-01-10T20:29:16.553Z] 20:29:16 INFO - Console message: [JavaScript Warning: "Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode”" {file: "chrome://mochikit/content/tests/SimpleTest/EventUtils.js" line: 869}]
[task 2019-01-10T20:29:16.553Z] 20:29:16 INFO - Console message: [JavaScript Warning: "Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox”" {file: "chrome://mochikit/content/tests/SimpleTest/EventUtils.js" line: 869}]
[task 2019-01-10T20:29:16.553Z] 20:29:16 INFO - Buffered messages finished
[task 2019-01-10T20:29:16.554Z] 20:29:16 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out -
[task 2019-01-10T20:29:16.557Z] 20:29:16 INFO - GECKO(1511) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2019-01-10T20:29:16.558Z] 20:29:16 INFO - GECKO(1511) | MEMORY STAT | vsize 1824MB | residentFast 264MB | heapAllocated 79MB
[task 2019-01-10T20:29:16.559Z] 20:29:16 INFO - TEST-OK | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | took 45099ms
[task 2019-01-10T20:29:16.560Z] 20:29:16 INFO - checking window state
[task 2019-01-10T20:29:17.447Z] 20:29:17 INFO - GECKO(1511) | Completed ShutdownLeaks collections in process 1769
[task 2019-01-10T20:29:17.506Z] 20:29:17 INFO - GECKO(1511) | Completed ShutdownLeaks collections in process 1684
[task 2019-01-10T20:29:17.507Z] 20:29:17 INFO - GECKO(1511) | Completed ShutdownLeaks collections in process 1603
[task 2019-01-10T20:29:17.508Z] 20:29:17 INFO - GECKO(1511) | Completed ShutdownLeaks collections in process 1625
[task 2019-01-10T20:29:17.509Z] 20:29:17 INFO - GECKO(1511) | Completed ShutdownLeaks collections in process 1715
[task 2019-01-10T20:29:17.791Z] 20:29:17 INFO - GECKO(1511) | Completed ShutdownLeaks collections in process 1511
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 10•6 years ago
|
||
Jamie, could you take a look please? Looks like this test has become a high prio intermittent at this point (see comment #9)
Comment 11•6 years ago
|
||
Joel, why didn't this get flagged up to someone as stockwell:needsowner?
Comment 12•6 years ago
|
||
gijs, this only started failing since February 14th. I am not sure why there wasn't a stockwell tag on this, I agree that looks invalid.
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 15•6 years ago
|
||
For the record, I am working on this, but am not having much luck so far. On Linux and Mac (but not Windows), focusing and pressing space on the Bookmark This page button (#star-button) in the test just does nothing sometimes. I've confirmed that the button is visible, that the button definitely has focus, that focus isn't getting yanked away by something else (by waiting 2 seconds and checking focus again), and that the "Show editor when saving" option is checked.
Comment 16•6 years ago
|
||
(In reply to James Teh [:Jamie] from comment #15)
For the record, I am working on this, but am not having much luck so far. On Linux and Mac (but not Windows), focusing and pressing space on the Bookmark This page button (#star-button) in the test just does nothing sometimes. I've confirmed that the button is visible, that the button definitely has focus, that focus isn't getting yanked away by something else (by waiting 2 seconds and checking focus again), and that the "Show editor when saving" option is checked.
Have you tried adding a popuphidden
listener to the popup and see if it fires when trying to open it? This is what seems to be happening in bug 1396196 (linux intermittent in browser_editcontrols_update.js ). Basically, something (in that bug, a focus change notification from the OS) trips some xul popup code while the popup is being opened, and closes it immediately, leading to the impression that it "does nothing".
Assignee | ||
Comment 17•6 years ago
|
||
I added this code before sending the key press:
let onHidden = evt => info("jtd panel hidden");
panel.addEventListener("popuphidden", onHidden);
After the key press, I wait for 2 seconds (via setTimeout). However, the "jtd panel hidden" never appears in the output. So, I guess that means it isn't getting fired?
Frustratingly, I just added a whole bunch of debug logging to the actual UI code... and with that, the bug magically goes away. 😬 I'll keep chipping away at it.
Comment hidden (Intermittent Failures Robot) |
Comment 19•6 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #12)
gijs, this only started failing since February 14th. I am not sure why there wasn't a stockwell tag on this, I agree that looks invalid.
Up until now, as it has the [stockwell disable-recommended] this did not appear in the fresh or neglected oranges list.
Comment 20•6 years ago
|
||
There are 147 total failures in the last 7 days, on linux, win and osx.
Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=230005636&repo=autoland&lineNumber=2919
[task 2019-02-23T00:23:42.093Z] 00:23:42 INFO - TEST-START | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js
[task 2019-02-23T00:23:42.101Z] 00:23:42 INFO - GECKO(1791) | Chrome file doesn't exist: /builds/worker/workspace/build/tests/mochitest/browser/browser/base/content/test/keyboard/head.js
[task 2019-02-23T00:23:42.253Z] 00:23:42 INFO - GECKO(1791) | [Parent 1791, Main Thread] WARNING: '!parent', file /builds/worker/workspace/build/src/netwerk
[task 2019-02-23T00:25:12.768Z] 00:25:12 INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Sidebar hidden after press -
[task 2019-02-23T00:25:12.768Z] 00:25:12 INFO - Leaving test bound testSidebarsButtonPress
[task 2019-02-23T00:25:12.769Z] 00:25:12 INFO - Entering test bound testBookmarkButtonPress
[task 2019-02-23T00:25:12.769Z] 00:25:12 INFO - Buffered messages finished
[task 2019-02-23T00:25:12.770Z] 00:25:12 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out -
[task 2019-02-23T00:25:12.770Z] 00:25:12 INFO - GECKO(1791) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2019-02-23T00:25:12.774Z] 00:25:12 INFO - GECKO(1791) | MEMORY STAT | vsize 1949MB | residentFast 311MB | heapAllocated 81MB
[task 2019-02-23T00:25:12.778Z] 00:25:12 INFO - TEST-OK | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | took 90089ms
[task 2019-02-23T00:25:12.778Z] 00:25:12 INFO - Not taking screenshot here: see the one that was previously logged
[task 2019-02-23T00:25:12.778Z] 00:25:12 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Found a tab after previous test timed out: https://example.com/ -
[task 2019-02-23T00:25:12.782Z] 00:25:12 INFO - GECKO(1791) | ++DOCSHELL 0x7feea6e9c000 == 1 [pid = 2118] [id = {f962cc04-420a-4fd3-a32e-538e19b2b21b}]
[task 2019-02-23T00:25:12.782Z] 00:25:12 INFO - checking window state
[task 2019-02-23T00:25:12.786Z] 00:25:12 INFO - GECKO(1791) | ++DOMWINDOW == 1 (0x7feea6e39c00) [pid = 2118] [serial = 1] [outer = (nil)]
James, since you are working on the bug, I'm removing the disable recommended bug and adding the needswork:owner one.
Comment hidden (Intermittent Failures Robot) |
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 23•6 years ago
|
||
After days of exasperation, I think I've finally figured out what's going on here. Testing the fix at the moment.
Assignee | ||
Comment 24•6 years ago
|
||
The status regarding whether a page is bookmarked or not is updated async.
While the update is pending, the Bookmark this page button ignores activation.
Thus, the test must wait for the update to be finished before trying to press the button.
This fixes intermittent timeouts in this test.
Comment 25•6 years ago
|
||
Comment 26•6 years ago
|
||
bugherder |
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 28•6 years ago
|
||
This is still occurring: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=231705402&repo=autoland&lineNumber=1633
James, should I file a new bug or reopen this?
Assignee | ||
Comment 29•6 years ago
|
||
It seems this is a failure in a different subtest (testAppMenuButtonPress vs testBookmarkButtonPress). I believe the latter (testBookmarkButtonPress) was a much more regular failure, which is why this became high priority in comment 9 after bug 1436086 landed (which introduced that test). That's the one I've fixed here. I think the reason this bug was originally filed was the former (testAppMenuButtonPress) and it seems that one hasn't gone away.
I'd prefer to have a new bug for this testappMenuButtonPress failure, as this bug now has a lot of history relating to the test that is now fixed.
Thanks!
Comment 30•6 years ago
|
||
Filed bug 1532501. Thanks James.
Comment hidden (Intermittent Failures Robot) |
Comment 32•5 years ago
|
||
The Bookmark page button ignores activation if there is pending update. Thus,
the test must wait for the update to be finished before synthesizing mouse
actions.
Comment 33•5 years ago
|
||
Comment 34•5 years ago
|
||
Comment on attachment 9140900 [details]
Bug 1519226 - Wait for the bookmarked status to finish updating before starting test; r?Gijs
Revision D71114 was moved to bug 1385882. Setting attachment 9140900 [details] to obsolete.
Comment 35•5 years ago
|
||
(In reply to Pulsebot from comment #33)
Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/5c1092771230
Wait for the bookmarked status to finish updating before starting test;
r=Gijs
Sorry, this should have landed pointing to bug 1385882 instead.
Comment 36•5 years ago
|
||
Comment 37•5 years ago
|
||
Backed out for landing with wrong bug number, relanded with correct bug no.
Comment 38•5 years ago
|
||
Description
•