Skip to content

Frozen busybox latest glibc#36375

Merged
thaJeztah merged 2 commits intomoby:masterfrom
arm64b:frozen-busybox-latest-glibc
Feb 28, 2018
Merged

Frozen busybox latest glibc#36375
thaJeztah merged 2 commits intomoby:masterfrom
arm64b:frozen-busybox-latest-glibc

Conversation

@arm64b
Copy link
Contributor

@arm64b arm64b commented Feb 22, 2018

As the follow-up of PR #36298, this PR:

  1. Adding both busybox:latest and busybox:glibc into docker container as frozen images
  2. Using busybox:glibc instead of busybox:latest as the testing image explicitly for those network related test cases.

- What I did
Using busybox:1.27-glibc as the image to test network related test cases (ping issue)
- How I did it
Adding both glibc and latest tagged busybox into frozen images
- How to verify it
make test-integration
- Description for the changelog

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

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 🐸

@arm64b
Copy link
Contributor Author

arm64b commented Feb 22, 2018

Thanks @vdemeester for the quick response 👍 !
Just checked the CI result, interesting, seems the service image busybox in the simpleTestService() have to be tagged by latest, otherwise the CreateService() cannot create the busybox /bin/top service.
Because TestAPISwarmHealthcheckNone test case will ping sth, so we have to point the service image to busybox: glibc instead of busybox:latest, that will be a dilemma...
Will investigate further tomorrow.
@vdemeester , @tianon @dnephin @thaJeztah PTAL first?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

mark

@dnephin
Copy link
Member

dnephin commented Feb 22, 2018

changes sgtm

Copy link
Member

@tianon tianon left a comment

Choose a reason for hiding this comment

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

LGTM

(any particular reason we're pinning explicitly to 1.27-glibc instead of just glibc?)

@arm64b arm64b force-pushed the frozen-busybox-latest-glibc branch from 80c6ef5 to 7770707 Compare February 23, 2018 02:45
@codecov
Copy link

codecov bot commented Feb 23, 2018

Codecov Report

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

@@            Coverage Diff            @@
##             master   #36375   +/-   ##
=========================================
  Coverage          ?   34.65%           
=========================================
  Files             ?      612           
  Lines             ?    45297           
  Branches          ?        0           
=========================================
  Hits              ?    15697           
  Misses            ?    27543           
  Partials          ?     2057

@arm64b arm64b force-pushed the frozen-busybox-latest-glibc branch from 7770707 to dc7aa30 Compare February 23, 2018 05:41
@arm64b
Copy link
Contributor Author

arm64b commented Feb 23, 2018

The only issue we need to resolve for this PR is #36386 , maybe we have some potential problems with the CreateService api?

@arm64b
Copy link
Contributor Author

arm64b commented Feb 23, 2018

(any particular reason we're pinning explicitly to 1.27-glibc instead of just glibc?)

No special reason, if any, maybe there're some testing noise in my local system prevent me from avoiding a little big changes, so I'd like to get to the target gradually 🤗

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 if green 😄

Adding `busybox:latest` and `busybox:glibc` as the frozen images

Signed-off-by: Dennis Chen <dennis.chen@arm.com>
@arm64b arm64b force-pushed the frozen-busybox-latest-glibc branch from fc3b8c3 to e429c82 Compare February 27, 2018 06:50
Using the `busybox:glibc` instead of `busybox:latest` to the
network related test cases (`ping` issue).

Signed-off-by: Dennis Chen <dennis.chen@arm.com>
@arm64b arm64b force-pushed the frozen-busybox-latest-glibc branch from e429c82 to 0d31dee Compare February 27, 2018 06:53
@arm64b
Copy link
Contributor Author

arm64b commented Feb 27, 2018

Hello @vdemeester , I dig into the CI failure cases last night and make some little tweak for the codes today, now from the CI result, I believe the failure on node powerpc and z are testing noise:
powerpc: ...............................................no space left on device
z: only DockerSwarmSuite.TearDownTest fails

So I bet this time if you rebuild the 2 nodes, we will win 🤗, else I owe you a bottle of beer🐸

@arm64b
Copy link
Contributor Author

arm64b commented Feb 28, 2018

Oops, seems I lost a bottle of beer but actually not, because we human beings think the powerpc machine is not reliable recently 😈 This point can be backed by the CI result of the PRs submitted these days...

@thaJeztah
Copy link
Member

Yeah, restarted the PPC build, I think some of them were cleaned up

@arm64b
Copy link
Contributor Author

arm64b commented Feb 28, 2018

OK, thanks @thaJeztah , apparently you are a lucky man, now it's green 😺

@thaJeztah
Copy link
Member

Can't take credits for that; I think the test-infra team and @vdemeester have been cleaning up nodes that were running out of disk space 🤗

@thaJeztah thaJeztah merged commit 3e0299f into moby:master Feb 28, 2018
@arm64b
Copy link
Contributor Author

arm64b commented Feb 28, 2018

Ah, a very tough CI battle we have experienced together🤗, and from the CI I found we still have some tear-down steps in CI need to be enhanced, so it's not bad thing 👍

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.

7 participants