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

Create 'suites' directory, test re-org #742

Open
Paul-Ferrell opened this issue Feb 29, 2024 · 0 comments · May be fixed by #782
Open

Create 'suites' directory, test re-org #742

Paul-Ferrell opened this issue Feb 29, 2024 · 0 comments · May be fixed by #782
Assignees
Milestone

Comments

@Paul-Ferrell
Copy link
Collaborator

Paul-Ferrell commented Feb 29, 2024

We should add a new config dir - suites, and deprecate the test_src and tests directory.

In a suites directory:

  • a single yaml file can contain a suite named for that file (as per tests currently)

  • a directory, containing:

    • a suite.yaml file (required), with the suite configuration.
    • a hosts.yaml file (optional) containing host specific configs (unlike regular hosts files, these will have multiple configs (see below)
    • a modes.yaml file (option) with multiple modes
    • an os.yaml file (option) with OS options
  • Pavilion should look in the suite directory first for any source files

    • If a source path should default to the series' directory if no path or download is specified.
    • The yaml files listed above should be ignored when calculating the build hash.

Host/Mode Files

The host and mode files in a suite directory should have the same format as a test, except the keys should be host/mode/os names.

rocinante:
  variables:
    foo: 'bar'

crossroads:
  variables:
    foo: 'baz'
@Paul-Ferrell Paul-Ferrell added this to the March 2024 milestone Feb 29, 2024
@hwikle-lanl hwikle-lanl linked a pull request Aug 14, 2024 that will close this issue
7 tasks
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 a pull request may close this issue.

2 participants