Open
Bug 1414563
Opened 7 years ago
Updated 3 years ago
TEST-UNEXPECTED-FAIL | /builds/slave/test/build/tests/mozmill/content-tabs/test-content-tab.js | test-content-tab.js::test_spellcheck_in_content_tabs
Categories
(Thunderbird :: General, enhancement)
Thunderbird
General
Tracking
(Not tracked)
REOPENED
Thunderbird 58.0
People
(Reporter: jorgk-bmo, Assigned: aceman)
Details
(Whiteboard: [Thunderbird-testfailure: Z Linux debug])
Attachments
(1 file)
|
6.01 KB,
patch
|
jorgk-bmo
:
review+
|
Details | Diff | Splinter Review |
Frequently seen on Linux debug on Treeherder.
No so frequent to be really annoying, so I haven't disabled it yet. I hear that a patch is in the wings, so here's the bug ;-)
Green try, so at least it shouldn't make things worse:)
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=d283a76f8a201c32416682edcda3a1e92d5c091b
Attachment #8925311 -
Flags: review?(jorgk)
| Reporter | ||
Comment 2•7 years ago
|
||
Comment on attachment 8925311 [details] [diff] [review]
1414563.patch
Looks good. Thanks for the "boy-scout" clean-up. You're the best person to know when to wait.
Sadly this is just the tip of the iceberg of test failures on Linux debug.
Attachment #8925311 -
Flags: review?(jorgk) → review+
| Reporter | ||
Comment 3•7 years ago
|
||
How about
TEST-UNEXPECTED-FAIL | /builds/slave/test/build/tests/mozmill/content-tabs/test-content-tab.js | test-content-tab.js::test_content_tab_context_menu
next, that's the second most frequent failure I haven't switched off yet (no bug yet).
I thought that one is solved by this patch too. Yes, there is no change to the function, so it may be the test-content-tab.js::test_spellcheck_in_content_tabs affected it.
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/b5fb9c055e0e
wait for context menu to open before poking its contents in test-content-tab.js. r=jorgk CLOSED TREE
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
| Reporter | ||
Updated•7 years ago
|
Target Milestone: --- → Thunderbird 58.0
| Reporter | ||
Comment 6•7 years ago
|
||
Sadly not 100% successful, still failing here:
https://treeherder.mozilla.org/#/jobs?repo=comm-central&revision=b5fb9c055e0e5a890f4515099bc3a967b76f4289&selectedJob=142241545
Should we reopen the bug?
Flags: needinfo?(acelists)
| Reporter | ||
Comment 7•7 years ago
|
||
Pretty perma-red on Linux and Windows debug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Reporter | ||
Comment 8•7 years ago
|
||
Latest debug try on Linux with Aceman's new patch:
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=35a928fc59485bd63769dbf1373d172fa83d7fea
Flags: needinfo?(acelists)
| Reporter | ||
Comment 9•6 years ago
|
||
Just for the record: This test is totally wrong. Spell check in M-C is async, so this code doesn't fly:
assert_true(suggestions.length > 0, "What, is zombocom a registered word now?");
Which is what we see:
EXCEPTION: What, is zombocom a registered word now?
The suggestions simply haven't arrived yet. I've written some spellcheck Mochitests for M-C once upon a time, and the right ways is to listen to some sort of event. Looking at the tests in editor/spellchecker/tests/, it's the onSpellCheck() callback. So we should wait for the spellcheck to finish before opening the context menu.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•