Closed Bug 979245 Opened 11 years ago Closed 9 years ago

Intermittent tests/test-child_process.testExecFileOptionsMaxBufferLargeStdOErr | Exit code is null in exit handler - null == 0

Categories

(Add-on SDK Graveyard :: General, defect, P1)

Product:
Add-on SDK Graveyard
Component:
General
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure)

Ubuntu ASAN VM 12.04 x64 mozilla-inbound opt test jetpack on 2014-03-03 23:41:19 PST for push 765770122c29 slave: tst-linux64-spot-411 https://tbpl.mozilla.org/php/getParsedLog.php?id=35584156&tree=Mozilla-Inbound TEST-UNEXPECTED-FAIL | tests/test-child_process.testExecFileOptionsMaxBufferLargeStdOErr | Exit code is null in exit handler - null == 0
https://tbpl.mozilla.org/php/getParsedLog.php?id=35572414&tree=Mozilla-Inbound
Summary: Intermittent ASAN | | tests/test-child_process.testExecFileOptionsMaxBufferLargeStdOErr | Exit code is null in exit handler - null == 0 → Intermittent ASAN tests/test-child_process.testExecFileOptionsMaxBufferLargeStdOErr | Exit code is null in exit handler - null == 0
Product: Core → Add-on SDK
Version: Trunk → unspecified
Summary: Intermittent ASAN tests/test-child_process.testExecFileOptionsMaxBufferLargeStdOErr | Exit code is null in exit handler - null == 0 → Intermittent tests/test-child_process.testExecFileOptionsMaxBufferLargeStdOErr | Exit code is null in exit handler - null == 0
Priority: -- → P1
Erik, it appears this is mostly confined to Gecko <32 branches at this point. However, that means it's still happening on the release destined to be our next ESR. Do you have any idea what might have fixed this in later releases? Otherwise, can we get a patch to disable this test on 31?
Flags: needinfo?(evold)
I thought the chile process tests were disabled.
Flags: needinfo?(evold) → needinfo?(jsantell)
(In reply to Erik Vold [:erikvold] [:ztatic] from comment #158) > I thought the chile process tests were disabled. *child_process
This looks like it was disabled on 5/30/2014: https://github.com/mozilla/addon-sdk/commit/8e68d49c71bac4202c689d6d677a8aed77f05dd4 Could/should this be uplifted? cc Wes
Flags: needinfo?(jsantell) → needinfo?(kwierso)
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #160) > This looks like it was disabled on 5/30/2014: > https://github.com/mozilla/addon-sdk/commit/ > 8e68d49c71bac4202c689d6d677a8aed77f05dd4 > > Could/should this be uplifted? cc Wes I guess. It's already disabled in the firefox32 branch, so it would only need to go to beta/firefox31. It's test-only, so it shouldn't be too hard to get approval to uplift it, even at this point in the beta cycle (Firefox 31 releases on July 22).
Flags: needinfo?(kwierso)
Test disabled on esr31 (Jetpack tests were completely turned off on the B2G release branches, so I'm not backporting to b2g30). https://hg.mozilla.org/releases/mozilla-esr31/rev/51b6baf691d8
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.