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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Criterion integrationv2 python changes #3534
Criterion integrationv2 python changes #3534
Changes from 15 commits
1721db0
b0d7db7
6564eb5
cb2cedd
816daa0
a737dec
8fd86df
bd2e5cb
1fbeb4b
5b10f6c
d439ae4
563756d
283da43
dac25b7
ef4fe22
5ea4fd5
4971c1d
3d9bfb5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning
Code scanning / CodeQL
Overwriting attribute in super-class or sub-class
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little paranoid that if we get the disabling / default value of this flag wrong, we would always skip netflix. Like if you change "off" to "disable" but forget to update this line. Hardcoded strings are dangerous, particularly if you're only checking "!=".
Can you put CriterionS2N's criterion_off somewhere accessible to this logic, as well as everywhere else you have "off" hardcoded? So they're all guaranteed to use the same value? Or maybe add a "is_criterion_enabled" type method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a
choices
option to the pytest arguments to cause pytest to fail if the criterion flag is unexpected and moved the "is it off" logic into a function in global_flags.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add log_cli?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it was helpful for early development, with only one xdist worker and cli-level increased