Feature request: platform-specific override for default-filter configuration #1869
Closed
nagisa
started this conversation in
Feature requests
Replies: 3 comments
-
Yes -- this was definitely something I was intending to do as a followup! |
Beta Was this translation helpful? Give feedback.
0 replies
-
We're going to likely need it at work soon, so implemented this: #1871 |
Beta Was this translation helpful? Give feedback.
0 replies
-
All right, this is part of cargo-nextest 0.9.84: https://nexte.st/docs/running/#per-platform-default-filters. Would love to hear your thoughts! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Motivation
I want to ignore a family of tests that I know does not run on a certain platform by default.
I tried
and have found that this is not taken into account.
Proposal
I propose that platform-specific overrides for
default-filter
should be applied.Alternatives
filterset could be extended to allow applying rules based on the platform? That would make it conditional, but...
I have also considered
#[cfg_attr(..., ignore)]
but in my case the tests affected are easier to filter out on a granularity of an entire crate/package, rather than individual tests.Since I use a
Justfile
, I also have attempted to figure something out with the-E
flags, but I have found that then it makes it difficult for users to specify their own filtersets via this flag as multiple-E
flags areunion
ed rather than subset as is the behaviour with thedefault-filter
set.Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions