This repository was archived by the owner on Jan 19, 2018. It is now read-only.
Fix CentOS CI Errors #797
Merged
Fix CentOS CI Errors #797
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't know *exactly* why it's failing, but let's try this. Could be related to "foobar" actually going to an internal server.
Merged
Member
Author
|
#dotests |
Member
Author
|
yay, looks like it fixed the tests, going to fix this "upstream" too in kubeshift. |
Contributor
|
should we try to understand the situation here a bit more? would be nice to know the root cause. |
Member
Author
|
No idea :( i can try pinging "foobar" from within the infrastructure and see what's up |
Member
Author
|
I'm going to merge this for now so it prevents the daily email reminders that the build is failing on the CentOS CI |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't know exactly why it's failing, but let's try this. Could be
related to "foobar" actually going to an internal server.