[SERVER-5413] repairDatabase should fail due to killOp in repair5.js Created: 26/Mar/12  Updated: 25/Jul/13  Resolved: 30/Mar/12

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

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

Linux 32-bit debug


Operating System: ALL
Participants:

 Description   

 m31000| Mon Mar 26 15:50:18 [conn1] warning: ClientCursor::yield can't unlock b/c of recursive lock ns: jstests_disk_repair5.jstests_disk_repair5 top: { opid: 20000, active: true, lockType: "W", waitingForLock: false, secs_running: 3, op: "query", ns: "jstests_disk_repair5", query: { repairDatabase: 1.0, backupOriginalFiles: true }, client: "127.0.0.1:60530", desc: "conn", threadId: "0xb6ac4b70", connectionId: 1, numYields: 0 }
 m31000| Mon Mar 26 15:50:18 [conn1] warning: ClientCursor::yield can't unlock b/c of recursive lock ns: jstests_disk_repair5.jstests_disk_repair5 top: { opid: 20000, active: true, lockType: "W", waitingForLock: false, secs_running: 3, op: "query", ns: "jstests_disk_repair5", query: { repairDatabase: 1.0, backupOriginalFiles: true }, client: "127.0.0.1:60530", desc: "conn", threadId: "0xb6ac4b70", connectionId: 1, numYields: 0 }
 m31000| Mon Mar 26 15:50:18 [conn1] warning: ClientCursor::yield can't unlock b/c of recursive lock ns: jstests_disk_repair5.jstests_disk_repair5 top: { opid: 20000, active: true, lockType: "W", waitingForLock: false, secs_running: 3, op: "query", ns: "jstests_disk_repair5", query: { repairDatabase: 1.0, backupOriginalFiles: true }, client: "127.0.0.1:60530", desc: "conn", threadId: "0xb6ac4b70", connectionId: 1, numYields: 0 }
 m31000| Mon Mar 26 15:50:18 [conn1] build index jstests_disk_repair5.jstests_disk_repair5 { _id: 1 }
 m31000| Mon Mar 26 15:50:18 [conn1] 	 fastBuildIndex dupsToDrop:0
 m31000| Mon Mar 26 15:50:18 [conn1] build index done.  scanned 20000 total records. 0.195 secs
 m31000| Mon Mar 26 15:50:19 [FileAllocator] done allocating datafile /data/db/jstests_disk_repair5/repairDir/backup_repairDatabase_0/jstests_disk_repair5.4, size: 256MB,  took 1.721 secs
 m31000| Mon Mar 26 15:50:19 [conn1] command jstests_disk_repair5.$cmd command: { repairDatabase: 1.0, backupOriginalFiles: true } ntoreturn:1 keyUpdates:0 reslen:37 4965ms
assert: command worked when it should have failed: { "ok" : 1 } : undefined
Error("Printing Stack Trace")@:0
()@src/mongo/shell/utils.js:37
("command worked when it should have failed: { \"ok\" : 1 } : undefined")@src/mongo/shell/utils.js:58
([object bson_object])@src/mongo/shell/utils.js:226
@/home/yellow/buildslave/Linux_32bit_debug/mongo/jstests/disk/repair5.js:38
 
Mon Mar 26 15:50:19 uncaught exception: command worked when it should have failed: { "ok" : 1 } : undefined
failed to load: /home/yellow/buildslave/Linux_32bit_debug/mongo/jstests/disk/repair5.js

http://buildbot.mongodb.org/builders/Linux%2032-bit%20debug/builds/1482/steps/test_2/logs/stdio



 Comments   
Comment by Andy Schwerin [ 30/Mar/12 ]

Various bug fixes in the last 3 days, 32-bit Linux build looks clean.

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