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

Change one derecho_nvhpc.clm-crop test to expected fail in RUN #2968

Open
samsrabin opened this issue Feb 15, 2025 · 0 comments
Open

Change one derecho_nvhpc.clm-crop test to expected fail in RUN #2968

samsrabin opened this issue Feb 15, 2025 · 0 comments
Assignees
Labels
bfb bit-for-bit enhancement new capability or improved behavior of existing capability testing additions or changes to tests

Comments

@samsrabin
Copy link
Collaborator

samsrabin commented Feb 15, 2025

This test is expected to fail in SHAREDLIB_BUILD:

<test name="SMS_D.f10_f10_mg37.I2000Clm60BgcCrop.derecho_nvhpc.clm-crop">
<phase name="SHAREDLIB_BUILD">
<status>FAIL</status>
<issue>#1733</issue>
</phase>
</test>

However, it is now passing SHAREDLIB_BUILD for me, and it turns out it's been passing for others too:

In what will be ctsm5.3.014 the test SMS_D.f10_f10_mg37.I2000Clm60BgcCrop.derecho_nvhpc.clm-crop now passes the BUILD phase and fails at RUN, pretty early in the mediator.

Originally posted by @ekluzek in #1733

Does anyone (@samsrabin?) know why SMS_D.f10_f10_mg37.I2000Clm60BgcCrop.derecho_nvhpc.clm-crop RUN time=35 ? The log files don't really show anything at all. Only the med.log and cesm.log have anything in them at all.

Originally posted by @adrifoster in #2952 (comment)

Fixing this should involve adding a new issue to include as a reference (if one doesn't already exist).

@samsrabin samsrabin added testing additions or changes to tests enhancement new capability or improved behavior of existing capability next this should get some attention in the next week or two. Normally each Thursday SE meeting. bfb bit-for-bit labels Feb 15, 2025
@wwieder wwieder removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Feb 20, 2025
@wwieder wwieder added this to the ctsm6.0.0 (code freeze) milestone Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bfb bit-for-bit enhancement new capability or improved behavior of existing capability testing additions or changes to tests
Projects
None yet
Development

No branches or pull requests

2 participants