Skip to content

Running a test suite with additional options (-s / --sets) breaks when tests are BFB-compared with other tests #569

Closed
@phil-blain

Description

I just ran into this issue again and realized I already knew about that but had not opened an issue to document it.

In the context of #560 I ran the decomp_suite in a debug configuration, i.e. I added -s debug to the cice.setup command line.

However, it seems our testing framework is unprepared for that use case if any test in the test suite have an entry under the BFB-compare column in the <test_suite>.ts definition file. For example, for the decomp suite:

# Test Grid PEs Sets BFB-compare
restart gx3 4x2x25x29x4 dslenderX2
decomp gx3 4x2x25x29x5
sleep 30
restart gx3 1x1x50x58x4 droundrobin,thread restart_gx3_4x2x25x29x4_dslenderX2
restart gx3 4x1x25x116x1 dslenderX1,thread restart_gx3_4x2x25x29x4_dslenderX2

The name of the test in the BFB-compare column is written to the ICE_BFBCOMP variable in cice.settings verbatim, i.e. it does not take into account additional options that were added on the command line. So the BFB compare part of the test fails with "missing-data" because they are not looking at the right place, i.e. the test on line 5 will look for restart_gx3_4x2x25x29x4_dslenderX2 but should look for restart_gx3_4x2x25x29x4_debug_dslenderX2.

So cice.setup should ideally add additional options from the command line before writing ICE_BFBCOMP in cice.settings for each test.

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions