[SERVER-5428] count8.js failing on Nightly RHEL build Created: 28/Mar/12  Updated: 11/Jul/16  Resolved: 28/May/12

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: None
Fix Version/s: 2.1.2

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

Nightly Linux RHEL 64-bit


Issue Links:
Related
related to SERVER-5935 count8.js sharding_passthrough tests Closed
Operating System: ALL
Participants:

 Description   

Wed Mar 28 06:14:18 [conn237] info journal _rotate called inside dbMutex - ok but should be somewhat rare
Wed Mar 28 06:14:19 [conn237] update test.jstests_count8 query: { $atomic: true } update: { $set: { a: -1.0 } } nscanned:2559996 nmoved:1279996 nupdated:1280000 keyUpdates:1 156719ms
Wed Mar 28 06:14:19 [conn237] end connection 127.0.0.1:48621 (4 connections now open)
sh12334| null
assert failed
Error("Printing Stack Trace")@:0
()@src/mongo/shell/utils.js:37
("assert failed")@src/mongo/shell/utils.js:58
(false)@src/mongo/shell/utils.js:66
checkYield(false,true)@/data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/jstests/count8.js:41
@/data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/jstests/count8.js:47
 
Wed Mar 28 06:14:19 uncaught exception: assert failed

http://buildbot.mongodb.org/builders/Nightly%20Linux%20RHEL%2064-bit/builds/46/steps/test_2/logs/stdio



 Comments   
Comment by Ian Whalen (Inactive) [ 19/Apr/12 ]

Looks like this might have just popped up again - http://buildbot.mongodb.org/builders/Nightly%20Linux%20RHEL%2032-bit/builds/72/steps/test_1/logs/stdio

Comment by auto [ 05/Apr/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5428 re-arrange aquiring blocks so we know when we're waiting for a lock
Branch: master
https://github.com/mongodb/mongo/commit/4f4ad3e12dd8198e11ead328fba0bc3ce2aa0491

Comment by auto [ 04/Apr/12 ]

Author:

{u'login': u'astaple', u'email': u'aaron@10gen.com', u'name': u'Aaron'}

Message: Revert "SERVER-5428 Remove yield validation from the count8.js test, but preserve sanity checks for drop on yield cases."

This reverts commit 0d5b0e67d37e896df3e932da1dfd0b38d591ff87.
Branch: master
https://github.com/mongodb/mongo/commit/50304f5ad87115a2a5de1cb391fa540d57cbdff2

Comment by auto [ 04/Apr/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5428 Add a deterministic count yield validation test to counttests.cpp.
Branch: master
https://github.com/mongodb/mongo/commit/3ae516c69c16be09f5c7dd1c8c1d1069efc0cc00

Comment by auto [ 04/Apr/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5428 Remove yield validation from the count8.js test, but preserve sanity checks for drop on yield cases.
Branch: master
https://github.com/mongodb/mongo/commit/0d5b0e67d37e896df3e932da1dfd0b38d591ff87

Comment by Eric Milkie [ 04/Apr/12 ]

The test seems to fail much more reliably with db level locking turned on; this will need to be fixed before we can make db level locking the default.
e.g. http://buildbot.mongodb.org/builders/Linux%2032-bit/builds/4506/steps/test/logs/stdio

Comment by Andy Schwerin [ 03/Apr/12 ]

This test is brittle to timing variation, and now fails sporadically because it depends on a race between two parties.

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