[SERVER-10046] buildbot: Linux 64 failing on fastsync.js Created: 27/Jun/13  Updated: 11/Jul/16  Resolved: 28/Jun/13

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

Type: Bug Priority: Critical - P2
Reporter: Matt Kangas Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Buildbot: Linux 64, probably others


Operating System: ALL
Steps To Reproduce:

../bisect_one_test.sh jstests/replsets/fastsync.js

Where bisect_one_test.sh is

#!/bin/bash
 
echo "START: " `date`
set -o errexit
set -o xtrace
 
time scons --dd  --sharedclient all
python buildscripts/cleanbb.py
./buildscripts/smoke.py --mode=files $@
 
echo "SUCCESS: " `date`

Participants:

 Description   

Eric - you said this came from Eliot's namespace change?

http://buildbot.10gen.cc/builders/Linux%2064-bit/builds/5550/steps/test_9/logs/stdio

         Test : fastsync.js ...
      Command : /data/buildslaves/Linux_64bit/mongo/mongo --port 27999 --authenticationMechanism MONGODB-CR --nodb /data/buildslaves/Linux_64bit/mongo/jstests/replsets/fastsync.js --eval TestData = new Object();TestData.testPath = "/data/buildslaves/Linux_64bit/mongo/jstests/replsets/fastsync.js";TestData.testFile = "fastsync.js";TestData.testName = "fastsync";TestData.noJournal = false;TestData.noJournalPrealloc = false;TestData.auth = false;TestData.keyFile = null;TestData.keyFileData = null;TestData.authMechanism = "MONGODB-CR";
         Date : Thu Jun 27 06:09:33 2013
                (output suppressed; see http://buildlogs.mongodb.org/build/51cbcb08d2a60f21c7000936/test/51cbd71dd2a60f3ffb000236/)
                    1.4172 minutes
test /data/buildslaves/Linux_64bit/mongo/jstests/replsets/fastsync.js exited with status 253

http://buildlogs.mongodb.org/Linux%2064-bit/builds/5550/test/replica%20sets/fastsync.js

Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:37:15)
    at doassert (src/mongo/shell/assert.js:6:5)
    at Function.assert.soon (src/mongo/shell/assert.js:174:60)
    at startSlave (/data/buildslaves/Linux_64bit/mongo/jstests/replsets/fastsync.js:146:12)
    at /data/buildslaves/Linux_64bit/mongo/jstests/replsets/fastsync.js:162:10
Thu Jun 27 06:10:56.294 assert.soon failed: function () {
        try {
            var last = local.oplog.rs.find().sort({$natural:-1}).limit(1).next();
            var cur = conn.getDB("local").oplog.rs.find().sort({$natural:-1}).limit(1).next();
            print("last: "+tojson(last)+" cur: "+tojson(cur));
            return cur != null && last != null && cur.ts.t == last.ts.t && cur.ts.i == last.ts.i;
        }
        catch (e) {
            print(e);
        }
        return false;
    }, msg:undefined at src/mongo/shell/assert.js:7



 Comments   
Comment by auto [ 28/Jun/13 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-10046 fix situation where ns is null
Branch: master
https://github.com/mongodb/mongo/commit/86e76e34e88c3db7c48039b3e7c1b2a8e5d12771

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