Skip to content

[develop] Remove Slurm Memory Option for noaacloud#506

Merged
MichaelLueken merged 1 commit into
ufs-community:developfrom
EdwardSnyder-NOAA:feature/noaacloud-slurm-mem
Dec 6, 2022
Merged

[develop] Remove Slurm Memory Option for noaacloud#506
MichaelLueken merged 1 commit into
ufs-community:developfrom
EdwardSnyder-NOAA:feature/noaacloud-slurm-mem

Conversation

@EdwardSnyder-NOAA
Copy link
Copy Markdown
Collaborator

@EdwardSnyder-NOAA EdwardSnyder-NOAA commented Dec 5, 2022

DESCRIPTION OF CHANGES:

Added logic to not include the slurm memory option for our NOAA cloud platforms. Testing the development branch of the SRW App on NOAA cloud platforms revealed this error:
"FV3LAM_wflow.xml :: sbatch: error: Memory specification can not be satisfied"

Slurm on NOAA cloud wasn't setup like the rest of the RDHPCs, so there isn't a good way to configure its memory. Removing the slurm memory option allows for the experiment to complete successfully.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

TESTS CONDUCTED:

  • hera.intel
  • orion.intel
  • cheyenne.intel
  • cheyenne.gnu
  • gaea.intel
  • jet.intel
  • wcoss2.intel
  • NOAA Cloud (indicate which platform)
  • Azure and GCP
  • Jenkins
  • fundamental test suite
  • comprehensive tests (specify which if a subset was used)

DEPENDENCIES:

DOCUMENTATION:

ISSUE:

The slurm memory logic was reported in Issue #349 and was addressed in PR #443.

CHECKLIST

  • My code follows the style guidelines in the Contributor's Guide
  • I have performed a self-review of my own code using the Code Reviewer's Guide
  • I have commented my code, particularly in hard-to-understand areas
  • My changes need updates to the documentation. I have made corresponding changes to the documentation
  • My changes do not require updates to the documentation (explain).
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • Any dependent changes have been merged and published

LABELS (optional):

A Code Manager needs to add the following labels to this PR:

  • Work In Progress
  • bug
  • enhancement
  • documentation
  • release
  • high priority
  • run_ci
  • run_we2e_fundamental_tests
  • run_we2e_comprehensive_tests
  • Needs Cheyenne test
  • Needs Jet test
  • Needs Hera test
  • Needs Orion test
  • help wanted

CONTRIBUTORS (optional):

Discussed with @danielabdi-noaa the origins of the Issue and PR.

Copy link
Copy Markdown
Collaborator

@MichaelLueken MichaelLueken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@EdwardSnyder-NOAA These changes look good to me! Tests were run on Gaea to ensure continued functionality. All tests passed successfully. Approving now.

@MichaelLueken MichaelLueken merged commit 53c62ca into ufs-community:develop Dec 6, 2022
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

Successfully merging this pull request may close these issues.

3 participants