Closed
Bug 1466264
Opened 7 years ago
Closed 7 years ago
Intermittent testing/marionette/harness/marionette_harness/tests/unit/test_navigation.py TestRefresh.test_timeout_error | application crashed [@ dalvik-jit-code-cache (deleted) + 0x2bbc]
Categories
(Testing :: Marionette Client and Harness, defect, P5)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1454680
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: crash, intermittent-failure)
Crash Data
Filed by: rgurzau [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=181441193&repo=mozilla-inbound
https://queue.taskcluster.net/v1/task/eP32IhcvQxWhj_TobCCaBw/runs/0/artifacts/public/logs/live_backing.log
[task 2018-06-01T23:00:12.552Z] 23:00:12 INFO - TEST-START | testing/marionette/harness/marionette_harness/tests/unit/test_navigation.py TestRefresh.test_timeout_error
[task 2018-06-01T23:00:19.844Z] 23:00:19 INFO - mozcrash Copy/paste: /usr/local/bin/linux64-minidump_stackwalk /tmp/tmp5VtkdF/482a3db3-c989-683e-6e93-7164ccf72274.dmp /builds/worker/workspace/build/symbols
[task 2018-06-01T23:00:29.268Z] 23:00:29 INFO - mozcrash Saved minidump as /builds/worker/workspace/build/blobber_upload_dir/482a3db3-c989-683e-6e93-7164ccf72274.dmp
[task 2018-06-01T23:00:29.268Z] 23:00:29 INFO - mozcrash Saved app info as /builds/worker/workspace/build/blobber_upload_dir/482a3db3-c989-683e-6e93-7164ccf72274.extra
[task 2018-06-01T23:00:29.271Z] 23:00:29 WARNING - PROCESS-CRASH | testing/marionette/harness/marionette_harness/tests/unit/test_navigation.py TestRefresh.test_timeout_error | application crashed [@ dalvik-jit-code-cache (deleted) + 0x2bbc]
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Comment hidden (Intermittent Failures Robot) |
Updated•2 years ago
|
Product: Testing → Remote Protocol
Comment 3•2 years ago
|
||
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in
before you can comment on or make changes to this bug.
Description
•