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

Optimize fundamental test suite coverage #445

Closed
danielabdi-noaa opened this issue Oct 30, 2022 · 0 comments
Closed

Optimize fundamental test suite coverage #445

danielabdi-noaa opened this issue Oct 30, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@danielabdi-noaa
Copy link
Collaborator

Description

Currently the 9 fundamental test suites are run on each platform (5 of them) repeatedly. I think this is a huge waster of resources, and can be optimized by assigning different test cases to each platform, different modes (nco/community). Variety should provide more "bang for the buck" than running the same tests on all platforms. Also some systems (cheyenne & jet) often finish later than the others, so some sort of load balancing can potentially be achieved.

Solution

Customise fundamental test suite for each platform e.g. fundamental.hera and for testing mode (nco or community mode) e.g. fundamental.hera.nco.

Requirements**

None

Acceptance Criteria (Definition of Done)

Customized fundamental test suites for each platform, some of them running exclusively nco mode. Both CIs should work in this mode. Github actions currently runs only on Hera and Jet, so there should be more differences between Hera & Jet.

Dependencies (optional)

None

Alternative Solutions (optional)

None

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

No branches or pull requests

1 participant