This syntax has never worked. in 2.5.x it will error out
2.5.x allows w=majority for standalone servers
This hits a different errorcode in 2.5.x (intentionally)
The order of fields is not guaranteed, and "sometimes" changes during writes

Fix test to work on all mongodb versions
Do another write to increase our chances of he 10 other being replicated
The request_id has been bumped by 3 at this point
Fix the weird skipif message with double reason

Stop right away when we know we aren't gonna run the test
Make it fail faster when broken, and more clearly
Fix failover tests on old mongod

When putting older 2.4 and older mongod into maintenance mode repeatidly
it will get confused as it has a task counter that will go negative and
therefore refuse to go into recovery mode, or come backup if positive
2.5.x changed some auth failure error messages and user document field order
2.5.x forces all queries on $cmd to be limit(1/-1)
Hide memory leak which we can't fix in 1.4, but is fixed in 1.5
Merge pull request #523 from bjori/fixtest-v14

Fixtest v14

* bjori/fixtest-v14:
  Hide memory leak which we can't fix in 1.4, but is fixed in 1.5
  2.5.x forces all queries on $cmd to be limit(1/-1)
  2.5.x changed some auth failure error messages and user document field order
  Fix failover tests on old mongod
  Make it fail faster when broken, and more clearly
  Fix the weird skipif message with double reason
  The request_id has been bumped by 3 at this point
  Do another write to increase our chances of he 10 other being replicated
  The order of fields is not guaranteed, and "sometimes" changes during writes
  This hits a different errorcode in 2.5.x (intentionally)
  2.5.x allows w=majority for standalone servers
  This syntax has never worked. in 2.5.x it will error out
Merge branch 'v1.4'

* v1.4:
  Hide memory leak which we can't fix in 1.4, but is fixed in 1.5
  2.5.x forces all queries on $cmd to be limit(1/-1)
  2.5.x changed some auth failure error messages and user document field order
  Fix failover tests on old mongod
  Make it fail faster when broken, and more clearly
  Fix the weird skipif message with double reason
  The request_id has been bumped by 3 at this point
  Do another write to increase our chances of he 10 other being replicated
  The order of fields is not guaranteed, and "sometimes" changes during writes
  This hits a different errorcode in 2.5.x (intentionally)
  2.5.x allows w=majority for standalone servers
  This syntax has never worked. in 2.5.x it will error out