Closed Bug 1525653 Opened 4 years ago Closed 4 years ago

win/1803 - dom/events/test/test_bug1298970.html | application timed out after 370 seconds with no output

Categories

(Core :: DOM: Events, defect, P3)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: egao, Unassigned)

References

Details

Treeherder: https://treeherder.mozilla.org/#/jobs?repo=try&revision=7f2edbc029097dc7ca3c14f2ae488e4d7275d147&selectedJob=226341275

Taskcluster: https://tools.taskcluster.net/groups/efMBjsn0Q66A2tvOdHEHDw/tasks/OcM-2T5JTmiUahD8T-bQsg/details

Filing new issues from first win10/aarch64 run of mochitest-e10s-1.

10:30:10    ERROR - TEST-UNEXPECTED-TIMEOUT | dom/events/test/test_bug1298970.html | application timed out after 370 seconds with no output
10:30:10    ERROR - Force-terminating active process(es).
10:30:10     INFO - Determining child pids from psutil...
10:30:10     INFO - [1248]
10:30:10     INFO - ==> process 1248 launched child process 5948 ("C:\tasks\task_1549447030\build\application\firefox\firefox.exe" -contentproc --channel="1248.0.1317754135\2035641941" -parentBuildID 20190205155112 -greomni "C:\tasks\task_1549447030\build\application\firefox\omni.ja" -appomni "C:\tasks\task_1549447030\build\application\firefox\browser\omni.ja" -appdir "C:\tasks\task_1549447030\build\application\firefox\browser" - 1248 "\\.\pipe\gecko-crash-server-pipe.1248" 2540 gpu)
10:30:10     INFO - ==> process 1248 launched child process 6304 ("C:\tasks\task_1549447030\build\application\firefox\firefox.exe" -contentproc --channel="1248.6.1396511988\675957025" -childID 1 -isForBrowser -prefsHandle 1828 -prefMapHandle 1628 -prefsLen 1 -prefMapSize 193547 -parentBuildID 20190205155112 -greomni "C:\tasks\task_1549447030\build\application\firefox\omni.ja" -appomni "C:\tasks\task_1549447030\build\application\firefox\browser\omni.ja" -appdir "C:\tasks\task_1549447030\build\application\firefox\browser" - 1248 "\\.\pipe\gecko-crash-server-pipe.1248" 1776 tab)
10:30:10     INFO - ==> process 1248 launched child process 7164 ("C:\tasks\task_1549447030\build\application\firefox\firefox.exe" -contentproc --channel="1248.13.1491996147\811567771" -childID 2 -isForBrowser -prefsHandle 2216 -prefMapHandle 2676 -prefsLen 132 -prefMapSize 193547 -parentBuildID 20190205155112 -greomni "C:\tasks\task_1549447030\build\application\firefox\omni.ja" -appomni "C:\tasks\task_1549447030\build\application\firefox\browser\omni.ja" -appdir "C:\tasks\task_1549447030\build\application\firefox\browser" - 1248 "\\.\pipe\gecko-crash-server-pipe.1248" 2916 tab)
10:30:10     INFO - ==> process 1248 launched child process 10660 ("C:\tasks\task_1549447030\build\application\firefox\firefox.exe" -contentproc --channel="1248.20.353059395\1332400436" -childID 3 -isForBrowser -prefsHandle 3028 -prefMapHandle 3208 -prefsLen 132 -prefMapSize 193547 -parentBuildID 20190205155112 -greomni "C:\tasks\task_1549447030\build\application\firefox\omni.ja" -appomni "C:\tasks\task_1549447030\build\application\firefox\browser\omni.ja" -appdir "C:\tasks\task_1549447030\build\application\firefox\browser" - 1248 "\\.\pipe\gecko-crash-server-pipe.1248" 3216 tab)
10:30:10     INFO - Found child pids: set([1248, 6304, 10660, 5948, 7164])
10:30:10     INFO - Killing process: 1248
10:30:10     INFO - Not taking screenshot here: see the one that was previously logged
10:30:10     INFO - mozcrash Using C:\tasks\task_1549447030\build\tests\bin\minidumpwriter.exe to write a dump to c:\users\testdr~1\appdata\local\temp\tmpaho_fm.mozrunner\minidumps\9b7b7c36-484b-4b50-9362-4b96f81564fe.dmp for [1248]
10:30:10     INFO - Killing process: 6304
10:30:10     INFO - Not taking screenshot here: see the one that was previously logged
10:30:10     INFO - mozcrash Using C:\tasks\task_1549447030\build\tests\bin\minidumpwriter.exe to write a dump to c:\users\testdr~1\appdata\local\temp\tmpaho_fm.mozrunner\minidumps\8cef042c-a2e7-46ef-bff8-9043383822b5.dmp for [6304]
10:30:10     INFO -  Couldn't get handle for 6304
10:30:10    ERROR - mozcrash minidumpwriter exited with status: 1
10:30:10  WARNING - mozcrash kill_pid(): unable to get handle for pid 6304: 87
10:30:10     INFO - Killing process: 10660
10:30:10     INFO - Not taking screenshot here: see the one that was previously logged
10:30:10     INFO - mozcrash Using C:\tasks\task_1549447030\build\tests\bin\minidumpwriter.exe to write a dump to c:\users\testdr~1\appdata\local\temp\tmpaho_fm.mozrunner\minidumps\091cabbf-8bfe-4956-9d6a-ec859fbec34e.dmp for [10660]
10:30:10     INFO -  Couldn't get handle for 10660
10:30:10    ERROR - mozcrash minidumpwriter exited with status: 1
10:30:10  WARNING - mozcrash kill_pid(): unable to get handle for pid 10660: 87
10:30:10     INFO - Killing process: 5948
10:30:10     INFO - Not taking screenshot here: see the one that was previously logged
10:30:10     INFO - mozcrash Using C:\tasks\task_1549447030\build\tests\bin\minidumpwriter.exe to write a dump to c:\users\testdr~1\appdata\local\temp\tmpaho_fm.mozrunner\minidumps\6d288a2e-ce7f-4a30-9f08-4ebfc9d32fa7.dmp for [5948]
10:30:10     INFO -  Couldn't get handle for 5948
10:30:10    ERROR - mozcrash minidumpwriter exited with status: 1
10:30:10  WARNING - mozcrash kill_pid(): unable to get handle for pid 5948: 87
10:30:10     INFO - Killing process: 7164
10:30:10     INFO - Not taking screenshot here: see the one that was previously logged
10:30:10     INFO - mozcrash Using C:\tasks\task_1549447030\build\tests\bin\minidumpwriter.exe to write a dump to c:\users\testdr~1\appdata\local\temp\tmpaho_fm.mozrunner\minidumps\50e94c32-3b40-456f-b9cb-3570ec057d8c.dmp for [7164]
10:30:10     INFO -  Couldn't get handle for 7164
10:30:10    ERROR - mozcrash minidumpwriter exited with status: 1
10:30:10  WARNING - mozcrash kill_pid(): unable to get handle for pid 7164: 87
10:30:10     INFO - psutil found pid 5948 dead
10:30:10     INFO - psutil found pid 6304 dead
10:30:10     INFO - psutil found pid 1248 dead
10:30:10     INFO - psutil found pid 7164 dead
10:30:10     INFO - psutil found pid 10660 dead
10:30:10     INFO - Killing process: 10288
10:30:10     INFO - Not taking screenshot here: see the one that was previously logged
10:30:10     INFO - mozcrash Using C:\tasks\task_1549447030\build\tests\bin\minidumpwriter.exe to write a dump to c:\users\testdr~1\appdata\local\temp\tmpaho_fm.mozrunner\minidumps\70859720-31d5-4fff-abb4-b117816c432b.dmp for [10288]
10:30:10     INFO -  Error 0x8007012B in MiniDumpWriteDump
10:30:10    ERROR - mozcrash minidumpwriter exited with status: 1
10:30:10  WARNING - mozcrash kill_pid(): unable to terminate pid 10288: 5
10:30:10     INFO - psutil found pid 10288 dead
10:30:10     INFO - TEST-INFO | Main app process: exit 1
10:30:10     INFO - Buffered messages finished
10:30:10    ERROR - TEST-UNEXPECTED-FAIL | dom/events/test/test_bug1298970.html | application terminated with exit code 1

other failures on 1803:
test_bug1264380.html (debug only)

:hsinyi- these 4 tests will be disabled on windows 10 in order to get an upgrade done efficiently- I would be happy to help out with any additional information needed; can you help to at least get this to the right people so they are aware we are losing some test coverage?

Blocks: 1522900
Flags: needinfo?(htsai)
Summary: TEST-UNEXPECTED-TIMEOUT | dom/events/test/test_bug1298970.html | application timed out after 370 seconds with no output → win/1803 - dom/events/test/test_bug1298970.html | application timed out after 370 seconds with no output

Hi Joel, thanks for letting the team and me know!

Flags: needinfo?(htsai)
Priority: -- → P3

Hmm, I really don't understand why those synchronous tests fail...

test_bug1298970.html is a test for creates a new untrusted event, dispatches it and then, receives it with a event listener.

test_bug1305458.html is a synchronous test except load event.

test_bug1304044.html is also a synchronous test even though this tests more complicated path of implementation though.

Finally, test_bug1264380.html passes according to the first log of comment 1. Did you paste wrong file name here?

Joel, can you take a look at comment 4?

Flags: needinfo?(jmaher)

I see test_bug1264380.html failing on the above try push in one of the logs:
https://taskcluster-artifacts.net/RG4uc-tLQaScdfonEUvViQ/0/public/logs/live_backing.log

possibly this was a rare failure case and it doesn't fail all the time- the other tests seem to be failing most if not all of the time.

Flags: needinfo?(jmaher)

ok, I had accidentally turned off the mouse and screen resolution script causing this test to fail- re-enabling in bug 1527369

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