Now that we have a long OpenSBI Verilator test that we would like to not run on every PR push, we should start to categorise tests instead of just by name. A feature in CMake/CTest is test labels, which can be filtered to include or exclude on the command line. Some test labels we might want to consider introducing:
verilator & fpga - to replace the usages of -R verilator/fpga which filter for the name of the test with -L verilator/fpga. We should use just labels.
The I2C smoketest requires an I2C device plugged into the FPGA which is only present in CI, so it would be useful to have a special label for those tests so they can be filtered out for local development/anyone that doesn't have specific hardware besides the board.
Now that we have a long OpenSBI Verilator test that we would like to not run on every PR push, we should start to categorise tests instead of just by name. A feature in CMake/CTest is test labels, which can be filtered to include or exclude on the command line. Some test labels we might want to consider introducing:
verilator&fpga- to replace the usages of-R verilator/fpgawhich filter for the name of the test with-L verilator/fpga. We should use just labels.The I2C smoketest requires an I2C device plugged into the FPGA which is only present in CI, so it would be useful to have a special label for those tests so they can be filtered out for local development/anyone that doesn't have specific hardware besides the board.