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
Bug 1897361: ctrcfg_test: Wait for our prior target config #2229
Bug 1897361: ctrcfg_test: Wait for our prior target config #2229
Conversation
Waiting for the previous MC isn't right here; we're deleting a config and so what we want to wait for is the previous pool target. Drop the racy `sleep()`.
@rphillips: This pull request references Bugzilla bug 1897361, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
=== RUN TestContainerRuntimeConfigLogLevel
--- PASS: TestContainerRuntimeConfigLogLevel (553.14s)
This has fixed it, but still not a great idea of why it happened in the first place, but this PR also makes the ctrcfg test more inline with the mcd tests.
/skip |
well looks like gcp-op isn't the only problem with ci today... sigh all required tests are failing on all prs. |
/retest |
3 similar comments
/retest |
/retest |
/retest |
TestDontDeleteRPMFiles keeps on timing out :( |
I'm pretty sure that's the overall test timeout, not that specific test. See |
LGTM |
/lgtm |
/skip |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest AWS should be better |
/test e2e-gcp-op |
/retest Please review the full test history for this PR and help us cut down flakes. |
/test e2e-gcp-op |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
openshift/cluster-dns-operator#213 (comment) merged (thanks to @cgwalters !), but it'll probably take another run or two before it's in... 👍 almost there! |
/test e2e-gcp-op |
/cherry-pick release-4.6 |
@rphillips: once the present PR merges, I will cherry-pick it on top of release-4.6 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm seeing:
|
It's.. running the tests... AGAIN 😭 It did officially pass gcp-op tho!! https://prow.ci.openshift.org/pr-history/?org=openshift&repo=machine-config-operator&pr=2229 |
e2e-gcp-op is passing again so waiting for this to officially merge (https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/2229/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/1329185639261802496):
|
@rphillips: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
gcp-op passed(!!!) aws-serial did pass once but now failed so let's try again. |
On second thought this PR is only updating our test in gcp-op (tests/e2e/...) and has passed 2x now so the fix works. I'm not going to block on aws-serial as it will never be affected by this pr. /override ci/prow/e2e-aws-serial |
@kikisdeliveryservice: Overrode contexts on behalf of kikisdeliveryservice: ci/prow/e2e-aws-serial In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rphillips: All pull requests linked via external trackers have merged: Bugzilla bug 1897361 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rphillips: new pull request created: #2239 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Waiting for the previous MC isn't right here; we're deleting
a config and so what we want to wait for is the previous pool
target.
Drop the racy
sleep()
.- What I did
- How to verify it
- Description for the changelog