Ignore unavoidable warning about private pytest classes #52
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
for more information, see https://pre-commit.ci
…ubtests into fix-private-warning
|
Agreed, thanks @kalekundert! |
nicoddemus
added a commit
to nicoddemus/pytest-subtests
that referenced
this pull request
Jan 15, 2022
kraj
pushed a commit
to YoeDistro/meta-openembedded
that referenced
this pull request
Jan 17, 2022
0.6.0 (2022-01-15) * pytest>=6.0 is now required. * Added official support for Python 3.10. * Dropped support for Python 3.5. * Users no longer need to configure a warnings filter for the internal A private pytest class or function was used pytest warning (openembedded#52). * Experimental: Use SUBPASS and , for passed subtests instead of general PASSED, SUBFAIL and u for failed ones instead of FAILED (openembedded#30). References: pytest-dev/pytest-subtests#52 pytest-dev/pytest-subtests#30 Signed-off-by: Tim Orling <[email protected]> Signed-off-by: Khem Raj <[email protected]>
halstead
pushed a commit
to openembedded/meta-openembedded
that referenced
this pull request
Jan 18, 2022
0.6.0 (2022-01-15) * pytest>=6.0 is now required. * Added official support for Python 3.10. * Dropped support for Python 3.5. * Users no longer need to configure a warnings filter for the internal A private pytest class or function was used pytest warning (#52). * Experimental: Use SUBPASS and , for passed subtests instead of general PASSED, SUBFAIL and u for failed ones instead of FAILED (#30). References: pytest-dev/pytest-subtests#52 pytest-dev/pytest-subtests#30 Signed-off-by: Tim Orling <[email protected]> Signed-off-by: Khem Raj <[email protected]> Signed-off-by: Trevor Gamblin <[email protected]>
sgunin
pushed a commit
to sgunin/oe-meta-openembedded-contrib
that referenced
this pull request
Mar 17, 2024
0.6.0 (2022-01-15) * pytest>=6.0 is now required. * Added official support for Python 3.10. * Dropped support for Python 3.5. * Users no longer need to configure a warnings filter for the internal A private pytest class or function was used pytest warning (#52). * Experimental: Use SUBPASS and , for passed subtests instead of general PASSED, SUBFAIL and u for failed ones instead of FAILED (#30). References: pytest-dev/pytest-subtests#52 pytest-dev/pytest-subtests#30 Signed-off-by: Tim Orling <[email protected]>
sgunin
pushed a commit
to sgunin/oe-meta-openembedded-contrib
that referenced
this pull request
Mar 17, 2024
0.6.0 (2022-01-15) * pytest>=6.0 is now required. * Added official support for Python 3.10. * Dropped support for Python 3.5. * Users no longer need to configure a warnings filter for the internal A private pytest class or function was used pytest warning (#52). * Experimental: Use SUBPASS and , for passed subtests instead of general PASSED, SUBFAIL and u for failed ones instead of FAILED (#30). References: pytest-dev/pytest-subtests#52 pytest-dev/pytest-subtests#30 Signed-off-by: Tim Orling <[email protected]>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this pull request
May 22, 2024
0.6.0 (2022-01-15) * pytest>=6.0 is now required. * Added official support for Python 3.10. * Dropped support for Python 3.5. * Users no longer need to configure a warnings filter for the internal A private pytest class or function was used pytest warning (#52). * Experimental: Use SUBPASS and , for passed subtests instead of general PASSED, SUBFAIL and u for failed ones instead of FAILED (#30). References: pytest-dev/pytest-subtests#52 pytest-dev/pytest-subtests#30 Signed-off-by: Tim Orling <[email protected]> Signed-off-by: Khem Raj <[email protected]> Signed-off-by: Trevor Gamblin <[email protected]>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this pull request
May 22, 2024
0.6.0 (2022-01-15) * pytest>=6.0 is now required. * Added official support for Python 3.10. * Dropped support for Python 3.5. * Users no longer need to configure a warnings filter for the internal A private pytest class or function was used pytest warning (#52). * Experimental: Use SUBPASS and , for passed subtests instead of general PASSED, SUBFAIL and u for failed ones instead of FAILED (#30). References: pytest-dev/pytest-subtests#52 pytest-dev/pytest-subtests#30 Signed-off-by: Tim Orling <[email protected]> Signed-off-by: Khem Raj <[email protected]> Signed-off-by: Trevor Gamblin <[email protected]>
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.
The README for this repository currently recommends configuring the
pytest.filterwarningssetting to ignore a warning generated by this plugin. This doesn't seem like something end-users should have to deal with, so this PR adds some code to ignore the warning on the exact lines that can trigger it.