Skip to content
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

Closed
sriharshakandala opened this issue Nov 6, 2024 · 8 comments

Comments

@sriharshakandala
Copy link
Member

The Compare AMIP/Atmos-only with diagnostic EDMF job is failing on benchmarks pipeline.
Please see https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/201 for the error.

cc: @juliasloan25 @szy21

@juliasloan25
Copy link
Member

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

@sriharshakandala
Copy link
Member Author

Thanks. I started a new build here: https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/202

@sriharshakandala
Copy link
Member Author

The CPU ClimaAtmos without diagnostic EDMF job is now failing here:
https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/202

@juliasloan25
Copy link
Member

The CPU ClimaAtmos without diagnostic EDMF job is now failing here: https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/202

The folder it's looking for is

/scratch/clima/slurm-buildkite/climacoupler-cpu-gpu-benchmarks/202/climacoupler-cpu-gpu-benchmarks/experiments/ClimaEarth/output/climaatmos/climaatmos/artifacts/output_active

It looks like there is an output folder output_0000, but no output_active:

[jsloan@clima artifacts]$ pwd
/scratch/clima/slurm-buildkite/climacoupler-cpu-gpu-benchmarks/202/climacoupler-cpu-gpu-benchmarks/experiments/ClimaEarth/output/climaatmos/climaatmos/artifacts
[jsloan@clima artifacts]$ ls
output_0000

The error is when we call ClimaAtmos.get_simulation here. @Sbozzolo do you know why output_active wouldn't appear?

@Sbozzolo
Copy link
Member

Sbozzolo commented Nov 7, 2024

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.

@Sbozzolo
Copy link
Member

Sbozzolo commented Nov 7, 2024

But the, I see this

/scratch/clima/slurm-buildkite/climacoupler-cpu-gpu-benchmarks/202/climacoupler-cpu-gpu-benchmarks/experiments/ClimaEarth/output/climaatmos/climaatmos/artifacts/ already contains some output data, but no active link

Is it possible that multiple jobs are using the same output folder?

@Sbozzolo
Copy link
Member

Sbozzolo commented Nov 7, 2024

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.

@juliasloan25
Copy link
Member

The linked build (https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/202) has passed, so we can close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants