Skip to content
Commits on Feb 8, 2016
  1. @DiannaHohensee
Commits on Feb 5, 2016
  1. @ksuarz

    Revert "SERVER-22352 lockFile changes for readOnly"

    ksuarz committed
    This reverts commit 77191d8.
  2. @scotthernandez
  3. @scotthernandez
  4. @scotthernandez
  5. @benety

    SERVER-22287 comment out failing test ReplCoordHBV1Test::IgnoreTheCon…

    benety committed
  6. @mgrundy

    SERVER-21698 Add error-checking for isMaster() return values in jstes…

    mgrundy committed
  7. @amidvidy

    SERVER-22352 lockFile changes for readOnly

    amidvidy committed
    modify StorageEngineLockFile::open() to return a different status if it
    fails due to the dbpath having read-only permissions
  8. @renctan

    Revert "SERVER-22349 Throw exceptions from loadStored"

    renctan committed
    This reverts commit dfc320f.
  9. @mgrundy
  10. @mgrundy

    SERVER-22341 fix jslint errors in jstests/parallel with eslint --fix

    mgrundy committed
  11. @mgrundy
  12. @mgrundy
  13. @mgrundy
  14. @mgrundy
  15. @mgrundy
  16. @mgrundy
  17. @mgrundy
  18. @mgrundy
  19. @mgrundy
  20. @mgrundy
  21. @mgrundy
  22. @mgrundy
  23. @mgrundy
  24. @mgrundy
  25. @mgrundy
  26. @mgrundy
  27. @mgrundy
  28. @mgrundy
  29. @mgrundy
  30. @mgrundy
  31. @mgrundy
  32. @jameswahlin

    SERVER-18826 Rename WorkingSet State Names from LOC to RID

    jameswahlin committed
    Also renamed:
     * WorkingSetMember::hasLoc() -> WorkingSetMember::hasRecordId
     * WorkingSetMember::loc -> WorkingSetMember::recordId
  33. @dannenberg
  34. @hanumantmk

    SERVER-22349 Throw exceptions from loadStored

    hanumantmk committed
    The JS engine's loadStored eats exceptions that occur while it's loading
    functions from system.js.  This also eats interruption exceptions, which
    can lead to a situation where a map reduce job is killed during
    loadStored, but the interrupt is lost. For tests where the map or reduce
    stages are long or non-terminating, and we rely on killing them, this
    can lead to hangs.
    Removing the try/catch block around loadStored fixes this behavior.
Something went wrong with that request. Please try again.