Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10462

Windows file locking related buildbot failures

    • Fully Compatible
    • Windows

      A number of build failures on Windows systems seem to stem from file locking issues.

      Working theory: Our test harness assumes that files owned by a process (usually mongod) will be unlocked as soon as the process exits.

      Windows guarantees that the OS will unlock files after process termination, but makes no guarantees about when they will be unlocked. On a loaded system it may not be immediate.

      Test failures we believe are due to our test framework assuming that the files are immediately unlocked on exit:

      Buildbot V2.4 Windows 64-bit 2008R2+

      Errors include:

      WindowsError: [Error 5] Access is denied: '/data/db/sconsTests//loadserverscripts.0'
      WindowsError: [Error 32] The process cannot access the file because it is being used by another process: '/data/db/sconsTests//loadserverscripts.0'

      Buildbot V2.4 Windows 64-bit

      WindowsError: [Error 5] Access is denied: '/data/db/sconsTests//local.0'

      This one different: not a test framework error, but rather a failure within a test.

      Buildbot V2.4 Windows 32-bit

            matt.dannenberg Matt Dannenberg
            matt.kangas Matt Kangas
            0 Vote for this issue
            7 Start watching this issue


                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.