[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 |
http://buildlogs.mongodb.org/build/5004f8ead2a60f60a4000f8c/test/500525d7d2a60f105c000956/ |
| 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: |
| 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: |
| 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. |