Closed Bug 814551 Opened 12 years ago Closed 11 years ago

Intermittent b2g process crash when running Marionette tests on emulator

Categories

(Firefox OS Graveyard :: General, defect, P4)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:-)

RESOLVED WORKSFORME
blocking-basecamp -

People

(Reporter: swu, Unassigned)

References

Details

(Keywords: crash, intermittent-failure, Whiteboard: [b2g-crash])

Another case:

https://tbpl.mozilla.org/php/getParsedLog.php?id=17292773&tree=Try&full=1
Keywords: crash
Whiteboard: [b2g-crash]
blocking-basecamp: --- → ?
We decided in triage that we can't block on this.  I'm marking it as a "soft" blocker (blocking-, P4).
blocking-basecamp: ? → -
Priority: -- → P4
https://tbpl.mozilla.org/php/getParsedLog.php?id=17440065&full=1&branch=mozilla-inbound

{
21:48:19     INFO - F/libc    (  182): Fatal signal 7 (SIGBUS) at 0x4138a9e8 (code=2)
21:48:19     INFO - I/DEBUG   (   35): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
21:48:19     INFO - I/DEBUG   (   35): Build fingerprint: 'Android/full/generic:4.0.4.0.4.0.4/OPENMASTER/1254:eng/test-keys'
21:48:19     INFO - I/DEBUG   (   35): pid: 182, tid: 182  >>> /system/b2g/plugin-container <<<
21:48:19     INFO - I/DEBUG   (   35): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4138a9e8
21:48:19     INFO - I/DEBUG   (   35):  r0 4138a9e8  r1 00000000  r2 00000600  r3 80000000
21:48:19     INFO - I/DEBUG   (   35):  r4 00000000  r5 00000000  r6 00000000  r7 00000000
21:48:19     INFO - I/DEBUG   (   35):  r8 b00136ac  r9 0019a9e8  10 01128000  fp 400c8000
21:48:19     INFO - I/DEBUG   (   35):  ip 00000000  sp be9b2540  lr 00000000  pc b000393c  cpsr a0000010
21:48:19     INFO - I/DEBUG   (   35):  d0  0000000000000000  d1  0000000000000000
21:48:19     INFO - I/DEBUG   (   35):  d2  0000000000000000  d3  0000000000000000
21:48:19     INFO - I/DEBUG   (   35):  d4  0000000000000000  d5  41cb0b69ee800000
21:48:19     INFO - I/DEBUG   (   35):  d6  3f50624dd2f1a9fc  d7  3ede5bd803edab09
21:48:19     INFO - I/DEBUG   (   35):  d8  0000000000000000  d9  0000000000000000
21:48:19     INFO - I/DEBUG   (   35):  d10 0000000000000000  d11 0000000000000000
21:48:19     INFO - I/DEBUG   (   35):  d12 0000000000000000  d13 0000000000000000
21:48:19     INFO - I/DEBUG   (   35):  d14 0000000000000000  d15 0000000000000000
21:48:19     INFO - I/DEBUG   (   35):  scr 00000010
21:48:19     INFO - I/DEBUG   (   35):
21:48:19     INFO - I/DEBUG   (  183): debuggerd: Nov 28 2012 17:54:00
}
https://tbpl.mozilla.org/php/getParsedLog.php?id=17599768&tree=Mozilla-Inbound

{
11:39:21 ERROR - Traceback (most recent call last):
11:39:21 INFO - TEST-UNEXPECTED-FAIL | test_execute_async_script.py TestExecuteAsyncContent.test_execute_async_unload | MarionetteException: {u'from': u'conn92.marionette1', u'value': None}
11:39:21 ERROR - Traceback (most recent call last):
11:39:21 INFO - TEST-UNEXPECTED-FAIL | test_execute_async_script.py TestExecuteAsyncContent.test_execute_js_exception | MarionetteException: {u'ok': True, u'from': u'conn92.marionette1'}
11:39:21 ERROR - FAILED (errors=2)
11:40:00 ERROR - Return code: 10
11:40:00 ERROR - F/libc ( 172): Fatal signal 7 (SIGBUS) at 0x4139d088 (code=2)
11:40:00 ERROR - This usually indicates the B2G process has crashed
}

Bug 815676 seems to be working :-)
https://tbpl.mozilla.org/php/getParsedLog.php?id=17751206&tree=Mozilla-Inbound

Please can we make the B2G marionette runs abort earlier on than in most of these? Judging from comments on IRC, non-sheriffs are still having great trouble seeing the true cause of the failures amongst all the noise.
(In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #17)
> https://tbpl.mozilla.org/php/getParsedLog.php?id=17751206&tree=Mozilla-
> Inbound
> 
> Please can we make the B2G marionette runs abort earlier on than in most of
> these? Judging from comments on IRC, non-sheriffs are still having great
> trouble seeing the true cause of the failures amongst all the noise.

Yes, it's high on our list of things to do.
Blocks: 823076
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.