Mocking the FixedIntervalLoopingCall doesn't help either. We don't face JSON serializable error anymore, but the test suites are very slow. Only around 3200 unit tests were executed in last 24hrs.
FWIW, with or without patch, the first 2200 tests are executed quickly within 10mins. It takes double the amount of time for each consecutive tests. For example, after executing 2200 tests, if it takes 1min for a test, it takes 2min for next test, 4mins for next test, 8mins and so on for remaining tests. However, if we run those tests alone separately they are successful and completed within a minute.
I'm going to see if I could narrow-down the reason for delay with cProfile. Meanwhile let me know if you got any other clue.
Thank you for the suggestion, ZhiQiang.
Mocking the FixedIntervalLo opingCall doesn't help either. We don't face JSON serializable error anymore, but the test suites are very slow. Only around 3200 unit tests were executed in last 24hrs.
FWIW, with or without patch, the first 2200 tests are executed quickly within 10mins. It takes double the amount of time for each consecutive tests. For example, after executing 2200 tests, if it takes 1min for a test, it takes 2min for next test, 4mins for next test, 8mins and so on for remaining tests. However, if we run those tests alone separately they are successful and completed within a minute.
I'm going to see if I could narrow-down the reason for delay with cProfile. Meanwhile let me know if you got any other clue.