Intermittent browser_input_file_tooltips.js | Test timed out

NEW
Unassigned

Status

()

defect
P3
normal
3 years ago
a year ago

People

(Reporter: aryx, Unassigned)

Tracking

(Blocks 1 bug, {intermittent-failure})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s+, firefox51 affected)

Details

(Whiteboard: [stockwell unknown])

+++ This bug was initially created as a clone of Bug #1257750 +++

https://treeherder.mozilla.org/logviewer.html#?job_id=11144325&repo=fx-team

According to the reports in bug 1257750, this started 2-3 weeks ago.

04:12:11     INFO -  465 INFO TEST-START | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js
04:12:11     INFO -  Chrome file doesn't exist: /home/worker/workspace/build/tests/mochitest/browser/toolkit/components/tooltiptext/tests/head.js
04:12:11     INFO -  ++DOCSHELL 0x7f430621c800 == 9 [pid = 3479] [id = 11]
04:12:11     INFO -  ++DOMWINDOW == 25 (0x7f430688b800) [pid = 3479] [serial = 25] [outer = (nil)]
04:12:12     INFO -  ++DOMWINDOW == 26 (0x7f43072e8400) [pid = 3479] [serial = 26] [outer = 0x7f430688b800]
04:12:12     INFO -  ++DOMWINDOW == 27 (0x7f4308061800) [pid = 3479] [serial = 27] [outer = 0x7f430688b800]
04:12:12     INFO -  --DOCSHELL 0x7f430825d800 == 8 [pid = 3479] [id = 9]
04:12:12     INFO -  --DOCSHELL 0x7f4306b43000 == 7 [pid = 3479] [id = 8]
04:12:12     INFO -  --DOCSHELL 0x7f43062ea000 == 6 [pid = 3479] [id = 7]
04:12:12     INFO -  --DOCSHELL 0x7f430620b800 == 5 [pid = 3479] [id = 4]
04:12:12     INFO -  --DOCSHELL 0x7f4306b4a000 == 4 [pid = 3479] [id = 5]
04:12:12     INFO -  --DOCSHELL 0x7f4306205000 == 3 [pid = 3479] [id = 6]
04:12:14     INFO -  [Parent 3426] WARNING: Unable to retrieve the tooltip node document.: file /home/worker/workspace/build/src/layout/xul/nsXULTooltipListener.cpp, line 564
04:12:14     INFO -  ++DOCSHELL 0x7f4306c58800 == 4 [pid = 3479] [id = 12]
04:12:14     INFO -  ++DOMWINDOW == 28 (0x7f430625dc00) [pid = 3479] [serial = 28] [outer = (nil)]
04:12:14     INFO -  ++DOMWINDOW == 29 (0x7f4311e13400) [pid = 3479] [serial = 29] [outer = 0x7f430625dc00]
04:12:14     INFO -  ++DOMWINDOW == 30 (0x7f4311e1c800) [pid = 3479] [serial = 30] [outer = 0x7f430625dc00]
04:12:15     INFO -  --DOCSHELL 0x7f4306c5c800 == 3 [pid = 3479] [id = 2]
04:12:15     INFO -  --DOCSHELL 0x7f430621c800 == 2 [pid = 3479] [id = 11]
04:12:17     INFO -  --DOMWINDOW == 19 (0x7fe2d27a9000) [pid = 3426] [serial = 9] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 18 (0x7fe2e3ec5800) [pid = 3426] [serial = 2] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 17 (0x7fe2e3650000) [pid = 3426] [serial = 20] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 16 (0x7fe2ca957800) [pid = 3426] [serial = 13] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 29 (0x7f430688b800) [pid = 3479] [serial = 25] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 28 (0x7f4308629c00) [pid = 3479] [serial = 1] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 27 (0x7f4306bb4c00) [pid = 3479] [serial = 12] [outer = (nil)] [url = http://mochi.test:8888/browser/toolkit/components/tooltiptext/tests/xul_tooltiptext.xhtml]
04:12:17     INFO -  --DOMWINDOW == 26 (0x7f4307493c00) [pid = 3479] [serial = 7] [outer = (nil)] [url = http://mochi.test:8888/browser/toolkit/components/tooltiptext/tests/title_test.svg]
04:12:17     INFO -  --DOMWINDOW == 25 (0x7f43076a1800) [pid = 3479] [serial = 19] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 24 (0x7f430624fc00) [pid = 3479] [serial = 15] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 23 (0x7f4306ce9000) [pid = 3479] [serial = 17] [outer = (nil)] [url = data:text/html,<!DOCTYPE%20html><html><body><input%20id='i'></body></html>]
04:12:17     INFO -  --DOMWINDOW == 22 (0x7f4311110c00) [pid = 3479] [serial = 21] [outer = (nil)] [url = data:text/html,<!DOCTYPE%20html><html><body><form%20id='content'></form></body></html>]
04:12:17     INFO -  --DOMWINDOW == 21 (0x7f4306ce1800) [pid = 3479] [serial = 5] [outer = (nil)] [url = about:blank]
04:12:17     INFO -  --DOMWINDOW == 20 (0x7f4306252000) [pid = 3479] [serial = 10] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 19 (0x7f430823a800) [pid = 3479] [serial = 2] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 18 (0x7f4306bbb800) [pid = 3479] [serial = 9] [outer = (nil)] [url = http://mochi.test:8888/browser/toolkit/components/tooltiptext/tests/title_test.svg]
04:12:20     INFO -  --DOMWINDOW == 17 (0x7f4306bb4400) [pid = 3479] [serial = 8] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 16 (0x7f4311e13400) [pid = 3479] [serial = 29] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 15 (0x7f4308061800) [pid = 3479] [serial = 27] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 14 (0x7f43072eb800) [pid = 3479] [serial = 14] [outer = (nil)] [url = http://mochi.test:8888/browser/toolkit/components/tooltiptext/tests/xul_tooltiptext.xhtml]
04:12:20     INFO -  --DOMWINDOW == 13 (0x7f4306c21000) [pid = 3479] [serial = 13] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 12 (0x7f43086a8800) [pid = 3479] [serial = 20] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 11 (0x7f4306888c00) [pid = 3479] [serial = 16] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 10 (0x7f430720d000) [pid = 3479] [serial = 18] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 9 (0x7f4311169400) [pid = 3479] [serial = 22] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 8 (0x7f43072e8400) [pid = 3479] [serial = 26] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 7 (0x7f4306ce5000) [pid = 3479] [serial = 6] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 6 (0x7f430625c000) [pid = 3479] [serial = 11] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 5 (0x7f4306c20000) [pid = 3479] [serial = 4] [outer = (nil)] [url = about:blank]
04:12:20     INFO -  --DOMWINDOW == 4 (0x7f4306e0c800) [pid = 3479] [serial = 3] [outer = (nil)] [url = about:blank]
04:13:42     INFO -  TEST-INFO | started process screentopng
04:13:44     INFO -  TEST-INFO | screentopng: exit 0
04:13:44     INFO -  466 INFO checking window state
04:13:44     INFO -  467 INFO Entering test bound setup
04:13:44     INFO -  468 INFO Leaving test bound setup
04:13:44     INFO -  469 INFO Entering test bound test_singlefile_selected
04:13:44     INFO -  470 INFO starting test {"value":true,"result":"testfile_bug1251809"}
04:13:44     INFO -  471 INFO Moving mouse out of the way.
04:13:44     INFO -  472 INFO creating input field
04:13:44     INFO -  473 INFO Creating mock filepicker to select files
04:13:44     INFO -  474 INFO Waiting for the input to have the requisite files
04:13:44     INFO -  475 INFO The input has 1 file(s) selected.
04:13:44     INFO -  476 INFO Initial mouse move
04:13:44     INFO -  477 INFO Waiting
04:13:44     INFO -  478 INFO Second mouse move
04:13:44     INFO -  479 INFO Waiting for tooltip to open
04:13:44     INFO -  480 INFO TEST-PASS | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | tooltip label should match expectation -
04:13:44     INFO -  481 INFO Closing tab
04:13:44     INFO -  482 INFO Leaving test bound test_singlefile_selected
04:13:44     INFO -  483 INFO Entering test bound test_title_set
04:13:44     INFO -  484 INFO starting test {"title":"foo","result":"foo"}
04:13:44     INFO -  485 INFO Moving mouse out of the way.
04:13:44     INFO -  486 INFO creating input field
04:13:44     INFO -  487 INFO No real file selection required.
04:13:44     INFO -  488 INFO Initial mouse move
04:13:44     INFO -  489 INFO Waiting
04:13:44     INFO -  490 INFO Second mouse move
04:13:44     INFO -  491 INFO Waiting for tooltip to open
04:13:44     INFO -  492 INFO Console message: [JavaScript Error: "1471320768362	Toolkit.GMP	ERROR	GMPInstallManager.simpleCheckAndInstall Could not check for addons: Error: got node name: html, expected: updates (resource://gre/modules/addons/ProductAddonChecker.jsm:153:11) JS Stack trace: parseXML@ProductAddonChecker.jsm:153:11 < Async*ProductAddonChecker.getProductAddonList@ProductAddonChecker.jsm:320:12 < GMPInstallManager.prototype.checkForAddons@GMPInstallManager.jsm:107:5 < GMPInstallManager.prototype.simpleCheckAndInstall<@GMPInstallManager.jsm:204:29 < gBrowserInit._delayedStartup/<@browser.js:1309:7 < setTimeout handler*gBrowserInit._delayedStartup@browser.js:1305:5 < EventListener.handleEvent*gBrowserInit.onLoad@browser.js:993:5 < onload@browser.xul:1:1" {file: "resource://gre/modules/Log.jsm" line: 753}]
04:13:44     INFO -  App_append@resource://gre/modules/Log.jsm:753:9
04:13:44     INFO -  Logger.prototype.log@resource://gre/modules/Log.jsm:389:7
04:13:44     INFO -  LoggerRepository.prototype.getLoggerWithMessagePrefix/proxy.log@resource://gre/modules/Log.jsm:504:44
04:13:44     INFO -  Logger.prototype.error@resource://gre/modules/Log.jsm:397:5
04:13:44     INFO -  GMPInstallManager.prototype.simpleCheckAndInstall<@resource://gre/modules/GMPInstallManager.jsm:273:7
04:13:44     INFO -  TaskImpl_run@resource://gre/modules/Task.jsm:320:40
04:13:44     INFO -  Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:940:21
04:13:44     INFO -  this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7
04:13:44     INFO -  Promise*this.PromiseWalker.scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:747:11
04:13:44     INFO -  this.PromiseWalker.schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:779:7
04:13:44     INFO -  this.PromiseWalker.completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:714:7
04:13:44     INFO -  GMPInstallManager.prototype.checkForAddons/<@resource://gre/modules/GMPInstallManager.jsm:116:7
04:13:44     INFO -  Async*GMPInstallManager.prototype.checkForAddons@resource://gre/modules/GMPInstallManager.jsm:107:5
04:13:44     INFO -  GMPInstallManager.prototype.simpleCheckAndInstall<@resource://gre/modules/GMPInstallManager.jsm:204:29
04:13:44     INFO -  TaskImpl_run@resource://gre/modules/Task.jsm:319:40
04:13:44     INFO -  TaskImpl@resource://gre/modules/Task.jsm:280:3
04:13:44     INFO -  createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
04:13:44     INFO -  gBrowserInit._delayedStartup/<@chrome://browser/content/browser.js:1309:7
04:13:44     INFO -  setTimeout handler*gBrowserInit._delayedStartup@chrome://browser/content/browser.js:1305:5
04:13:45     INFO -  EventListener.handleEvent*gBrowserInit.onLoad@chrome://browser/content/browser.js:993:5
04:13:45     INFO -  onload@chrome://browser/content/browser.xul:1:1
04:13:45     INFO -  493 INFO TEST-UNEXPECTED-FAIL | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | Test timed out -

Comment 1

3 years ago
This isn't a new failure; the other failures are logged in 1257750, but that bug is marked fixed for some reason.

The test is using native mouse move events; I'm unclear if that is actually needed and can instead just use synthesizeMouse.

Updated

3 years ago
Flags: needinfo?(gijskruitbosch+bugs)

Comment 2

3 years ago
(In reply to Neil Deakin from comment #1)
> This isn't a new failure; the other failures are logged in 1257750, but that
> bug is marked fixed for some reason.

Because the bug that caused those timeouts was fixed, 3 months ago. There were then no more timeouts until about July 25:

https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1257750&endday=2016-08-16&startday=2016-06-01&tree=trunk

Do we know why it suddenly started happening again 2-3 weeks ago?

> The test is using native mouse move events; I'm unclear if that is actually
> needed and can instead just use synthesizeMouse.

It needs to cause a popup (tooltip) to show. I would expect that to require the native mouse moves. In any case, I think it's unlikely that's related unless code around those (native) events or tooltips changed in the timeframe where this started reoccurring. It's more likely to be related to the hardcoded timeout value the test uses.

At 35 failures over 2-3 weeks this isn't top of my priority list, and will be very hard to debug because of the number of retriggers you'd need to verify anything got fixed (in the hundreds, I expect). Feel free to ping me again if this increases in frequency.
Flags: needinfo?(gijskruitbosch+bugs)
tracking-e10s: --- → ?
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)

Comment 5

3 years ago
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
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)
this failure is becoming more frequent and getting on the radar of something we should fix.

the pattern here is linux32/64 debug e10s as the common failures.

a successful log [0] on linux32 debug looks like this:
 TEST-OK | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | took 10366ms

so when we fail on 45 seconds, something is happening.  Here is a screenshot:
http://mozilla-releng-blobs.s3.amazonaws.com/blobs/autoland/sha512/98eb69e6c54745fc383d30d30b1c12d2e835777051fb07b3b99bec41078f5c6d8c924a6ecdd818b2107f766f4226722a126a7183b82cdd70f91dafe312fe4c99

doesn't look interesting really, but maybe it will help.  Here is a clip from a failing log [1]:
04:32:36     INFO - Buffered messages logged at 04:31:48
04:32:36     INFO - Entering test bound setup
04:32:36     INFO - Leaving test bound setup
04:32:36     INFO - Entering test bound test_singlefile_selected
04:32:36     INFO - starting test {"value":true,"result":"testfile_bug1251809"}
04:32:36     INFO - Buffered messages logged at 04:31:49
04:32:36     INFO - Moving mouse out of the way.
04:32:36     INFO - creating input field
04:32:36     INFO - Creating mock filepicker to select files
04:32:36     INFO - Waiting for the input to have the requisite files
04:32:36     INFO - The input has 1 file(s) selected.
04:32:36     INFO - Initial mouse move
04:32:36     INFO - Waiting
04:32:36     INFO - Second mouse move
04:32:36     INFO - Buffered messages logged at 04:31:50
04:32:36     INFO - Waiting for tooltip to open
04:32:36     INFO - TEST-PASS | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | tooltip label should match expectation - 
04:32:36     INFO - Closing tab
04:32:36     INFO - Leaving test bound test_singlefile_selected
04:32:36     INFO - Entering test bound test_title_set
04:32:36     INFO - starting test {"title":"foo","result":"foo"}
04:32:36     INFO - Moving mouse out of the way.
04:32:36     INFO - creating input field
04:32:36     INFO - No real file selection required.
04:32:36     INFO - Initial mouse move
04:32:36     INFO - Waiting
04:32:36     INFO - Buffered messages logged at 04:31:51
04:32:36     INFO - Second mouse move
04:32:36     INFO - Waiting for tooltip to open
04:32:36     INFO - TEST-PASS | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | tooltip label should match expectation - 
04:32:36     INFO - Closing tab
04:32:36     INFO - Leaving test bound test_title_set
04:32:36     INFO - Entering test bound test_nofile_selected
04:32:36     INFO - starting test {"result":"No file selected."}
04:32:36     INFO - Buffered messages logged at 04:31:52
04:32:36     INFO - Moving mouse out of the way.
04:32:36     INFO - creating input field
04:32:36     INFO - No real file selection required.
04:32:36     INFO - Initial mouse move
04:32:36     INFO - Waiting
04:32:36     INFO - Second mouse move
04:32:36     INFO - Waiting for tooltip to open
04:32:36     INFO - Buffered messages finished
04:32:36     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | Test timed out - 


it is possible that we are really waiting for the tooltip to open and it doesn't?

other odd stuff is this message appears:
Chrome file doesn't exist: /builds/slave/test/build/tests/mochitest/browser/toolkit/components/tooltiptext/tests/head.js

that seems like a simple fix, but it doesn't seem related to the timeout.

[0] https://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-linux-debug/1482819036/autoland_ubuntu32_vm-debug_test-mochitest-e10s-browser-chrome-2-bm02-tests1-linux32-build137.txt.gz
[1] https://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-linux-debug/1482836136/autoland_ubuntu32_vm-debug_test-mochitest-e10s-browser-chrome-5-bm141-tests1-linux32-build69.txt.gz

:gijs, I see that you worked on this test case in the past, can you help troubleshoot this some more or help find someone who can?
Flags: needinfo?(gijskruitbosch+bugs)
Comment hidden (Intermittent Failures Robot)

Comment 25

2 years ago
(In reply to Joel Maher ( :jmaher) from comment #23)
> this failure is becoming more frequent and getting on the radar of something
> we should fix.
> 
> the pattern here is linux32/64 debug e10s as the common failures.
> 
> a successful log [0] on linux32 debug looks like this:
>  TEST-OK |
> toolkit/components/tooltiptext/tests/browser_input_file_tooltips.js | took
> 10366ms
> 
> so when we fail on 45 seconds, something is happening.  Here is a screenshot:
> http://mozilla-releng-blobs.s3.amazonaws.com/blobs/autoland/sha512/
> 98eb69e6c54745fc383d30d30b1c12d2e835777051fb07b3b99bec41078f5c6d8c924a6ecdd81
> 8b2107f766f4226722a126a7183b82cdd70f91dafe312fe4c99

Where is the mouse on this screenshot? Do screenshots on linux normally not have a cursor visible?


The last time we fixed something here we changed how long we waited between mousemoves. It's possible that increasing that again will reduce the frequency. I don't know how to verify that reasonably, because this only happens once every 30 times you run the test, if the messages from the bot are correct. :-\
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(jmaher)
I suspect this is an issue with running tests on docker vs a raw aws image or a real machine.

the 12 failures in 305 pushes is slightly misleading.  It over reports as we have >1 failure in some pushes, but in many cases we do not run the tests for every push, instead we run every 5th push.  

Interesting idea to wait between mouse moves, is there a way to listen for an event (or add an event) so we can do better than a random wait?  If not, maybe a much longer random wait so we have a much lower chance to run into this problem.
Flags: needinfo?(jmaher)

Updated

2 years ago
Flags: needinfo?(gijskruitbosch+bugs)
Comment hidden (Intermittent Failures Robot)

Comment 28

2 years ago
(In reply to Joel Maher ( :jmaher) from comment #26)
> I suspect this is an issue with running tests on docker vs a raw aws image
> or a real machine.
> 
> the 12 failures in 305 pushes is slightly misleading.  It over reports as we
> have >1 failure in some pushes, but in many cases we do not run the tests
> for every push, instead we run every 5th push.  
> 
> Interesting idea to wait between mouse moves, is there a way to listen for
> an event (or add an event) so we can do better than a random wait?  If not,
> maybe a much longer random wait so we have a much lower chance to run into
> this problem.

I would be surprised. I'm not even entirely sure what we're waiting for. Jared, do you know? Presumably the synthesized event is dispatched synchronously on the same thread.

Here's a base push:
remote:   https://treeherder.mozilla.org/#/jobs?repo=try&revision=b07bb59f91d14f5c51959d84eeaacb1271de06db

and one with a longer timeout:

remote:   https://treeherder.mozilla.org/#/jobs?repo=try&revision=7c96517eb1f4de9a6ab5d218957fc03e3bf00240

to see if that helps. Will need retriggers, of course...

Comment 29

2 years ago
(In reply to :Gijs from comment #28)
> (In reply to Joel Maher ( :jmaher) from comment #26)
> > I suspect this is an issue with running tests on docker vs a raw aws image
> > or a real machine.
> > 
> > the 12 failures in 305 pushes is slightly misleading.  It over reports as we
> > have >1 failure in some pushes, but in many cases we do not run the tests
> > for every push, instead we run every 5th push.  
> > 
> > Interesting idea to wait between mouse moves, is there a way to listen for
> > an event (or add an event) so we can do better than a random wait?  If not,
> > maybe a much longer random wait so we have a much lower chance to run into
> > this problem.
> 
> I would be surprised. I'm not even entirely sure what we're waiting for.
> Jared, do you know? Presumably the synthesized event is dispatched
> synchronously on the same thread.
> 
> Here's a base push:
> remote:  
> https://treeherder.mozilla.org/#/
> jobs?repo=try&revision=b07bb59f91d14f5c51959d84eeaacb1271de06db
> 
> and one with a longer timeout:
> 
> remote:  
> https://treeherder.mozilla.org/#/
> jobs?repo=try&revision=7c96517eb1f4de9a6ab5d218957fc03e3bf00240
> 
> to see if that helps. Will need retriggers, of course...

Eh, with needinfo for Jared this time:
Flags: needinfo?(jaws)

Comment 30

2 years ago
(In reply to Joel Maher ( :jmaher) from comment #26)
> I suspect this is an issue with running tests on docker vs a raw aws image
> or a real machine.
> 
> the 12 failures in 305 pushes is slightly misleading.  It over reports as we
> have >1 failure in some pushes, but in many cases we do not run the tests
> for every push, instead we run every 5th push.  

Is that really true for Linux/linux64 debug mochitest-e10s-bc ? I retriggered the offending bc6 runs in both trypushes 30 times last night and this morning they're all green. How many retriggers do I need to see a difference? :-\
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(jmaher)
based on the data from 2 weeks ago when I flagged this bug the 30 retriggers would have been enough.  In the last week we have only seen this 10 times vs 38 times.  I don't know why this has been reduced in frequency, there is no clear pattern in the orange factor data.  I did verify that bc6 is the right one job to be retriggering- it seems that this test hops around the browser-chrome chunks a lot- I wonder if it is being affected by a test run previously and now is just sitting in the ideal chunk.

based on the current failure rate it might be more like 60-75 retriggers :(
Flags: needinfo?(jmaher)

Comment 32

2 years ago
(In reply to Joel Maher ( :jmaher) from comment #31)
> based on the data from 2 weeks ago when I flagged this bug the 30 retriggers
> would have been enough.  In the last week we have only seen this 10 times vs
> 38 times.  I don't know why this has been reduced in frequency, there is no
> clear pattern in the orange factor data.  I did verify that bc6 is the right
> one job to be retriggering- it seems that this test hops around the
> browser-chrome chunks a lot- I wonder if it is being affected by a test run
> previously and now is just sitting in the ideal chunk.

I guess it's kind of a small chunk so maybe that's why? https://dxr.mozilla.org/mozilla-central/source/toolkit/components/tooltiptext/tests/ 

> based on the current failure rate it might be more like 60-75 retriggers :(

To hit it once? Hm, I guess I'll do 30 retriggers on each now and then another 30 tomorrow morning or something, to avoid hogging try capacity.
Flags: needinfo?(gijskruitbosch+bugs)

Comment 33

2 years ago
After running 60 times, there's 0 hits on the try run with the existing timeout and 1 hit on the try run with the longer timeout (so that won't help), but this also seems to now be lower frequency again so maybe we can just not do anything for now. Going to clear my ni. If Jared has an idea we can pursue it, otherwise I suggest we wait until/unless this becomes higher frequency again.
Flags: needinfo?(gijskruitbosch+bugs)
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)
Yeah, this is quite low (1.3%, 00.8%, and 00.8% for the last three weeks). I don't think it's worth the effort at this point.
Flags: needinfo?(jaws)
Comment hidden (Intermittent Failures Robot)
Whiteboard: [stockwell unknown]
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)
Most starring of this bug is against non-e10s now -> Bug title updated
Summary: Intermittent e10s browser_input_file_tooltips.js | Test timed out → Intermittent browser_input_file_tooltips.js | Test timed out
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)
See Also: → 1400368
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)
You need to log in before you can comment on or make changes to this bug.