Merge pipelines

[ekouts]

Merge the UENV and CPE pipelines.

Additional changes in the PR:

• In order to avoid running simple generic tests in almost every applications uenv (because some tests just need an +mpi feature), we introduce a new feature prgenv to differentiate between uenvs that we want to test for simple compilations.
• We use this branch of reframe, until [feat] Log all tests in perfloggers, not only performance tests reframe-hpc/reframe#3516 is merged.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[gppezzi]

For completeness, could you please clarify/document how should we define the checks and the reframe command line in order to use this PR?
In most of them you add +prgenv, but in uenv_status.py you add builtin.

[ekouts]

I added the +prgenv for tests that need some prog env to build something. The thing is that it no uenv contains this at the moment, so if we go with that we should probably add it in the prgenv-gnu envs at least.

But the uenv_status doesn't need to load on any environment, right? And I am not sure we are gaining anything by running on every env.

[ekouts]

I also added a script that will collect all the uenvs with Reframe metadata, just copying the commands we have in the uenv pipelines. @jgphpc maybe you can also have a look to see if there is a better way to do this?

[gppezzi]

I added the +prgenv for tests that need some prog env to build something. The thing is that it no uenv contains this at the moment, so if we go with that we should probably add it in the prgenv-gnu envs at least.

But the uenv_status doesn't need to load on any environment, right? And I am not sure we are gaining anything by running on every env.

For sure executing uenv status once per reframe run is enough.

It is still not entirely clear to me how the tests and the reframe environment calls should look like for the different cases, I'll try to elaborate here to see if I understand the workflow correctly:

• Reframe environment preparation
  • UENV variable is populated using list of uenvs retrieved with the script prepare_uenvs.sh
• Test definition
  • Check should run once for every uenv available
    • Add feature +prgenv to valid_prog_environs
  • Check requires specific uenv to run
    • Add specific +prgenv_XYZ to valid_prog_environs
  • Check should be executed only once (uenv status)
    • Doesn't require any feature or reference to uenv