For a nvcc version, which was not released at the moment, when the filter rules was implemented, we decide that each combination of a GCC and Clang version is valid. The result is, that if a new combination is tested, which is not supported, the CI will throw an error and we need to forbid this combination.
The other option wold be to forbid every combination for up coming releases, which are not allowed for the latest know versions. The problem of the solution is, that it forbid silently valid combinations.
The PR fixes the implementation, that it follows the first approach.
For a nvcc version, which was not released at the moment, when the filter rules was implemented, we decide that each combination of a GCC and Clang version is valid. The result is, that if a new combination is tested, which is not supported, the CI will throw an error and we need to forbid this combination.
The other option wold be to forbid every combination for up coming releases, which are not allowed for the latest know versions. The problem of the solution is, that it forbid silently valid combinations.
The PR fixes the implementation, that it follows the first approach.