Compilation when --with-attributes returns empty test_list

[robindust-ce]

VUnit will compile a testbench that does not set the ".example" attribute for any testcase, when called like this:
python run.py --with-attributes=.example

Only after compilation "No tests were run." is reported. Is this a deliberate design decision?
I think it would make sense to skip compilation if the test_list is empty.

My use case, where this would be a great benefit:
The codebase has many run.py's. In the CI/CD pipeline for an FPGA Image A I want to run all testbenches that are tagged to be related to the FPGA Image. The Makefile finds all run.py's and runs them using --with-attributes. However, the time overhead for compiling all testbenches if only a few are actually executed is quite large.

[tasgomes]

Did you try with the "-m" (for minimal) flag? That should only compile the minimal list of files necessary to run the tests you enabled via wildcard (and I guess via attribute should also work but I never try).

[LarsAsplund]

This is an omission. Currently, at compile time, we don't make a distinction between "there are no testbenches to simulate because of attributes" and "no testbenches have been specified when calling the run script". The latter is the interpretation which means that we prepare for a full simulation and compile everything that has changed. A CI starting from scratch would compile everything. This can be updated.