Closed
Bug 1544536
(jsreftest-android-timeout)
Opened 6 years ago
Closed 5 years ago
Intermittent Android 4.3 http://10.0.2.2:8854/jsreftest/tests/jsreftest.html?test =... | application crashed [@ libc.so + 0x1c3dc] after "application timed out after 370 seconds with no output"
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jorendorff, Unassigned)
References
Details
Crash Data
Sometimes jsreftests time out on Android, with the following symptoms:
-
Android 4.3.
-
The number of reports is small.
-
The test being blamed actually passed, as indicated by
REFTEST INFO | Result summary:
with nothingUnexpected
andREFTEST SUITE-END | Shutdown
in the log. -
Subsequent output is like this:
[task 2019-03-27T07:17:14.743Z] 07:17:14 INFO - REFTEST SUITE-END | Shutdown [task 2019-03-27T07:17:14.743Z] 07:17:14 INFO - REFTEST INFO | Slowest test took 0ms (undefined) [task 2019-03-27T07:17:14.744Z] 07:17:14 INFO - REFTEST INFO | Total canvas count = 0 [task 2019-03-27T07:17:14.744Z] 07:17:14 INFO - REFTEST WARNING | Failed to find the test-plugin. [task 2019-03-27T07:17:14.744Z] 07:17:14 INFO - REFTEST WARNING | Failed to find the test-plugin. [task 2019-03-27T07:17:14.744Z] 07:17:14 INFO - REFTEST WARNING | Failed to get test plugin tags. [task 2019-03-27T07:23:53.925Z] 07:23:53 INFO - wait for org.mozilla.fennec_aurora complete; top activity=org.mozilla.fennec_aurora [task 2019-03-27T07:23:54.229Z] 07:23:54 INFO - org.mozilla.fennec_aurora unexpectedly found running. Killing... [task 2019-03-27T07:23:54.230Z] 07:23:54 INFO - REFTEST TEST-INFO | started process screentopng [task 2019-03-27T07:23:54.595Z] 07:23:54 INFO - REFTEST TEST-INFO | screentopng: exit 0 [task 2019-03-27T07:24:09.449Z] 07:24:09 WARNING - TEST-UNEXPECTED-FAIL | http://10.0.2.2:8854/jsreftest/tests/jsreftest.html?test=test262/built-ins/RegExp/property-escapes/generated/Script_Extensions_-_Old_Italic.js | application timed out after 370 seconds with no output [task 2019-03-27T07:24:09.449Z] 07:24:09 INFO - remoteautomation.py | Application ran for: 0:07:37.212425 [task 2019-03-27T07:24:10.266Z] 07:24:10 INFO - REFTEST INFO | Downloading symbols from: https://queue.taskcluster.net/v1/task/LeawknlESBufb9Xv8HZPzw/artifacts/public/build/target.crashreporter-symbols.zip [task 2019-03-27T07:24:13.723Z] 07:24:13 INFO - REFTEST INFO | Copy/paste: /builds/worker/workspace/build/linux64-minidump_stackwalk /tmp/tmpaeKu0R/7be2d250-ba39-4908-aed6-437c69bf7d4c.dmp /tmp/tmp57EOZM [task 2019-03-27T07:24:21.162Z] 07:24:21 INFO - REFTEST INFO | Saved minidump as /builds/worker/workspace/build/blobber_upload_dir/7be2d250-ba39-4908-aed6-437c69bf7d4c.dmp [task 2019-03-27T07:24:21.162Z] 07:24:21 INFO - REFTEST INFO | Saved app info as /builds/worker/workspace/build/blobber_upload_dir/7be2d250-ba39-4908-aed6-437c69bf7d4c.extra [task 2019-03-27T07:24:21.166Z] 07:24:21 INFO - REFTEST PROCESS-CRASH | http://10.0.2.2:8854/jsreftest/tests/jsreftest.html?test=test262/built-ins/RegExp/property-escapes/generated/Script_Extensions_-_Old_Italic.js | application crashed [@ libc.so + 0x1c3dc]
In particular,
-
Long pause after the three WARNING lines.
-
TEST-UNEXPECTED-FAIL | ... | application timed out after ... seconds with no output
appears in the log -
Crash at
[@ libc.so + 0x1c3dc]
.
I don't think it is a bug in the test suite or the JS engine. The test passes or is skipped.
Updated•6 years ago
|
Crash Signature: [@ libc.so + 0x1c3dc]
Reporter | ||
Updated•6 years ago
|
Type: task → defect
Component: JavaScript Engine → General
Product: Core → Taskcluster
Reporter | ||
Updated•6 years ago
|
Alias: jsreftest-android-timeout
Reporter | ||
Updated•6 years ago
|
Summary: Intermittent http://10.0.2.2:8854/jsreftest/tests/jsreftest.html?test=... | application crashed [@ libc.so + 0x1c3dc] after "application timed out after 370 seconds with no output" on Android → Intermittent Android 4.3 http://10.0.2.2:8854/jsreftest/tests/jsreftest.html?test=... | application crashed [@ libc.so + 0x1c3dc] after "application timed out after 370 seconds with no output"
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•