Open Bug 1941110 Opened 1 month ago Updated 2 days ago

Intermittent dom/events/test/test_all_synthetic_events.html (finished) | single tracking bug

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P5)

defect

Tracking

()

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, intermittent-testcase)

Filed by: sstanca [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=489725967&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/YrQx-eddSqu_0zhUYAPnNQ/runs/0/artifacts/public/logs/live_backing.log


[task 2025-01-11T11:00:15.918Z] 11:00:15     INFO - TEST-OK | dom/events/test/test_all_synthetic_events.html | took 150ms
[task 2025-01-11T11:06:25.976Z] 11:06:25     INFO - TEST-UNEXPECTED-TIMEOUT | dom/events/test/test_all_synthetic_events.html (finished) | application timed out after 370 seconds with no output
[task 2025-01-11T11:06:25.976Z] 11:06:25     INFO - TEST-INFO 
[task 2025-01-11T11:06:25.977Z] 11:06:25     INFO - Buffered messages finished
[task 2025-01-11T11:06:25.977Z] 11:06:25  WARNING - Force-terminating active process(es).
[task 2025-01-11T11:06:25.978Z] 11:06:25  WARNING - profiler Attempting to start the profiler to help with diagnosing the hang.
[task 2025-01-11T11:06:25.978Z] 11:06:25     INFO - profiler Sending SIGUSR1 to pid 1322 start the profiler.
[task 2025-01-11T11:06:25.979Z] 11:06:25     INFO - profiler Waiting 10s to capture a profile...
[task 2025-01-11T11:06:36.106Z] 11:06:36     INFO - profiler Sending SIGUSR2 to pid 1322 stop the profiler.
[task 2025-01-11T11:06:36.107Z] 11:06:36     INFO - profiler Wait 10s for Firefox to write the profile to disk.
[task 2025-01-11T11:06:46.158Z] 11:06:46     INFO - profiler Symbolicating profile in /opt/worker/tasks/task_173659285577547/build/blobber_upload_dir
[task 2025-01-11T11:06:46.159Z] 11:06:46     INFO - profiler Looking inside symbols dir: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GV0NCdn2RK6q4XTgf-ptuA/artifacts/public/build/target.crashreporter-symbols.zip)
[task 2025-01-11T11:06:46.159Z] 11:06:46     INFO - profiler Symbolicating profile: /opt/worker/tasks/task_173659285577547/build/blobber_upload_dir/profile_0_1322.json
[task 2025-01-11T11:06:46.160Z] 11:06:46     INFO - profiler Symbolicating the performance profile... This could take a couple of minutes.
[task 2025-01-11T11:06:47.376Z] 11:06:47     INFO - Determining child pids from psutil...
[task 2025-01-11T11:06:47.382Z] 11:06:47     INFO - [1324, 1325, 1333, 1334, 1336, 1340]
[task 2025-01-11T11:06:47.383Z] 11:06:47     INFO - ==> process 1322 launched child process 1324
[task 2025-01-11T11:06:47.383Z] 11:06:47     INFO - ==> process 1322 launched child process 1325
[task 2025-01-11T11:06:47.383Z] 11:06:47     INFO - ==> process 1322 launched child process 1326
[task 2025-01-11T11:06:47.384Z] 11:06:47     INFO - ==> process 1322 launched child process 1333
[task 2025-01-11T11:06:47.384Z] 11:06:47     INFO - ==> process 1322 launched child process 1334
[task 2025-01-11T11:06:47.384Z] 11:06:47     INFO - ==> process 1322 launched child process 1335
[task 2025-01-11T11:06:47.385Z] 11:06:47     INFO - ==> process 1322 launched child process 1336
[task 2025-01-11T11:06:47.385Z] 11:06:47     INFO - ==> process 1322 launched child process 1337
[task 2025-01-11T11:06:47.385Z] 11:06:47     INFO - ==> process 1322 launched child process 1338
[task 2025-01-11T11:06:47.386Z] 11:06:47     INFO - ==> process 1322 launched child process 1339
[task 2025-01-11T11:06:47.386Z] 11:06:47     INFO - ==> process 1322 launched child process 1340
[task 2025-01-11T11:06:47.386Z] 11:06:47     INFO - Found child pids: {1324, 1325, 1326, 1333, 1334, 1335, 1336, 1337, 1338, 1339, 1340}
[task 2025-01-11T11:06:47.387Z] 11:06:47     INFO - Failed to get child procs
[task 2025-01-11T11:06:47.387Z] 11:06:47     INFO - Killing process: 1324
[task 2025-01-11T11:06:47.387Z] 11:06:47     INFO - TEST-INFO | started process screencapture
[task 2025-01-11T11:06:47.566Z] 11:06:47     INFO - TEST-INFO | screencapture: exit 0
You need to log in before you can comment on or make changes to this bug.