[SERVER-6482] Parallel test basicPlus.js failing Created: 17/Jul/12  Updated: 11/Jul/16  Resolved: 17/Jul/12

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 2.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

	
Error: Printing Stack Trace
    at src/mongo/shell/utils.js:37:7
    at src/mongo/shell/utils.js:58:1
    at Function.eq (src/mongo/shell/utils.js:88:1)
    at Function.parallelTests (src/mongo/shell/utils.js:926:8)
    at [object Object].run (src/mongo/shell/utils.js:789:8)
assert: [0] != [1] are not equal : one or more tests failed
    at /data/buildslaves/Linux_64bit_v8/mongo/jstests/parallel/basicPlus.js:24:3
Tue Jul 17 08:51:52 exec error: src/mongo/shell/utils.js:59 [0] != [1] are not equal : one or more tests failed
      ^
throw msg;
failed to load: /data/buildslaves/Linux_64bit_v8/mongo/jstests/parallel/basicPlus.js

http://buildlogs.mongodb.org/build/5004f8ead2a60f60a4000f8c/test/500525d7d2a60f105c000956/
http://buildbot.mongodb.org/builders/Linux%2064-bit%20v8/builds/3736



 Comments   
Comment by auto [ 17/Jul/12 ]

Author:

{u'date': u'2012-07-17T11:41:39-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}

Message: SERVER-6482 loglong.js is unreliable in parallel suite
Branch: master
https://github.com/mongodb/mongo/commit/527bdc4c5f251422650a3983a7d323248b91b6d5

Comment by auto [ 17/Jul/12 ]

Author:

{u'date': u'2012-07-17T11:41:39-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}

Message: SERVER-6482 loglong.js is unreliable in parallel suite
Branch: master
https://github.com/mongodb/mongo/commit/527bdc4c5f251422650a3983a7d323248b91b6d5

Comment by Aaron Staple [ 17/Jul/12 ]

My guess is the log messages were recorded in the ram log and overwrote the message expected by the loglong.js test, and this occurred before the test runner read the mongod log messages and flushed them to the output. It is normal for a failure to be reported before server logs relating to the failure are printed. There is no strict ordering between the client and server logs.

I agree there is no definitive proof that this theory about this failure's cause is correct. Since loglong.js can clearly fail due to this issue, though, I think it does make to remove the test from the parallel suite.

I'm not sure why the suites appear to report running multiple tests simultaneously. That seems new.

Previously we were in a state where the parallel tests were passing reliably.

Comment by Eric Milkie [ 17/Jul/12 ]

I half considered removing loglong.js from the suite. But it was unclear to me that the log message was actually flushed. It appears almost adjacent to where the failure is recorded, and I was befuddled by the logging that indicates that S1 was doing more than test at a time and they were overlapping somehow; this seems like a bug as well.
I don't find the parallel test that useful at the moment because it's too difficult to reproduce and debug what is essentially a random interaction between tests, without an easy way to even assign output lines in the log to a particular test.

Generated at Thu Feb 08 03:11:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.