diff options
| author | Tad Marshall <tad@10gen.com> | 2012-03-08 03:31:39 -0500 |
|---|---|---|
| committer | Tad Marshall <tad@10gen.com> | 2012-03-08 03:31:39 -0500 |
| commit | ef111a5b999fdb6871775a57fedf4fab07a10df4 (patch) | |
| tree | 91298fe538fff252aecfb22f28ce9c6c3de5138e /jstests/push2.js | |
| parent | 5132fee1a9e4e5bcfe17a414e732c371d51072ea (diff) | |
| download | mongo-ef111a5b999fdb6871775a57fedf4fab07a10df4.tar.gz | |
SERVER-5244 Added temporary diagnostics to 2 tests
The 32-bit Windows BuildBot is showing signs of being out of
memory while mapping a file that has been expanded to try to
get a BSON size error (on purpose). In successful tests, we
get the BSON size error, on failing tests we get a Windows API
failure instead. I added db.hostInfo(), db.serverStatus() and
db.stats() to push2.js and pushall.js temporarily to see if we
can learn if it's really an out-of-memory failure.
Diffstat (limited to 'jstests/push2.js')
| -rw-r--r-- | jstests/push2.js | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/jstests/push2.js b/jstests/push2.js index c8d0d0f5508..0a3906d315f 100644 --- a/jstests/push2.js +++ b/jstests/push2.js @@ -1,3 +1,11 @@ +print( "Temporary diagnostics for 32-bit Windows pushall.js failures" ); +print( "db.hostInfo()" ); +printjson( db.hostInfo() ); +print( "db.serverStatus()" ); +printjson( db.serverStatus() ); +print( "db.stats()" ); +printjson( db.stats() ); +print( "End of temporary diagnostics for 32-bit Windows pushall.js failures" ); t = db.push2 t.drop() |