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

test: Update list of allowed level=error logs #16623

Merged
merged 2 commits into from Jun 23, 2021

Conversation

pchaigno
Copy link
Member

Follow up to #16395.

The first commit updates the list now that we have feedback from running with #16395 in CI for a while. The second commit adds a comment to warn against adding more exceptions.

cilium#16477 was merged and a new error,
cilium#16402 (comment) was
discovered since the PR disallowing level=error in CI was merged.

Signed-off-by: Paul Chaignon <paul@cilium.io>
Suggested-by: Joe Stringer <joe@cilium.io>
Signed-off-by: Paul Chaignon <paul@cilium.io>
@pchaigno pchaigno added area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI. labels Jun 22, 2021
@pchaigno pchaigno requested a review from a team as a code owner June 22, 2021 13:50
@pchaigno
Copy link
Member Author

I opened #16632 for the new flake in k8s-1.20-kernel-4.19 as it's clearly unrelated (not failing because of a bad log message). Marking as ready to merge.

@pchaigno pchaigno added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 23, 2021
@christarazi christarazi merged commit 81b1db7 into cilium:master Jun 23, 2021
@pchaigno pchaigno deleted the ci-update-list-allowed-errors branch June 23, 2021 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants