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.

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

travis: update configuration #2222

Merged
merged 1 commit into from
Mar 6, 2020
Merged

travis: update configuration #2222

merged 1 commit into from
Mar 6, 2020

Conversation

cyphar
Copy link
Member

@cyphar cyphar commented Feb 5, 2020

Update the set of Go versions (and use 1.x to always test the latest
release), as well as making the cgroupv2 tests allowable failures (the
vagrant setup seems to break pretty often, causing flaky failures).

Signed-off-by: Aleksa Sarai asarai@suse.de

Update the set of Go versions (and use 1.x to always test the latest
release), as well as making the cgroupv2 tests allowable failures (the
vagrant setup seems to break pretty often, causing flaky failures).

Signed-off-by: Aleksa Sarai <asarai@suse.de>
@@ -29,6 +32,7 @@ matrix:
- ssh default sudo podman run --privileged --cgroupns=private test make localunittest
allow_failures:
- go: tip
- name: "cgroup-v2"
Copy link
Member

Choose a reason for hiding this comment

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

can we add retry code to the v2 setup script instead?

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe, but the v2 tests also take the longest to run -- I'm not a huge fan of the idea of having possibly-regular >1hr test runs.

Choose a reason for hiding this comment

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

@cyphar: I'm not a huge fan of the idea of having possibly-regular >1hr test runs.

Compared to how little the CI is exercised here, that seems like an acceptable trade-off for not breaking things...? "Acceptable failures" often quickly degenerate unless someone pays close attention to them. Wouldn't it be better to try to figure out what's causing the flakes and fixing that?

@AkihiroSuda
Copy link
Member

AkihiroSuda commented Mar 4, 2020

LGTM

Approved with PullApprove

@AkihiroSuda
Copy link
Member

@mrunalp PTAL?

@crosbymichael
Copy link
Member

crosbymichael commented Mar 6, 2020

LGTM

Approved with PullApprove

@crosbymichael crosbymichael merged commit fc5759c into opencontainers:master Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants