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

Fix integration test failures in dind. #3632

Merged
merged 1 commit into from
Dec 11, 2020
Merged

Conversation

dlorenc
Copy link
Contributor

@dlorenc dlorenc commented Dec 11, 2020

Changes

These were failing during "docker build" with a cgroup/OOM score issue.
After some digging, I found a similar report here: k3s-io/k3s#1164 (comment)
It looks like something related to the intersecton of new versions of docker and containerd based clusters,
where the pod dind is running in did not set memory limits.

/kind failing-test

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

NONE

@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 11, 2020
@dlorenc
Copy link
Contributor Author

dlorenc commented Dec 11, 2020

/test pull-tekton-pipeline-integration-tests

This failure was a different test! I think we have a winner.

These were failing during "docker build" with a cgroup/OOM score issue.
After some digging, I found a similar report here: k3s-io/k3s#1164 (comment)
It looks like something related to the intersecton of new versions of docker and containerd based clusters,
where the pod dind is running in did not set memory limits.
@dlorenc dlorenc changed the title WIP: testing a fix for e2e tests. Fix integration test failures in dind. Dec 11, 2020
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Dec 11, 2020
@ghost
Copy link

ghost commented Dec 11, 2020

/approve
/lgtm

@tekton-robot tekton-robot assigned ghost Dec 11, 2020
@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 11, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbwsg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 11, 2020
@tekton-robot tekton-robot merged commit ccfe5d2 into tektoncd:master Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants