Closed Bug 1476817 Opened 8 years ago Closed 8 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | dom/canvas/test/webgl-conf/generated/test_conformance__textures__webgl_canvas__tex-2d-alpha-alpha-unsigned_byte.html | application timed out after 370 seconds with no output

Categories

(Core :: Graphics: CanvasWebGL, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1479666

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, Whiteboard: [TV-bf pass:pass])

Filed by: csabou [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=188839046&repo=autoland https://queue.taskcluster.net/v1/task/Ah9loGkqS0-it1PSDmB6IA/runs/0/artifacts/public/logs/live_backing.log 16:01:55 INFO - TEST-START | dom/canvas/test/webgl-conf/generated/test_conformance__textures__webgl_canvas__tex-2d-alpha-alpha-unsigned_byte.html 16:01:55 INFO - GECKO(748) | JavaScript error: , line 0: uncaught exception: out of memory 16:01:55 INFO - GECKO(748) | JavaScript error: http://mochi.test:8888/tests/dom/canvas/test/webgl-conf/mochi-single.html?checkout/conformance/textures/webgl_canvas/tex-2d-alpha-alpha-unsigned_byte.html, line 38: TypeError: parent.SimpleTest is undefined 16:08:05 INFO - Buffered messages finished 16:08:05 ERROR - TEST-UNEXPECTED-TIMEOUT | dom/canvas/test/webgl-conf/generated/test_conformance__textures__webgl_canvas__tex-2d-alpha-alpha-unsigned_byte.html | application timed out after 370 seconds with no output 16:08:05 ERROR - Force-terminating active process(es). 16:08:05 INFO - Determining child pids from psutil... 16:08:05 INFO - [752, 753, 754] 16:08:05 INFO - ==> process 748 launched child process 752 16:08:05 INFO - ==> process 748 launched child process 753 16:08:05 INFO - ==> process 748 launched child process 754 16:08:05 INFO - Found child pids: set([752, 753, 754]) 16:08:05 INFO - Killing process: 752 16:08:05 INFO - TEST-INFO | started process screencapture 16:08:05 INFO - TEST-INFO | screencapture: exit 0 16:08:05 INFO - Killing process: 753 16:08:05 INFO - Not taking screenshot here: see the one that was previously logged 16:08:05 INFO - Killing process: 754 16:08:05 INFO - Not taking screenshot here: see the one that was previously logged 16:08:05 INFO - psutil found pid 754 dead 16:08:05 INFO - psutil found pid 752 dead 16:08:05 INFO - psutil found pid 753 dead 16:08:05 INFO - Killing process: 748 16:08:05 INFO - Not taking screenshot here: see the one that was previously logged 16:08:06 INFO - psutil found pid 748 dead 16:08:06 WARNING - runtests.py | Failed to get app exit code - running/crashed? 16:08:06 INFO - TEST-INFO | Main app process: exit 0 16:08:06 INFO - runtests.py | Application ran for: 0:11:06.157848 16:08:06 INFO - zombiecheck | Reading PID log: /var/folders/l0/h1hr3djj5ml5p48mx_rl0_tw00000w/T/tmpxIcfD1pidlog 16:08:06 INFO - ==> process 748 launched child process 752 16:08:06 INFO - ==> process 748 launched child process 753 16:08:06 INFO - ==> process 748 launched child process 754 16:08:06 INFO - zombiecheck | Checking for orphan process with PID: 752 16:08:06 INFO - zombiecheck | Checking for orphan process with PID: 753 16:08:06 INFO - zombiecheck | Checking for orphan process with PID: 754 16:08:06 INFO - mozcrash Downloading symbols from: https://queue.taskcluster.net/v1/task/MzV7j4hnTUCZd2A3bB2vjg/artifacts/public/build/target.crashreporter-symbols.zip 16:08:18 INFO - mozcrash Copy/paste: /Users/cltbld/tasks/task_1531954449/build/macosx64-minidump_stackwalk /var/folders/l0/h1hr3djj5ml5p48mx_rl0_tw00000w/T/tmpdO1d1e.mozrunner/minidumps/03F16E0C-DA3A-4C93-83BF-4ADC6038F957.dmp /var/folders/l0/h1hr3djj5ml5p48mx_rl0_tw00000w/T/tmpgYiXqL 16:08:31 INFO - mozcrash Saved minidump as /Users/cltbld/tasks/task_1531954449/build/blobber_upload_dir/03F16E0C-DA3A-4C93-83BF-4ADC6038F957.dmp 16:08:31 INFO - mozcrash Saved app info as /Users/cltbld/tasks/task_1531954449/build/blobber_upload_dir/03F16E0C-DA3A-4C93-83BF-4ADC6038F957.extra
Dear Reader, We are a joint research team from the University of Zurich, Switzerland* and Mozilla** and are building a tool to automatically recognize the type of an intermittent-failure, such as the one here. By automatically recognizing the type of failure, the tool should provide a starting point for the bug fixing process. To evaluate and improve the tool, we kindly ask your feedback. Tool Result - this intermittent-failure is most likely affected by a: Concurrency Issue: This includes tests in which failures occur due to thread management issues (different threads or their outcomes depending on an implicit ordering), race conditions and/or deadlocks, and issues related to an asynchronous waits (e.g. a process trying to access an external resource or continuing before the external resource is available). Feedback: 1. Did the tool correctly recognize the type of intermittent-failure? (please also explain why or why not) 2. Did the information from the tool help your analysis, the bug fixing process, or anything in the process? (please also let us know how the tool was useful and/or what would improve the tool's usefulness for you) Thank you very much for your help! *Moritz, Fabio and Alberto (http://www.ifi.uzh.ch/en/zest/team.html) **Marco Castellucio (https://marco-c.github.io/)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.