Skip to content

ci: add 3.13

ci: add 3.13 #283

Triggered via pull request October 31, 2024 17:12
Status Failure
Total duration 1m 25s
Artifacts

test.yml

on: pull_request
Matrix: test
All tests passed
2s
All tests passed
Fit to window
Zoom out
Zoom in

Annotations

25 errors
ubuntu-latest, Python 3.11: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
ubuntu-latest, Python 3.11
Process completed with exit code 1.
ubuntu-latest, Python 3.8: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
ubuntu-latest, Python 3.8
Process completed with exit code 1.
ubuntu-latest, Python 3.10: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
ubuntu-latest, Python 3.10
Process completed with exit code 1.
ubuntu-latest, Python 3.12: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
ubuntu-latest, Python 3.12
Process completed with exit code 1.
ubuntu-latest, Python 3.9: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
ubuntu-latest, Python 3.9
Process completed with exit code 1.
ubuntu-latest, Python 3.13: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
ubuntu-latest, Python 3.13
Process completed with exit code 1.
windows-latest, Python 3.10: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
windows-latest, Python 3.10
Process completed with exit code 1.
windows-latest, Python 3.9: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
windows-latest, Python 3.9
Process completed with exit code 1.
windows-latest, Python 3.12: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
windows-latest, Python 3.12
Process completed with exit code 1.
windows-latest, Python 3.8: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
windows-latest, Python 3.8
Process completed with exit code 1.
windows-latest, Python 3.11: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
windows-latest, Python 3.11
Process completed with exit code 1.
windows-latest, Python 3.13: test_annotation_pytest_error.py#L1169
test_error Failed: Fixture "fixture" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/stable/explanation/fixtures.html for more information about fixtures, and https://docs.pytest.org/en/stable/deprecations.html#calling-fixtures-directly about how to update your code.
windows-latest, Python 3.13
Process completed with exit code 1.
All tests passed
Process completed with exit code 1.