-
Notifications
You must be signed in to change notification settings - Fork 199
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
ci: Split codestyle checks into separate context #1364
Conversation
Prep for reworking the primary test to do vm-in-container, which will temporarily be vm-in-container-in-vm. See coreos#1362
💔 Test failed - status-atomicjenkins |
Weird, not sure why it timed out there. @rh-atomic-bot retry |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
OK, I think this is PAPR actually crashing. Retrying and keeping a close eye this time. |
OK, it's just hitting:
a lot. Something that I've been seeing myself with the f28 image. I just bumped it down to f27 for now. |
💔 Test failed - status-atomicjenkins |
Looks like somehow the jigdo content in CCI got nuked...the next build run regenerated it anyways. |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
💥 Test timed out |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
Something weird going on with the |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
☀️ Test successful - status-atomicjenkins |
Prep for reworking the primary test to do vm-in-container, which
will temporarily be vm-in-container-in-vm.
See #1362