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
arm is significantly slower - either the machine we are using is not big enough, or it is emulated, or github offering is not really good...
build time overall is consistent - at 4 minutes though, we should be able to cut that to 1 minute or less (implies rethinking the way we build the image and possibly push the "dependencies" part on a registry instead of rebuilding them every time)
windows testing is really weak, with 100 safe tests, and 100 flaky tests
we now have about 300 safe tests (not counting ipv6 and kube), and about 650 "flaky" tests - so, about 1/3 are considered safe - when the container tests suite will be done, the balance should shift towards 50%
for the worst offenders:
TestCopy are very slow - current in-progress rewrite will parallelize and reduce this
Compose tests are definitely the number 1 contributor (including some IPFS tests) - we should look into this and figure out why compose is so slow
current flakyness status
2 failed runs out of the 8 main target platforms (with 4 test failures) - these are both TestIPFSCompNoBuild - the issue being likely [MAJOR] content digest not found #3513 (it might be a snapshotter issue though, and not a nerdctl one)
4 "rewritten" tests are explicitly flagged as flaky (3 on windows, 1 on IPFS)
9 tests are currently disabled (marked NerdctlNeedsFixing), although some of them might have been fixed recently - they should be reviewed
With the current effort on testing, we should start looking into our run duration, platform coverage, and hard data on flakyness / disabled tests.
This issue here is to record that information over time.
This is the first sample (of #3535), ran on 10/19/2024
ipv6: 331 tests, 325 skipped in 15.012s
Here is the list of the worst offenders (taken from the arm run):
Current take-aways:
containertests suite will be done, the balance should shift towards 50%TestIPFSCompNoBuild- the issue being likely [MAJOR] content digest not found #3513 (it might be a snapshotter issue though, and not a nerdctl one)NerdctlNeedsFixing), although some of them might have been fixed recently - they should be reviewedTagging @djdongjin @AkihiroSuda
Will post other samples on this ticket in the future to track progress.