Closed Bug 687116 Opened 13 years ago Closed 12 years ago

Intermittent "unrecognized output format" running Talos on Android

Categories

(Testing :: Talos, defect)

Product:
Testing
Component:
Talos
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [mobile_unittests][android_tier_1_mozharness])

An old classic, back by popular demand. https://tbpl.mozilla.org/php/getParsedLog.php?id=6424059&tree=Firefox tegra-051: Started Fri, 16 Sep 2011 07:03:26 Running test tsspider: Started Fri, 16 Sep 2011 07:03:26 reconnecting socket FIRE PROC: 'org.mozilla.fennec -profile /mnt/sdcard/tests/profile http://bm-remote.build.mozilla.org/getInfo.html' reconnecting socket FIRE PROC: 'org.mozilla.fennec -profile /mnt/sdcard/tests/profile -tp /mnt/sdcard/tests/sunspider.manifest -tpnoisy -tpformat tinderbox -tpcycles 3 -tpdelay 1000' reconnecting socket pushing directory: /tmp/tmpUEi_Qb/profile to /mnt/sdcard/tests/profile Screen width/height:1024/768 colorDepth:24 Browser inner width/height: 980/825 NOISE: __metrics Screen width/height:1024/768 NOISE: colorDepth:24 NOISE: Browser inner width/height: 980/825 NOISE: __metrics NOISE: __metrics Screen width/height:1024/768 NOISE: colorDepth:24 NOISE: Browser inner width/height: 980/825 NOISE: __metrics__startSecondTimestamp1316181990805__endSecondTimestamp Failed tsspider: Stopped Fri, 16 Sep 2011 07:07:30 FAIL: Busted: tsspider FAIL: unrecognized output format Completed test tsspider: Stopped Fri, 16 Sep 2011 07:07:30 RETURN: cycle time: 00:04:03<br>
Can someone from ateam look into this?
Component: Release Engineering → Talos
Product: mozilla.org → Testing
QA Contact: release → talos
Version: other → Trunk
currently blocked by bug 687147
Depends on: 687147
Depends on: 690311
Whiteboard: [orange][mobile_unittests][android_tier_1] → [orange][mobile_unittests][android_tier_1_mozharness]
Blocks: 738716
We're now tracking this in bug 738716. This bug is ambiguous. It can mean any number of things has happened (firefox isn't closed properly; lack of write permissions; parsing error; buffers did not flush properly). All you really know is that the file didn't get read properly. We should disambiguate this since generally we know (*somewhere* in the code, anyway) what happened
See Also: → 742937
Once bug 742937 lands, this error message will be more specific to the type of parsing failure for the browser log, though it won't fix the underlying failure
This message fragmented into all those "could not find beforeLaunchTime" and whatnot things.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange][mobile_unittests][android_tier_1_mozharness] → [mobile_unittests][android_tier_1_mozharness]
You need to log in before you can comment on or make changes to this bug.