When searching for RequiresDialect, CustomRunner uses a nested-loop and upon a match, it breaks from the innermost loop only.
So if I declare a test like this:
The CustomRunner will do this:
When using multiple RequiresDialect(s) provided via a @RequiresDialects, the current logic acts like an AND operand, not as an OR. Unfortunately, a test can only use a single Dialect at runtime, so the AND logic does not make sense.
On the other hand, this works: