Closed garrettwrong closed 1 year ago
Perhaps the longest running one, tests/test_apple.py::ApplePickerTestCase::testFileCorruption could be corrupted sooner?
Closed by several patches on 11/29. Disabling multiprocessing for Win and OSX on Azure, reducing pytest multiprocessing pool size, and patching a bug wrt pool launching.
Locally they run reasonably fast (10-15m sequentially), but our Azure tests seem to take 30-60 minutes. If the total azure test takes over 60 minutes, the job is killed and fails CI.
We should
Regarding the second point, I placed example py37 timings from my macbook below. These are from
develop
at c3b13f4a. I filtered just the tests executing over one second. It's actually not as bad as I thought... so we might need to focus a little more on the platform/setup.