Closed Bug 949071 Opened 11 years ago Closed 10 years ago

Intermittent Android 2.2 test_add_put.js | test failed (with xpcshell return code: 0) | false == true followed by many more

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure) 

Philor notes that every slave showing this appears to be a recently-recovered Tegra.

https://tbpl.mozilla.org/php/getParsedLog.php?id=31801916&tree=B2g-Inbound

Android 2.2 Armv6 Tegra b2g-inbound opt test xpcshell on 2013-12-11 03:12:25 PST for push cf2a20bbc6cf
slave: tegra-189

is(0, 0, "expect zero for test {"autoincrement":true,"keypath":true,"method":"put","explicit":true,"existing":false}")
TEST-PASS | test_add_put.js | [testSteps : 94] 0 == 0
is({"theObj":true,"id":5}, {"theObj":true,"id":5}, "call didn't modify value for test {"autoincrement":true,"keypath":true,"method":"put","explicit":true,"existing":false}")
TEST-PASS | test_add_put.js | [testSteps : 95] "{"theObj":true,"id":5}" == "{"theObj":true,"id":5}"
indexedDB error: UnknownError
TEST-UNEXPECTED-FAIL | /mnt/sdcard/tests/xpcshell/dom/indexedDB/test/unit/head.js | false == true - See following stack:
JS frame :: /mnt/sdcard/tests/xpcshell/dom/indexedDB/test/unit/head.js :: errorHandler :: line 83
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
TEST-INFO | (xpcshell/head.js) | exiting test
System JS : ERROR (null):0 - uncaught exception: 2147500036

<<<<<<<
It seems pretty obvious to me that this is an error for these devices that wasn't here before and that its for every xpcshell run they encounter, while other xpchsell runs are fine. Its across trees even on beta.

gbrown,

Can you peek at these logs and suggest anything for me to check that may be amiss we could identify in a pre-flight task of some sort.

Vinh,

Can you identify any potential change/missed item that was in this tegra recovery batch that wasn't in others.
Flags: needinfo?(vhua)
Flags: needinfo?(gbrown)
i think i know what happened. we used SD cards that we proactively imaged for the pandas when we ran out of SD cards for the tegras. the interns might not have formatted these SD cards (they probably thought it might have been brand new) before putting the tegra image on top.

can you give us a list of affected tegras?
Flags: needinfo?(vhua)
Sooo, out of all tegras recovered in Bug 944498 --

The following had failed xpcshell jobs (asterisks next to are per each failure linked in this bug)

tegra-231**
tegra-219*
tegra-178*
tegra-214*
tegra-170**
tegra-173*
tegra-177*
tegra-181**
tegra-343
tegra-189**
tegra-235*
tegra-262*
tegra-220*

The following have had no xpcshell jobs but still have taken other jobs:

tegra-263
tegra-073
tegra-039
tegra-040
tegra-215
tegra-052
tegra-074
tegra-061
tegra-072
tegra-356
tegra-107

And for completeness the following have never taken a job since recovery in that bug:

tegra-050
tegra-171
tegra-200
tegra-045
tegra-232
tegra-087
tegra-192
tegra-217
tegra-158
tegra-149

I'm adding all of the above to the recovery bug.
Depends on: 949447
Flags: needinfo?(gbrown)
Closing bugs where TBPLbot has previously commented, but have now not been modified for >3 months & do not contain the whiteboard strings for disabled/annotated tests or use the keyword leave-open. Filter on: mass-intermittent-bug-closure-2014-07
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.