[SERVER-11729] dup_bgindex.js failing on RHEL 5.7, "Should find only one doc" Created: 15/Nov/13  Updated: 11/Jul/16  Resolved: 15/Nov/13

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.5.4

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: build-failure
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

79bd9b3f4062 RHEL 5.7 64-bit slow_nightly_tests: dup_bgindex.js
http://mci.10gen.com/ui/task/mongodb_mongo_master_rhel_57_64_bit_79bd9b3f40622fef11eb695e27ff18decf6703fc_13_11_15_16_44_06_slow_nightly_tests_rhel57

Fails really fast! I wonder if this test is racy, and why this seems only visible on RHEL 5.7?

http://buildlogs.mongodb.org/mci_0.9_rhel_57_64_bit/builds/9969/test/slow_nightly_tests_0/dup_bgindex.js

Complete test output:

MongoDB shell version: 2.5.4-pre-
connecting to: 127.0.0.1:27999/test
/data/db/
2013-11-15T12:50:01.681-0500 shell: started program /data/mci/git@github.commongodb/mongo.git/master/mongo --useLegacyWriteOps --eval TestData = {
	"testPath" : "/data/mci/git@github.commongodb/mongo.git/master/jstests/slowNightly/dup_bgindex.js",
	"testFile" : "dup_bgindex.js",
	"testName" : "dup_bgindex",
	"setParameters" : "",
	"setParametersMongos" : "",
	"noJournal" : false,
	"noJournalPrealloc" : false,
	"auth" : false,
	"keyFile" : null,
	"keyFileData" : null,
	"authMechanism" : "MONGODB-CR",
	"useSSL" : false,
	"useX509" : false
};db = db.getSiblingDB('test');db.duplIndexTest.ensureIndex( { i : 1 }, {background:true} ); 127.0.0.1:27999
2013-11-15T12:50:01.685-0500 shell: started program /data/mci/git@github.commongodb/mongo.git/master/mongo --useLegacyWriteOps --eval TestData = {
	"testPath" : "/data/mci/git@github.commongodb/mongo.git/master/jstests/slowNightly/dup_bgindex.js",
	"testFile" : "dup_bgindex.js",
	"testName" : "dup_bgindex",
	"setParameters" : "",
	"setParametersMongos" : "",
	"noJournal" : false,
	"noJournalPrealloc" : false,
	"auth" : false,
	"keyFile" : null,
	"keyFileData" : null,
	"authMechanism" : "MONGODB-CR",
	"useSSL" : false,
	"useX509" : false
};db = db.getSiblingDB('test');db.duplIndexTest.ensureIndex( { i : 1 }, {background:true} ); 127.0.0.1:27999
sh30797| MongoDB shell version: 2.5.4-pre-
sh30799| MongoDB shell version: 2.5.4-pre-
sh30797| connecting to: 127.0.0.1:27999/test
sh30799| connecting to: 127.0.0.1:27999/test
sh30797| [object Object]
assert: [1] != [0] are not equal : Should find only one doc
Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:38:15)
    at doassert (src/mongo/shell/assert.js:6:5)
    at Function.assert.eq (src/mongo/shell/assert.js:32:5)
    at /data/mci/git@github.commongodb/mongo.git/master/jstests/slowNightly/dup_bgindex.js:14:8
2013-11-15T12:50:01.819-0500 [1] != [0] are not equal : Should find only one doc at src/mongo/shell/assert.js:7
failed to load: /data/mci/git@github.commongodb/mongo.git/master/jstests/slowNightly/dup_bgindex.js
2013-11-15T12:50:01.748-0500 [conn30] creating index with info @ 0:4328
2013-11-15T12:50:01.748-0500 [conn30] build index on: test.duplIndexTest properties: { v: 1, key: { i: 1.0 }, name: "i_1", ns: "test.duplIndexTest", background: true }
2013-11-15T12:50:01.749-0500 [initandlisten] connection accepted from 127.0.0.1:33898 #31 (3 connections now open)
2013-11-15T12:50:01.757-0500 [conn31] end connection 127.0.0.1:33898 (2 connections now open)
2013-11-15T12:50:01.808-0500 [conn29] CMD: dropIndexes test.duplIndexTest
2013-11-15T12:50:01.808-0500 [conn29] halted 1 index build(s)
2013-11-15T12:50:01.812-0500 [conn30] index build failed. spec: { v: 1, key: { i: 1.0 }, name: "i_1", ns: "test.duplIndexTest", background: true } error: 11601 operation was interrupted
2013-11-15T12:50:01.816-0500 [conn30] end connection 127.0.0.1:33896 (1 connection now open)
2013-11-15T12:50:01.821-0500 [conn29] end connection 127.0.0.1:33895 (0 connections now open)
2013-11-15T12:50:03.267-0500 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2013-11-15T12:50:03.267-0500 [signalProcessingThread] now exiting



 Comments   
Comment by Eric Milkie [ 15/Nov/13 ]

fixed by 42a9c840d346d88c23bc3fb241ab113c85cc7660

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