Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Flaky test: lib network TestRequestReleaseAddressDuplicate #42612

Closed
thaJeztah opened this issue Jul 9, 2021 · 0 comments · Fixed by #45019
Closed

Flaky test: lib network TestRequestReleaseAddressDuplicate #42612

thaJeztah opened this issue Jul 9, 2021 · 0 comments · Fixed by #45019
Labels
area/networking area/testing kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.

Comments

@thaJeztah
Copy link
Member

Seen failing on #42511 and #42607

=== RUN   TestRequestReleaseAddressDuplicate
    allocator_test.go:1533: IP 198.168.1.22/23 was previously allocated
--- FAIL: TestRequestReleaseAddressDuplicate (0.04s)

https://ci-next.docker.com/public/blue/rest/organizations/jenkins/pipelines/moby/branches/PR-42607/runs/3/nodes/309/log/?start=0

win-2022-integration-bundles-2.zip
@thaJeztah thaJeztah added kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. area/networking area/testing labels Jul 9, 2021
This was referenced Jul 9, 2021
Merged
Merged
@olljanat olljanat mentioned this issue Aug 9, 2021
Merged
@thaJeztah thaJeztah mentioned this issue Aug 27, 2021
Merged
@thaJeztah thaJeztah mentioned this issue Oct 26, 2021
Merged
@thaJeztah thaJeztah mentioned this issue Nov 11, 2021
Closed
This was referenced Dec 21, 2021
Merged
Closed
@thaJeztah thaJeztah mentioned this issue Feb 15, 2022
Merged
@thaJeztah thaJeztah mentioned this issue Jan 20, 2023
Merged
@corhere corhere mentioned this issue Feb 16, 2023
Merged
@thaJeztah thaJeztah mentioned this issue Mar 3, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/networking area/testing kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

libnetwork/ipam: fix racy, flaky unit test corhere/moby
1 participant
@thaJeztah