You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2020. It is now read-only.
When running the Drive unit tests, after and sometimes during the testing the execute the TestDrive executable, the TestDrive will remain mounted, quickly consuming all system resources, and causing all later tests to fails. This only appears to occur on virtualized machines.
Running the failed tests through the debugger after cleaning up the TestDrive mounts left behind from the unit test run, will obviously work, as the system now has resources available again.
This is a big issue for continuous integration servers as it prevents them running uninterrupted for more than one night.
Test Machines affected:
CI-Ubuntu11-32bit
CI-Ubuntu11-64bit
The text was updated successfully, but these errors were encountered:
When running the Drive unit tests, after and sometimes during the testing the execute the TestDrive executable, the TestDrive will remain mounted, quickly consuming all system resources, and causing all later tests to fails. This only appears to occur on virtualized machines.
Running the failed tests through the debugger after cleaning up the TestDrive mounts left behind from the unit test run, will obviously work, as the system now has resources available again.
This is a big issue for continuous integration servers as it prevents them running uninterrupted for more than one night.
Test Machines affected:
CI-Ubuntu11-32bit
CI-Ubuntu11-64bit
The text was updated successfully, but these errors were encountered: