-
Notifications
You must be signed in to change notification settings - Fork 5
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
Compare AMIP/Atmos-only with diagnostic EDMF
job is failing on benchmarks
pipeline
#1064
Comments
Thanks for flagging this! It should be fixed by #1054, which was merged on Monday. I had missed propagating some changes to the benchmark comparison code. The job should run and pass this Sunday |
Thanks. I started a new build here: https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/202 |
The |
The folder it's looking for is
It looks like there is an output folder
The error is when we call |
This error is rather mysterious to me. The code in OutputPathGenerator is link_exists = islink(active_link)
if link_exists
target = readlink(active_link) So, reaching the line where we read the link means that we passed the line where we checked if there's a link. |
But the, I see this
Is it possible that multiple jobs are using the same output folder? |
Okay. I think I know what's happening. The first time the job was run it failed due to an intermitted filesystem issue/slowdown (the error is "output path not synced"). This left the folder structure in a partially broken state, so the second time the job was run, it failed again. Running the second time cleaned some things up and allowed the system reset for the third attempt. |
The linked build (https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/202) has passed, so we can close this issue |
The
Compare AMIP/Atmos-only with diagnostic EDMF
job is failing onbenchmarks
pipeline.Please see https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/201 for the error.
cc: @juliasloan25 @szy21
The text was updated successfully, but these errors were encountered: