Fix test to work with SpiderMonkey and updated V8 exception text
fix test; background indexing behavior changed (for the better)

Conflicts:
	jstests/slowWeekly/indexbg1.js
remove test no longer needed due to index changes

Conflicts:
	jstests/slowWeekly/indexbg_dur.js
wait longer for test completion

On my Windows box it takes 36 minutes, but on some of the slower
Windows buildbots, the test is taking longer than 60 minutes.
We will now wait for 2 hours before giving up.
buildbot - fix dbpath name
not so big so Windows can finish in a reasonable amount of time
SERVER-8360 - only run dur_passthrough.js on linux 64bit non-debug builds.
Add node startup information to the local DB jstests - SERVER-7451
revert: Add node startup information to the local DB jstests - SERVER-7451
SERVER-8381 raise timeout in cursor timeout test
SERVER-8203: replication metrics test fix
Make slowNightly/sharding_rs1.js more robust

Use a more reliable method for stopping the balancer before computing
database hashes.  awaitReplication() is not sufficient if the balancer
is still running, since the data on the primary can change after we've
checked for replication.
SERVER-8203: cleanup test for failing buildbot
add a test for multiple 2dsphere fields and timing with and without index
remove flaky timing test
SERVER-5064 Improve error reporting in test

Adjust code to catch exception during query attempt so that assert
runs and prints stack trace, display message on assertion failure.
SERVER-6388 partial

With server-8382 bench_test1.js should send (or not send) same
username/password for all benchRun calls.

Signed-off-by: Ian Whalen <ian.whalen@gmail.com>
Disable portion of test that depends on reconnect

Related tickets:
SERVER-8532 - fix reconnect logic in shell (revert this commit when fixed)
SERVER-8529 - max_message_size.js failing on win32
SERVER-8220: test for eval() returning a native function
tab -> space + formatting for sharding_passthrough.js

Conflicts:
	jstests/slowNightly/sharding_passthrough.js