-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ON HOLD] Disable TestIPFSComposeUp #3396
[ON HOLD] Disable TestIPFSComposeUp #3396
Conversation
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
c913f68
to
0f41939
Compare
@@ -31,6 +31,8 @@ import ( | |||
) | |||
|
|||
func TestIPFSComposeUp(t *testing.T) { | |||
t.Skip("This is currently broken and failing very often. It is unclear if the test or the code is faulty.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a link to the github issue w/ failure logs
I'm trying to reproduce this flakiness on GitHub Actions but I can't reproduce this (passed 3 times / 3 attemptions). 🤔 |
Thanks a lot for looking into this @ktock. Here are a couple of links with potentially more info:
One example of failure on the above happening after a couple of tries: https://github.com/containerd/nerdctl/actions/runs/10433233259/job/28894754561?pr=3305#step:7:531 It also happens regularly on normal PRs: unfortunately not sure how to access the logs of this one ^ since we manually restarted it. Will send more as soon as we hit it again. |
I still think we should remove the retries entirely: #3400 It would be extremely painful for a few weeks, but we would be much better off in the long run... |
@ktock I just hit the "cannot start a stopped container" variant of it: https://github.com/containerd/nerdctl/actions/runs/10690479035/job/29634950871
|
@ktock were you able to reproduce this locally? |
@ktock any update? |
@ktock @AkihiroSuda I have a local version (with #3490 + custom cni plugins + rewritten tests) and had it run 100+ times without breaking (I had to disable some estargz tests though - they are currently passing only because of side effects with other tests - see #3475). I will send the rest of the changes for review later on. In the meantime, closing this. |
This test is failing a lot.
Even despite the fact that we do retry all tests, it still regularly fail builds, with a variety of different errors (
cannot start a stopped container
,reuse of closed network connections
, etc).While it is unclear whether the test or the underlying code is faulty, and despite some time spent investigating it with no success, this test serves no purpose given its current condition, and there does not seem to be interest in fixing it.
Suggesting we disable it.