-
Notifications
You must be signed in to change notification settings - Fork 371
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
update circleci image spec due to upstream changes #6277
Conversation
|
We can probably get rid of circle ci and replace it with a github action. Its doing a build-only test of a fully coupled case. The command to do that is: |
Hi @rljacob, I agree, I just didn't want to be the one proposing the change :) I went ahead and implemented a fix that will allow us to avoid their planned brownouts and blackouts, but we can drop this PR and/or simply get rid of our CircleCI runs. I was hoping to propose getting rid of CircleCI testing once I manage to upgrade our images from 20.04 to 22.04 (see this PR: mahf708/e3sm-imgs#13, I just didn't have enough time to test changes locally, but I am hoping it will be a quick work once I get to it) |
Also, note that this PR was in response to us experiencing a brownout in PR #6276 (see my note on top: #6277 (comment)) |
Addresses CircleCI new image requirements, lest we are affected by brownouts and eventual blackouts. [BFB]
Addresses CircleCI new image requirements, lest we are affected by brownouts and eventual blackouts.
--
We expreienced our first brownout in https://app.circleci.com/pipelines/github/E3SM-Project/E3SM/10529/workflows/8d2afe3d-53a7-456d-ae39-ecf6378f23f9/jobs/10059 (as part of PR #6276). See the note by CircleCI here: https://discuss.circleci.com/t/linux-image-deprecations-and-eol-for-2024/50177. The fix in this PR is simply putting a band-aid on our CircleCI testing until we have some time for a proper fix and for a thorough upgrade of our containers.