Run features3.js.

That test spawns a separate shell process that runs a long-running query in an infinite loop that only breaks when the query throws an exception.

The main test program then goes and kills that query with db.killOp(), which should cause an interrupted exception in the other shell process, causing it to terminate, but it doesn't. Because of this, when the main test program tries to join() with the child shell process, it waits forever and the test never terminates. Without authentication this works fine.