splitting test groups

[Fabian188]

Sorry, me again.

I might not properly understand how ctest/cdash shall be used.

In the overview all stages are grouped by group. I'd like to have a special group for tests and changed
the call in the .gitlab-ci.yml like this

ctest -D ExperimentalStart --group $CDASH_TRACK -V ...
ctest -D ExperimentalUpdate --group $CDASH_TACK  -V ...
...
ctest -D ExperimentalTest --group {$CDASH_TRACK}Tests ...

I did more experiments. I seems that always the --group from ctest -D ExperimentalStart is used and other --group in the sequence are ignored.

Am I right, could I do it different or do I simply misunderstand how it should be done/used?

Thanks.

[williamjallen]

Hi @Fabian188, all components of a single "build" (update, configure, build, test, etc) should be submitted to the same build group and will show up as a single row on the dashboard. Build groups are for...well...grouping entire builds. For example, CMake has "Nightly Expected", "merge-requests", and "continuous" build groups, amongst other things.

What are you trying to accomplish with CDash? Understanding what you're trying to do would help me suggest a better CDash configuration for you.

[Fabian188]

Thanks. Then it is as it is and it is ok.

We have cdash for a single software where multiple branches might commit and we have for each pipeline several tests, including some which are allowed to fail.

From time to time I want to check how many tests are passing and failing on the cdash server. For the other states I rather check the output in the pipelines on gitlab itself. So I thought about sub-grouping.

We have only two groups with one is Nightly

[williamjallen]

Many projects create a build group for each branch they regularly run CI on. ParaView does something similar if you're looking for inspiration.