Skip to content

[WIP] Reduce baseline footprint - #3254

Draft
BrianCurtis-NOAA wants to merge 31 commits into
ufs-community:developfrom
BrianCurtis-NOAA:small_bl_footprint
Draft

[WIP] Reduce baseline footprint#3254
BrianCurtis-NOAA wants to merge 31 commits into
ufs-community:developfrom
BrianCurtis-NOAA:small_bl_footprint

Conversation

@BrianCurtis-NOAA

Copy link
Copy Markdown
Collaborator

Commit Queue Requirements:

  • This PR addresses a relevant WM issue (if not, create an issue).
  • All subcomponent pull requests (if any) have been reviewed by their code managers.
  • Run the full Intel+GNU RT suite (compared to current baselines), preferably on Ursa (Derecho or Hercules are acceptable alternatives). Exceptions: documentation-only PRs, CI-only PRs, etc.
    • Commit log file w/full results from RT suite run (if applicable).
    • Verify that test_changes.list indicates which tests, if any, are changed by this PR. Commit test_changes.list, even if it is empty.
  • Fill out all sections of this template.

Description:

[WORK IN PROGRESS]

  • This PR will be testing along side the current PR process to see what other changes might be needed over the course of a month. Questions might need to be answered on how long we can keep this method up until we need to delete older baselines, and how that might work.

[WORK IN PROGRESS]

The current system of storage for baselines will copy/mv all baselines into a new bl_date regardless if the test changed baselines. This causes a lot of overlap between PR's that only change a few tests.

The work in this PR is meant to add a new function to the rt.sh called "Final Testing" which will add the '-f' option.

This -f option will make changes to the repository in tests/tests (where the bl_date will now be stored). This move will allow rt.sh to have a unique bl_date for every test. The -f option will also create the log file, and test_changes.list

I would recommend all PR's now use this -f option after a PR meets all criteria (minus what we would typically ask for in final testing, i.e. logs & test_changes.list) and it is ready for final testing. Then we will have the PR author run final testing as a final step before getting into the commit queue.

Commit Message:

* UFSWM - Update methodology of baseline storage to minimize footprint.

Priority:

  • Critical Bugfix: Reason
  • High: Reason
  • Normal

Git Tracking

UFSWM:

Sub component Pull Requests:

  • None

UFSWM Blocking Dependencies:

  • Blocked by #
  • None

Documentation:

  • Documentation update required.
    • Relevant updates are included with this PR.
    • A WM issue has been opened to track the need for a documentation update; a person responsible for submitting the update has been assigned to the issue (link issue).
  • Documentation update NOT required.
    • Explanation:

Changes

Regression Test Changes (Please commit test_changes.list):

  • PR Adds New Tests/Baselines.
  • PR Updates/Changes Baselines.
  • No Baseline Changes.

Input data Changes:

  • None.
  • PR adds input data.
  • PR changes existing input data.

Library Changes/Upgrades:

  • Required
    • Library names w/versions:
    • Git Stack Issue (JCSDA/spack-stack#)
  • No Updates

Testing Log:

  • RDHPCS
    • Orion
    • Hercules
    • GaeaC6
    • Derecho
    • Ursa
  • WCOSS2
    • Dogwood/Cactus
    • Acorn
  • CI
  • opnReqTest (complete task if unnecessary)

Testing Remarks:

@gspetro-NOAA gspetro-NOAA added the No Baseline Change No Baseline Change label Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

No Baseline Change No Baseline Change

Projects

Status: Evaluating

Development

Successfully merging this pull request may close these issues.

Improve baseline footprint

2 participants