Bassam (Sam) Khouri

> Could you try wiping the caches and trying again? > > ``` > bazel clean --expunge > rm -r /Volumes/BazelRepoCache/ > ``` All Volumes uses for bazel are local...

For what it's work, using `version = "jruby-9.4.7.0"` in `MODULE.bazel` gets past the error. So I'm unsure why the works, but `version = "3.3.1"` fails.

I agree this would be beneficial. One option could be to emit a `deprecated` to the console when the deprecated option is used.

The implemented solution should consider readability of the conditions, in addition for "swift formatting". For example, how do we want to treat a "more complex" condition, say, ``` @Test( .any(...

Looking at that the below example (which is an actual usage [here](https://github.com/swiftlang/swift-package-manager/blob/main/IntegrationTests/Tests/IntegrationTests/BasicTests.swift#L25-L31 )), I always have to look at the Swift Testing source code, or documentation, do determine if they...

My original request, which may not have been clear, is to make usage of custom traits more explicit. That I, I want do define custom ConditionalTrais, and make their uses...

> [@bkhouri](https://github.com/bkhouri) That's already supported and functional though. But it's not explicit. I would like to have an equivalent of, where it's explicit, and where I can select `.all`, or...

Personally, I just want the readability to be explicit on the application of the conditional traits. Using the `&&` and `||` overload in this example ``` @Test( .skipSwiftCISelfHosted( "These packages...

@swift-ci test

@swift-ci test macOS