1518719 - Intermittent android tests/jit-test/<randomtest> | error: device '<serial no>' not found (code 1, args "") [0.1 s]

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Testing, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: rmaries [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=220748078&repo=mozilla-central

https://queue.taskcluster.net/v1/task/S6e-ItFOQSqEIvQQglEbHA/runs/0/artifacts/public/logs/live_backing.log

04:32:23 INFO - TEST-PASS | tests/jit-test/jit-test/tests/ion/bug807047.js | Success (code 0, args "--no-baseline --no-ion") [0.3 s]
04:32:23 INFO - {"action": "test_start", "jitflags": "--no-baseline --no-ion", "pid": 426, "source": "jittests", "test": "ion/bug807047.js", "thread": "main", "time": 1547008343.055773}
04:32:23 INFO - {"action": "test_end", "extra": {"jitflags": "--no-baseline --no-ion"}, "jitflags": "--no-baseline --no-ion", "message": "Success", "pid": 426, "source": "jittests", "status": "PASS", "test": "ion/bug807047.js", "thread": "main", "time": 1547008343.360729}
04:32:23 INFO - exception output: error: device 'FA84B1A00013' not found
04:32:23 INFO - error: device 'FA84B1A00013' not founderror: device 'FA84B1A00013' not foundExit code: 1
04:32:23 INFO - FAIL - ion/bug808023.js
04:32:23 WARNING - TEST-UNEXPECTED-FAIL | tests/jit-test/jit-test/tests/ion/bug808023.js | error: device 'FA84B1A00013' not found (code 1, args "") [0.1 s]
04:32:23 INFO - {"action": "test_start", "jitflags": "", "pid": 426, "source": "jittests", "test": "ion/bug808023.js", "thread": "main", "time": 1547008343.361875}
04:32:23 INFO - {"action": "test_end", "extra": {"jitflags": ""}, "jitflags": "", "message": "error: device 'FA84B1A00013' not found", "pid": 426, "source": "jittests", "status": "FAIL", "test": "ion/bug808023.js", "thread": "main", "time": 1547008343.466483}
04:32:23 INFO - INFO exit-status : 1
04:32:23 INFO - INFO timed-out : False
04:32:23 INFO - INFO stdout > error: device 'FA84B1A00013' not found
04:32:23 INFO - INFO stderr 2> error: device 'FA84B1A00013' not found
04:32:24 INFO - exception output: /data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js line 4 > eval:1:31 TypeError: t is not a function
04:32:24 INFO - Stack:
04:32:24 INFO - @/data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js line 4 > eval:1:31
04:32:24 INFO - f@/data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js:4:3
04:32:24 INFO - @/data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js:7:1
04:32:24 INFO - TEST-PASS | tests/jit-test/jit-test/tests/ion/bug808023.js | Success (code 3, args "--ion-eager --ion-offthread-compile=off") [1.3 s]
04:32:24 INFO - {"action": "test_start", "jitflags": "--ion-eager --ion-offthread-compile=off", "pid": 426, "source": "jittests", "test": "ion/bug808023.js", "thread": "main", "time": 1547008343.467589}
04:32:24 INFO - {"action": "test_end", "extra": {"jitflags": "--ion-eager --ion-offthread-compile=off"}, "jitflags": "--ion-eager --ion-offthread-compile=off", "message": "Success", "pid": 426, "source": "jittests", "status": "PASS", "test": "ion/bug808023.js", "thread": "main", "time": 1547008344.774633}
04:32:25 INFO - exception output: /data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js line 4 > eval:1:31 TypeError: t is not a function
04:32:25 INFO - Stack:
04:32:25 INFO - @/data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js line 4 > eval:1:31
04:32:25 INFO - f@/data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js:4:3
04:32:25 INFO - @/data/local/tests/jit-tests/jit-tests/tests/ion/bug808023.js:7:1

Comment 1

[Razvan Maries]

There is another similar bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1517932
Should we file a general bug for Android 8.0 Pixel2 opt Jit failures?

Comment 2

[Bob Clary [:bc] (inactive)]

The jit bugs with error: device 'FA84B1A00013' not found type messages mean the device has crashed in some way during the test. It is not clear to me that this is an intermittent device failure due to Android flakiness or is a result of the jit test crashing the device which might also be the problem.

I realize that the error messages aren't that helpful since they lead to independent bugs being filed for each separate device which could potentially be a separate bug for each of the current 28 pixel2 devices used in unit tests. Aryx and I have a project to help improve that but we are just beginning.

If you could use a single bug to track the jit error: device 'FA84B1A00013' not found type errors regardless of the device serial number that would be awesome.

Comment 4

[Intermittent Failures Robot]

3 failures in 2627 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 2
• mozilla-central: 1

Platform breakdown:

• android-hw-p2-8-0-android-aarch64: 2
• android-hw-p2-8-0-arm7-api-16: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-01-07&endday=2019-01-13&tree=all

Comment 8

[Intermittent Failures Robot]

8 failures in 2378 pushes (0.003 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 4
• mozilla-inbound: 2
• mozilla-central: 2

Platform breakdown:

• android-hw-p2-8-0-arm7-api-16: 4
• android-hw-p2-8-0-android-aarch64: 4

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-01-14&endday=2019-01-20&tree=all

Comment 10

[Intermittent Failures Robot]

10 failures in 2383 pushes (0.004 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• try: 2
• mozilla-inbound: 6
• autoland: 2

Platform breakdown:

• android-hw-p2-8-0-arm7-api-16: 5
• android-hw-p2-8-0-android-aarch64: 5

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-01-21&endday=2019-01-27&tree=all

Comment 12

[Intermittent Failures Robot]

4 failures in 2628 pushes (0.002 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 4

Platform breakdown:

• android-hw-p2-8-0-android-aarch64: 1
• android-hw-p2-8-0-arm7-api-16: 3

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-01-28&endday=2019-02-03&tree=all

Comment 14

[Intermittent Failures Robot]

10 failures in 2658 pushes (0.004 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 3
• mozilla-inbound: 7

Platform breakdown:

• android-hw-p2-8-0-arm7-api-16: 4
• android-hw-p2-8-0-android-aarch64: 6

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-02-04&endday=2019-02-10&tree=all

Comment 15

[Bob Clary [:bc] (inactive)]

Moving to Firefox for Android::Testing and resolving.

Comment 16

[Intermittent Failures Robot]

2 failures in 2832 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 1
• mozilla-beta: 1

Platform breakdown:

• android-hw-p2-8-0-android-aarch64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-02-11&endday=2019-02-17&tree=all

Comment 17

[Intermittent Failures Robot]

1 failures in 4337 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 1

Platform breakdown:

• android-hw-p2-8-0-arm7-api-16: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1518719&startday=2019-05-27&endday=2019-06-02&tree=all