Remove @avoid_ci from stress tests
- Related to #5371
- Blocked by #6577
Currently crashes also in the case without AMM. I believe this is due to having 10 nannies on 2-4 CPUs.
Unit Test Results
10 files - 5 10 suites - 5 1h 52m 4s :stopwatch: - 4h 58m 35s 152 tests - 2 623 120 :heavy_check_mark: - 2 574 4 :zzz: - 75 28 :x: +26 622 runs - 19 965 561 :heavy_check_mark: - 19 118 4 :zzz: - 902 57 :x: +55
For more details on these failures, see this check.
Results for commit b1d92073. ± Comparison against base commit 50d29110.
:recycle: This comment has been updated with latest results.
Unit Test Results
See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.
8 files - 7 8 suites - 7 3h 13m 34s :stopwatch: - 3h 18m 10s 157 tests - 2 928 133 :heavy_check_mark: - 2 866 2 :zzz: - 83 22 :x: +21 673 runs - 22 154 619 :heavy_check_mark: - 21 222 4 :zzz: - 981 50 :x: +49
For more details on these failures, see this check.
Results for commit 8e4248d4. ± Comparison against base commit a5d68657.
:recycle: This comment has been updated with latest results.
- Blocked by #6577
Currently crashes also in the case without AMM. I believe this is due to having 10 nannies on 2-4 CPUs.
Note that #6577 will allow this PR to just switch to Workers from Nannies, which should solve the problem while still testing all the AMM machinery. It will not solve the more generic #5371.
Superseded by #7062