Skip to content
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

test_annotation_pytest_error fails on main branch #78

Open
amezin opened this issue Jul 27, 2023 · 1 comment
Open

test_annotation_pytest_error fails on main branch #78

amezin opened this issue Jul 27, 2023 · 1 comment

Comments

@amezin
Copy link

amezin commented Jul 27, 2023

  Failed:  nomatch: '::error file=test_annotation_pytest_error\\.py,line=8::test_error.*'
       and: ''
       and: '::error file=test_annotation_pytest_error.py,line=1168::test_error%0A%0AFailed: Fixture "fixture" called directly. Fixtures are not meant to be called directly,%0Abut are created automatically when test functions request them as parameters.%0ASee https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and%0Ahttps://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.'
  remains unmatched: '::error file=test_annotation_pytest_error\\.py,line=8::test_error.*'

https://github.com/amezin/pytest-github-actions-annotate-failures/actions/runs/5683449264/job/15404043739

@amezin
Copy link
Author

amezin commented Jul 28, 2023

Not surprising, given that the code takes the file name from one source, and the line number from another source (and possibly a different file). Not sure how it's supposed to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant