-
Notifications
You must be signed in to change notification settings - Fork 339
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
[DNM] Test CI #1654
[DNM] Test CI #1654
Conversation
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 42s |
recheck |
@alinabuzachis Now the integration tests ran into a cc @jillr |
recheck |
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
recheck |
@alinabuzachis and I are working on it :-) |
recheck |
1 similar comment
recheck |
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
recheck |
This looks weird, I don't understand it at all :-/ |
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 22s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 31s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 38s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 32s |
@alinabuzachis @goneri I've seen those node failures in the past: #1260 Not sure if this is the same issue but maybe it helps you to troubleshoot. |
recheck |
@alinabuzachis the node_failure error only affects the jobs that depend on an ESXi, it may be a problem with the image name. Also, you may want to check the checksum and size of the images. |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 26s |
recheck |
1 similar comment
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 36s |
recheck |
@alinabuzachis @goneri Thanks, it looks better now! The last failure was something I see from time, some network problem or similar... so unrelated. I'll keep this open and do rechecks until I see a complete success, but I think the basic problems are solved 🥳 |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 8m 25s |
Thanks @alinabuzachis @goneri! |
SUMMARY
Test CI
ISSUE TYPE
COMPONENT NAME
vmware_vswitch
ADDITIONAL INFORMATION
#1051