Closed Bug 1080100 Opened 10 years ago Closed 11 months ago

Intermittent test_bug343416.xhtml,test_bug343416.xul | We added a listener and it should have been called by now.

Categories

(Core :: Widget, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure, regression, Whiteboard: tpi:-)

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

builder 	Ubuntu VM 12.04 fx-team debug test mochitest-other
buildid 	20141008073405
builduid 	3a63e7532ba14ecaa3bf371c86dd03fd
results 	warnings (1)
revision 	116b905fd605
slave 		tst-linux32-spot-232
starttime 	Wed Oct 08 2014 11:58:12 GMT-0400 (Eastern Standard Time)

09:50:15 INFO - 2475 INFO TEST-START | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul
09:50:15 INFO - ++DOMWINDOW == 471 (0x7150f110) [pid = 1832] [serial = 5850] [outer = 0x9bcd8950]
09:50:24 INFO - [Parent 1832] WARNING: Detected really long delay between samples, continuing from previous sample: file /builds/slave/fx-team-lx-d-00000000000000000/build/dom/smil/nsSMILAnimationController.cpp, line 147
09:50:27 INFO - 2476 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | nsIIdleService should exist and be implemented on all tier 1 platforms.
09:50:27 INFO - 2477 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | Getting the idle time should not fail in normal circumstances on any tier 1 platform.
09:50:27 INFO - 2478 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | The nsIIdleService should allow us to add an observer.
09:50:27 INFO - 2479 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | The nsIIdleService should allow us to add the same observer again.
09:50:27 INFO - 2480 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | The nsIIdleService should allow us to remove the observer just once.
09:50:27 INFO - 2481 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | Getting the idle time should not fail in normal circumstances on any tier 1 platform.
09:50:27 INFO - 2482 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | The idle time should have increased by roughly the amount of time it took for the timeout to fire. You didn't touch the mouse or keyboard during the test did you?
09:50:27 INFO - 2483 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | We set a timeout and it should have fired by now.
09:50:27 INFO - 2484 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/widget/tests/test_bug343416.xul | We added a listener and it should have been called by now. - expected PASS
This and bug 763894 combined make up one of the top contributors to a currently ~30% failure rate on Win8 mochitest-other. As the original test author, any chance you can take a look, Gijs? Otherwise, suggestions for who might? :)
Flags: needinfo?(gijskruitbosch+bugs)
See Also: → 763894
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #202)
> This and bug 763894 combined make up one of the top contributors to a
> currently ~30% failure rate on Win8 mochitest-other. As the original test
> author, any chance you can take a look, Gijs? Otherwise, suggestions for who
> might? :)

The test is failing because of setTimeout issues.

In 99.9% of cases the failures are on debug (one bug has exactly 1 opt failure, in the other the last failure was in January). I think we should disable the test on debug, which is almost as good as rewriting it but takes a fraction of the time. I would have just landed that skip-if, but the tree is closed. needinfo? back to you to disable it when you reopen the tree. :-)
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(ryanvm)
Whiteboard: tpi:-
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression
Summary: Intermittent test_bug343416.xul | We added a listener and it should have been called by now. → Intermittent test_bug343416.xhtml,test_bug343416.xul | We added a listener and it should have been called by now.
Severity: normal → S3

I got a profile of the failure on my local mac build: https://share.firefox.dev/3IpQYsU
This was captured with MOZ_PROFILER_STARTUP_FILTERS="GeckoMain,Timer" ./mach test widget/tests/test_bug343416.xhtml --profiler --run-until-failure.

(In reply to Florian Quèze [:florian] from comment #370)

I got a profile of the failure on my local mac build: https://share.firefox.dev/3IpQYsU

I have not been able to reproduce since that, despite trying many times. There's a context menu that opened before the test that failed. Given my cat was on the desk when I left the office after launching the tests, I'm starting to wonder if the cat might have stepped on the touchpad and disturbed the test.

My try push, where I re-enabled the test on debug builds, also didn't reproduce: https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=4a83ffdd7b34a6907d31cc178919461e56129b33

Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.