Display traceback with --strict-markers error #6232
Closed
Conversation
This file contains hidden or 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
blueyed
force-pushed
the
strict-markers-pytrace
branch
from
41108ff to
0440750
Compare
blueyed
added a commit
to blueyed/pytest
that referenced
this pull request
Nov 26, 2019
Alternative / related to pytest-dev#6232. This is in line with pytest-dev#6247.
blueyed
added a commit
to blueyed/pytest
that referenced
this pull request
Nov 26, 2019
Alternative / related to pytest-dev#6232. This is in line with pytest-dev#6247.
Contributor
Author
|
Alternative / related: ignore |
blueyed
added a commit
to blueyed/pytest
that referenced
this pull request
Nov 26, 2019
Via pytest-dev#6232. (cherry picked from commit 0440750)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
TODO: