Open Bug 1308377 Opened 9 years ago Updated 3 years ago

Intermittent non-Win 8 browser/base/content/test/general/browser_tab_dragdrop2.js | Test timed out -

Categories

(Firefox :: Tabbed Browser, defect, P3)

Product:
Firefox
Component:
Tabbed Browser
Type:
defect

Tracking

()

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])

Component: General → Tabbed Browser
Priority: -- → P3
As of November 2th, it seems this started happening more frequently. :dao, can you look into this or find someone to look into it in the near future? I see this is a P3, but it is our #2 intermittent orange in the last week.
Flags: needinfo?(dao+bmo)
(In reply to Joel Maher ( :jmaher) from comment #10) > As of November 2th, it seems this started happening more frequently. Do you have a more specific regression range, ideally two revisions that we can use to see if something suspicious landed making this more frequent? > :dao, can you look into this or find someone to look into it in the near future? Mats? You added this test in bug 449734, apparently without review :( Tim also kindly rewrote this test in bug 1041297 but he doesn't work on this code anymore.
Flags: needinfo?(mats)
Flags: needinfo?(jmaher)
Flags: needinfo?(dao+bmo)
Sorry, I don't have time to investigate this.
Flags: needinfo?(mats)
here is the range: https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=browser-chrome-e10s-7%20linux64%20debug&tochange=0124edce0553b43a9c320356fa9d1c175bb352c5&fromchange=86529c84da06979e8f9d859e161c7c0c1e16d91f suspiciously we enabled dragdrop.js (not dragdrop2.js) where this started failing. This test is the immediate test prior to dragdrop2.js- I suspect there are issues there. :jaws, did you test out the dragdrop.js and how it might affect dragdrop2.js? Possibly that is just coincidence.
Flags: needinfo?(jmaher) → needinfo?(jaws)
(In reply to Joel Maher ( :jmaher) from comment #13) > here is the range: > https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=browser- > chrome-e10s- > 7%20linux64%20debug&tochange=0124edce0553b43a9c320356fa9d1c175bb352c5&fromcha > nge=86529c84da06979e8f9d859e161c7c0c1e16d91f > > suspiciously we enabled dragdrop.js (not dragdrop2.js) where this started > failing. This test is the immediate test prior to dragdrop2.js- I suspect > there are issues there. Yep, yesterday I tried disabling browser_tab_dragdrop2.js and then browser_tabfocus.js started timing out: https://treeherder.mozilla.org/#/jobs?repo=try&revision=34849d6c556f16599e4079c9d88bccd0d7fdcfea So this is an issue with the previous test, browser_tab_dragdrop.js.
Flags: needinfo?(jaws)
Blocks: 1312436
thanks :dao!
:dao, this is showing up often in linux64 opt/pgo in e10s. I am not a fan of always disabling tests- not sure if you have some cycles to look into this? Please do ask for any information if you need it or want to see stuff that I could gather easily.
Flags: needinfo?(dao+bmo)
It looks like the test times out before we get any results, i.e. here: add_task(function* () { // Open a new window. let args = "chrome,all,dialog=no"; let win = window.openDialog(getBrowserURL(), "_blank", args, URI); // Wait until the tests were run. >> yield promiseTestsDone(win); ok(true, "tests succeeded"); This would mean that browser_tab_dragdrop2_frame1.xul either 1) failed to load, or 2) failed to dispatch the TestsDone event, or 3) the page loaded and the event got dispatched before we could add the listener. I would think / hope that (3) isn't possible, otherwise this would be a Gecko bug. Here's a screenshot of the failed test that looks like (1) rather than (2) but I can't explain why this would happen: https://public-artifacts.taskcluster.net/FClrL0vnRHyPHKzmI27CSw/0/public/test_info//mozilla-test-fail-screenshot_6vuHs0.png
Flags: needinfo?(dao+bmo)
o, this is failing on test_dragdrop.js: [task 2017-01-07T22:23:02.687931Z] 22:23:02 INFO - TEST-START | browser/base/content/test/general/browser_tab_dragdrop.js [task 2017-01-07T22:23:04.016046Z] 22:23:04 INFO - Xlib: extension "RANDR" missing on display ":0". [task 2017-01-07T22:23:07.092319Z] 22:23:07 INFO - [NPAPI 2259] ###!!! ASSERTION: plug removed: 'glib assertion', file /home/worker/workspace/build/src/toolkit/xre/nsSigHandlers.cpp, line 140 [task 2017-01-07T22:23:07.096937Z] 22:23:07 INFO - #01: g_logv[/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x4ef61] [task 2017-01-07T22:23:07.098889Z] 22:23:07 INFO - #02: g_log[/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x4f172] [task 2017-01-07T22:23:07.100689Z] 22:23:07 INFO - #03: ???[/tmp/tmpjsvq43.mozrunner/plugins/libnptest.so +0x70f4] [task 2017-01-07T22:23:07.111387Z] 22:23:07 INFO - #04: ???[/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x136e78] [task 2017-01-07T22:23:07.113205Z] 22:23:07 INFO - #05: g_closure_invoke[/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0xfca2] [task 2017-01-07T22:23:07.116221Z] 22:23:07 INFO - #06: ???[/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x20d71] [task 2017-01-07T22:23:07.118358Z] 22:23:07 INFO - #07: g_signal_emit_valist[/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x28d4e] [task 2017-01-07T22:23:07.120598Z] 22:23:07 INFO - #08: g_signal_emit[/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x29212] [task 2017-01-07T22:23:07.122961Z] 22:23:07 INFO - #09: ???[/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x251231] [task 2017-01-07T22:23:07.127270Z] 22:23:07 INFO - #10: ???[/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x16a147] [task 2017-01-07T22:23:07.133356Z] 22:23:07 INFO - #11: ???[/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x2c92fa] [task 2017-01-07T22:23:07.141536Z] 22:23:07 INFO - #12: ???[/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x597c1] [task 2017-01-07T22:23:07.155815Z] 22:23:07 INFO - #13: ???[/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x5a2aa] [task 2017-01-07T22:23:07.161954Z] 22:23:07 INFO - #14: ???[/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x5bd96] [task 2017-01-07T22:23:07.164293Z] 22:23:07 INFO - #15: ???[/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x5be3e] [task 2017-01-07T22:23:07.170616Z] 22:23:07 INFO - #16: g_main_context_dispatch[/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x47d13] [task 2017-01-07T22:23:07.177790Z] 22:23:07 INFO - #17: ???[/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x48060] [task 2017-01-07T22:23:07.180146Z] 22:23:07 INFO - #18: g_main_context_iteration[/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x48124] [task 2017-01-07T22:23:07.182807Z] 22:23:07 INFO - #19: ???[/home/worker/workspace/build/application/firefox/libxul.so +0xbfd6ff] [task 2017-01-07T22:23:07.185169Z] 22:23:07 INFO - #20: ???[/home/worker/workspace/build/application/firefox/libxul.so +0x32deca7] [task 2017-01-07T22:23:07.189167Z] 22:23:07 INFO - #21: XRE_InitChildProcess[/home/worker/workspace/build/application/firefox/libxul.so +0x218dc46] [task 2017-01-07T22:23:07.197755Z] 22:23:07 INFO - #22: ???[/home/worker/workspace/build/application/firefox/plugin-container +0xe5f3] [task 2017-01-07T22:23:07.203709Z] 22:23:07 INFO - #23: __libc_start_main[/lib/x86_64-linux-gnu/libc.so.6 +0x217ed] [task 2017-01-07T22:23:07.206294Z] 22:23:07 INFO - #24: ???[/home/worker/workspace/build/application/firefox/plugin-container +0xe45d] [task 2017-01-07T22:23:07.210210Z] 22:23:07 INFO - ** (/home/worker/workspace/build/application/firefox/plugin-container:2259): ERROR **: plug removed [task 2017-01-07T22:23:07.402587Z] 22:23:07 INFO - MEMORY STAT | vsize 1705MB | residentFast 474MB | heapAllocated 209MB [task 2017-01-07T22:23:07.406531Z] 22:23:07 INFO - TEST-OK | browser/base/content/test/general/browser_tab_dragdrop.js | took 4717ms [task 2017-01-07T22:23:07.495609Z] 22:23:07 INFO - checking window state it looks like we need to fix this problem first and I suspect all issues with this test will go away.
(In reply to Joel Maher ( :jmaher) from comment #29) > o, this is failing on test_dragdrop.js: It's quite possible if not likely that browser_tab_dragdrop.js is to blame. However I don't see any test failure in the log that you posted.
correct, I don't see a specific failure, but the assertion and stack are very questionable.
Not sure what that's about. My first guess would be that it's unrelated.
when we do not have a failure, the browser_dragdrop.js doesn't hit the assertion, nor the stack.
Depends on: 1331904
Looks like something made this failure more frequent again.
the rate of failures has been reduced a bit, although I don't have a lot of faith this is really fixed.
ok, we are 3 weeks in a row where this is a high frequency failure (>30 failures/week). I would like to get this resolved in the next 2 weeks one way or another. The failures are on opt/pgo e10s (not debug at all). a most recent failure from [0], yields this in the log: [task 2017-02-04T10:24:49.235011Z] 10:24:49 INFO - TEST-START | browser/base/content/test/general/browser_tab_dragdrop2.js [task 2017-02-04T10:25:34.285236Z] 10:25:34 INFO - TEST-INFO | started process screentopng [task 2017-02-04T10:25:35.795158Z] 10:25:35 INFO - TEST-INFO | screentopng: exit 0 [task 2017-02-04T10:25:35.802159Z] 10:25:35 INFO - Buffered messages logged at 10:24:49 [task 2017-02-04T10:25:35.802438Z] 10:25:35 INFO - Entering test bound [task 2017-02-04T10:25:35.802649Z] 10:25:35 INFO - Waiting for TestsDone [task 2017-02-04T10:25:35.802859Z] 10:25:35 INFO - Buffered messages finished [task 2017-02-04T10:25:35.803217Z] 10:25:35 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_tab_dragdrop2.js | Test timed out - [task 2017-02-04T10:25:35.805362Z] 10:25:35 INFO - MEMORY STAT | vsize 1736MB | residentFast 405MB | heapAllocated 173MB [task 2017-02-04T10:25:35.808785Z] 10:25:35 INFO - TEST-OK | browser/base/content/test/general/browser_tab_dragdrop2.js | took 45145ms [task 2017-02-04T10:25:35.810761Z] 10:25:35 INFO - checking window state [task 2017-02-04T10:25:35.814004Z] 10:25:35 INFO - Not taking screenshot here: see the one that was previously logged [task 2017-02-04T10:25:35.816000Z] 10:25:35 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_tab_dragdrop2.js | Found a browser window after previous test timed out - [task 2017-02-04T10:25:38.792981Z] 10:25:38 INFO - Console message: [JavaScript Error: "1486203938741 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://127.0.0.1:8888/telemetry-dummy//submit/telemetry/4a3d70c4-57b7-4cd8-a2f7-ff4d33134a97/main/Firefox/54.0a1/default/20170204094231?v=4: timeout" {file: "resource://gre/modules/Log.jsm" line: 748}] <and many more traceback messages...> and this screenshot: https://public-artifacts.taskcluster.net/D8i6RhwZTpSpkQBwfDrwnA/0/public/test_info//mozilla-test-fail-screenshot_hBKWCe.png this looks like we are not loading anything, I recall :gbrown looking into some tests not loading a tab, possibly he could take a brief look to see if this is similar. I also wonder if these javascript errors we get happen at the right time and prevent things from loading or other events from happening, in this case it is an error for the telemetry ping as we give it a fake server.
Flags: needinfo?(gbrown)
:dao, also ni you as you might have more ideas on this or could help find someone to work on this so we can get it resolved in the next 2 weeks.
Flags: needinfo?(dao+bmo)
(In reply to Joel Maher ( :jmaher) from comment #43) > :dao, also ni you as you might have more ideas on this or could help find > someone to work on this so we can get it resolved in the next 2 weeks. I filed bug 1331904 based on our earlier discussion here. Let's focus on moving that bug forward.
Flags: needinfo?(dao+bmo)
Thanks, but not similar to the issue I am tracking.
Flags: needinfo?(gbrown)
this magically became fixed
Whiteboard: [stockwell unknown]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.