Closed Bug 1335611 Opened 7 years ago Closed 7 years ago

Intermittent modules/libjar/zipwriter/test/unit/test_bug419769_1.js | xpcshell return code: 0

Categories

(Testing :: XPCShell Harness, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1335501

People

(Reporter: intermittent-bug-filer, Assigned: gbrown)

Details

(Keywords: intermittent-failure)

Geoff, I don't think this is exactly bug 1335501, but I believe I've seen a couple of instances of this in the past.
It seems to me that the storage is either unavailable, or the harness is unable to cd into the right folder.
Component: Networking: JAR → XPCShell Harness
Flags: needinfo?(gbrown)
Product: Core → Testing
Thanks for pointing this out. It is different from bug 1335501, and I hadn't noticed it before.

I see:

[task 2017-01-31T21:25:02.497846Z] 21:25:02     INFO -  pushing /home/worker/workspace/build/tests/xpcshell/tests
[task 2017-01-31T21:30:54.147389Z] 21:30:54     INFO -  mozdevice Timeout exceeded for _runCmd call 'adb shell unzip -o /storage/sdcard/tests/xpc/adbdmtmp.zip -d /storage/sdcard/tests/xpc'

which probably means that the tests directory on the device was not fully created. I think that explains all the following errors:

[task 2017-01-31T21:32:10.329116Z] 21:32:10     INFO -  PROCESS | modules/libjar/zipwriter/test/unit/test_bug419769_1.js | /data/local/xpcb/xpcw[14]: cd: /storage/sdcard/tests/xpc/modules/libjar/zipwriter/test/unit: No such file or directory

The root cause of the failure might just be bug 1321605. Or a longer timeout might be required on that unzip...and probably better error handling.

But the good news is that my fix for bug 1335501 will handle this case too: Since "Timeout exceeded for _runCmd call" is reported, the job will be abandoned and automatically retried, and this type of failure should no longer result in a bug being filed.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(gbrown)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.