Separate tests require separate names. Requiring the suffix to be in the tests is not a bug or a limitation, but rather a requirement. This does require an `output_file:` at the testset level. Scott On 2021-08-20 12:57, Pierre Jolivet did write:

That’s a long-standing issue that I personally bypass by setting the suffix in the test instead of at the testset scope. But maybe that’s not working for you either?

Thanks, Pierre

...

On 20 Aug 2021, at 12:43 PM, Stefano Zampini <[email protected]> wrote:

Scott

This test is specified as

testset: suffix: expl nsize: {{1 2}} filter: grep -v "MPI processes" | grep -v " type:" | grep -v "Mat Object" args: -ksp_converged_reason -view_explicit_mat -pc_type none -ksp_type {{cg gmres}} test: args: -mat_type aij test: requires: hypre args: -mat_type hypre

It triggers an error here https://gitlab.com/petsc/petsc/-/jobs/1519558357 <https://gitlab.com/petsc/petsc/-/jobs/1519558357>, with a CI configuration without hypre. Other testset instances works fine if any “require:" is both specified in the testset body and in the specific test. Is this supposed to work?

Thanks Stefano

-- Scott Kruger Tech-X Corporation [email protected] 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303 Fax: (303) 448-7756