Skip to content

TestServiceWithDefaultAddressPoolInit#37836

Merged
thaJeztah merged 1 commit intomoby:masterfrom
selansen:test_initpool
Jul 15, 2019
Merged

TestServiceWithDefaultAddressPoolInit#37836
thaJeztah merged 1 commit intomoby:masterfrom
selansen:test_initpool

Conversation

@selansen
Copy link
Contributor

    Looks like TestServiceWithDefaultAddressPoolInit is failing
    randomly in CI. I am not able to reproduce the issue locally
    but this has been reported few times.  So I tried to modify
    code and see if I can fix the random failure.

Signed-off-by: selansen [email protected]

- What I did

- How I did it

- How to verify it

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

@thaJeztah
Copy link
Member

ping @kolyshkin

@kolyshkin
Copy link
Contributor

@selansen once you have a failure, take a look at the relevant daemon.log, maybe there's some hints in there. I have a couple of other test cases involving swarm that fail randomly, and it's only happening in CI and never locally, such as #37833. I figured out the code flow, scrutinized the source code, but still don't have a clue about what is going on :(

@AkihiroSuda
Copy link
Member

What's current status?

@olljanat
Copy link
Contributor

@selansen this one needs to be rebased

@derek derek bot added the status/failing-ci Indicates that the PR in its current state fails the test suite label Dec 22, 2018
Looks like TestServiceWithDefaultAddressPoolInit is failing
randomly in CI. I am not able to reproduce the issue locally
but this has been reported few times.  So I tried to modify
code and see if I can fix the random failure.

Signed-off-by: selansen <[email protected]>
Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah thaJeztah removed the status/failing-ci Indicates that the PR in its current state fails the test suite label Jul 14, 2019
@codecov
Copy link

codecov bot commented Jul 14, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@f4da929). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #37836   +/-   ##
=========================================
  Coverage          ?   37.31%           
=========================================
  Files             ?      609           
  Lines             ?    45232           
  Branches          ?        0           
=========================================
  Hits              ?    16877           
  Misses            ?    26065           
  Partials          ?     2290

@thaJeztah
Copy link
Member

rebased

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🐯

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

not sure if this fixes the flakiness, but changes don't look like they'll harm, so bringing this in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants