Test feature flags #2004
Closed
Test feature flags #2004
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tustvold
force-pushed
the
test-feature-flags
branch
from
d6c294f
to
a55f282
Compare
tustvold
force-pushed
the
test-feature-flags
branch
from
a55f282
to
ea8840b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft as builds on #2003 and I want to see how long this takes
Which issue does this PR close?
Closes #
Rationale for this change
We are still seeing invalid feature flag combinations, lets brute force them all 馃帀
What changes are included in this PR?
Uses cargo hack to test every feature flag combination
Are there any user-facing changes?
No, this just impacts CI