Open timuthy opened 3 years ago
It is a known flaky test case and it never occurs when you run test cases locally, it always occurs in pipeline.
It probably occurs due to CPU throttling or in general less computing power during the pipeline runs. However, it'd be beneficial to improve this test and eliminate its flakiness because it blocks PRs and releases on a regular basis.
It probably occurs due to CPU throttling or in general less computing power during the pipeline runs
ok, if that’s the case then migrating the unit test to use gomock pkg
will solve this issue.
Updated the issue to track all flaky tests in backup-restore.
How to categorize this issue? /area testing /kind flake
Which test(s)/suite(s) are flaking:
[ ] Defragmentor suite falky tests:
Logs
time="2021-10-27T08:32:00Z" level=info msg="Defragmenting etcd member[127.0.0.1:39459]" job=defragmentor suite=defragmentor
time="2021-10-27T08:32:00Z" level=info msg="Finished defragmenting etcd member[127.0.0.1:39459]" job=defragmentor suite=defragmentor
time="2021-10-27T08:32:00Z" level=info msg="Probable DB size change for etcd member [127.0.0.1:39459]: 376832B -> 372736B after defragmentation" job=defragmentor suite=defragmentor
• Failure [14.864 seconds]
Defrag Defragmentation [It] should defragment and reduce size of DB within time
/tmp/build/bc4dbee3/pull-request-gardener.etcd-backup-restore-pr.master/pkg/defragmentor/defrag_test.go:67
Expected
to be <
/tmp/build/bc4dbee3/pull-request-gardener.etcd-backup-restore-pr.master/pkg/defragmentor/defrag_test.go:89
Full Stack Trace
github.com/gardener/etcd-backup-restore/pkg/defragmentor_test.glob..func1.2.2()
github.com/gardener/etcd-backup-restore/pkg/defragmentor_test.TestDefragmentor(0xc000643980)
testing.tRunner(0xc000643980, 0x2936380)
created by testing.(*T).Run
Logs
Logs