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
We have switched our tests to Semaphore CI (#1266) and we got a execution time boost (~2x).
We also restored the ci_retry function (#1573) because the integration tests are still flaking.
I'm starting to deploy a simple scenario based on tests series to obtain a closer perimeter and to understand which tests have the higher "flaky probability".
Reiterating the same test on semaphore 100 times (deactivating the ci_retry function),
i get those results: link
The text was updated successfully, but these errors were encountered:
Series: S2 (acme and eureka tests are executed first):
KO: 15%
higher errors:
acme_test 7
eureka_test 4
Acme and eureka tests are still the tests with the higher flaky probability.
The test's order doesn't affect the final results so we "could" exclude an hw resource exhaustion issue.
We have switched our tests to Semaphore CI (#1266) and we got a execution time boost (~2x).
We also restored the ci_retry function (#1573) because the integration tests are still flaking.
I'm starting to deploy a simple scenario based on tests series to obtain a closer perimeter and to understand which tests have the higher "flaky probability".
Reiterating the same test on semaphore 100 times (deactivating the ci_retry function),
i get those results: link
The text was updated successfully, but these errors were encountered: