Closed Bug 575914 Opened 14 years ago Closed 8 years ago

test_cpow.js | test failed (with xpcshell return code: 3), see following log: | 3 == 6 - See following stack:

Categories

(Core :: IPC, defect)

Product:
Core
Component:
IPC
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: romaxa, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [test disabled])

Attachments

(1 file)

Disable cpow tests
496 bytes, patch
jst
: review+
Details | Diff | Splinter Review 
e10s build test orange dues failed cpow

http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1277878866.1277879895.10533.gz

***********************
TEST-PASS | /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jetpack/unit/test_jetpack.js | test passed
TEST-UNEXPECTED-FAIL | /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jsipc/unit/test_cpow.js | test failed (with xpcshell return code: 3), see following log:
  >>>>>>>
  TEST-INFO | (xpcshell/head.js) | test 1 pending
parent: TEST-INFO | (xpcshell/head.js) | test 2 pending
parent: TEST-INFO | (xpcshell/head.js) | test 2 finished
parent: TEST-INFO | (xpcshell/head.js) | running event loop
child: TEST-INFO | (xpcshell/head.js) | test 1 pending
child: TEST-INFO | (xpcshell/head.js) | test 1 finished
child: TEST-INFO | (xpcshell/head.js) | exiting test
child: TEST-INFO | (xpcshell/head.js) | No (+ 0) checks actually run
parent: TEST-PASS | /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jsipc/unit/test_cpow.js | [test_properties : 30] true == true
*************

parent: TEST-PASS | /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jsipc/unit/test_cpow.js | [test_generators : 178] 6 == 6
parent: TEST-UNEXPECTED-FAIL | /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jsipc/unit/test_cpow.js | 3 == 6 - See following stack:
parent: JS frame :: /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/head.js :: do_throw :: line 266
parent: JS frame :: /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/head.js :: do_check_eq :: line 296
parent: JS frame :: /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jsipc/unit/test_cpow.js :: test_generators :: line 186
parent: JS frame :: /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_jsipc/unit/test_cpow.js :: run_actual_tests :: line 21
parent: TEST-INFO | (xpcshell/head.js) | exiting test
uncaught exception: 2147500036
NOTE: child process received `Goodbye', closing down

  <<<<<<<
TEST-PASS | /builds/slave/tryserver-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_libjar/unit/test_bug278262.js | test passed
**********************************************


I think we should disable that test, or fix it
This is not a m-c merge blocker.
So, umm... that means somebody is going to disable the test? Obviously we can't merge with the tree orange.
disable tests.

There are currently no consumers of cpow.  Lets disable these tests (so that we can have green tests), and re-enable them when the know issue is figured out.
Attachment #455296 - Flags: review?
Attachment #455296 - Flags: review? → review?(benjamin)
Comment on attachment 455296 [details] [diff] [review]
Disable cpow tests

r=jst assuming we get a bug filed for the followup.
Attachment #455296 - Flags: review?(benjamin) → review+
Blocks: 438871
In sorting out bug 696498, I've been having to go through makefiles missing from toolkit-makefiles.sh. Having the tests directory include removed rather than commented out made it hard to use MXR to track down whether cpow was supposed to be part of the build or not. 

What do you think of the idea of re-adding |TOOL_DIRS += tests|, but commenting out and including a reference to this bug, similar to what has been done in other places in the tree?
Whiteboard: [orange] → [orange][test disabled]
Whiteboard: [orange][test disabled] → [test disabled]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.