Conversation
|
|
||
| $ pytest --version | ||
| pytest 9.0.0 | ||
| pytest 9.0.1 |
| ? - - | ||
| + '4': 4, | ||
| } | ||
| FAILED test_verbosity_example.py::test_long_text_fail - AssertionError: assert 'hello world' in 'Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ips... sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet ' |
There was a problem hiding this comment.
Seems like these changes should have gone into the 9.0.0 release... 🤔
|
pre-commit is failing with: I cannot reproduce this locally. Strange, I noticed it is building with an image released just today, might be related: Perhaps @asottile can chime in? EDIT: I see this in the pre-commit changelog: - Add `language: unsupported` / `language: unsupported_script` as aliases
for `language: system` / `language: script` (which will eventually be
deprecated).
- #3577 PR by @asottile. |
…nsupported` As per the pre-commit changelog: https://github.com/pre-commit/pre-commit/blob/main/CHANGELOG.md#440---2025-11-08
|
huh that's a weird one. I guess I used the stricter parser in pre-commit ci by mistake you'll probably want to use |
In pytest-dev#13939 we are using the new `language: unsupported` setting, which was introduced in pre-commit 4.4.0. Configure minimum pre-commit version to ensure the installed pre-commit supports it (pytest-dev#13938 (comment)).
Thanks, done: #13941 |
|
ok I've fixed pre-commit ci to not early approach the deprecation 😆 small oversight pre-commit-ci/runner-image#316 |
|
Waiting on a second approval before proceeding with the release. 👍 |
| E assert [0, 0, 0, 0, 0, 0, ...] == [0, 0, 0, 0, 0, 0, ...] | ||
| E | ||
| E At index 100 diff: 1 != 2 | ||
| E Use -v to get more diff |
There was a problem hiding this comment.
This seems bad, any idea why it no longer truncates?
There was a problem hiding this comment.
Note: better to see this comment in the diff itself to understand...
There was a problem hiding this comment.
Seems related to the changes in how we handle the CI environment variable... will investigate.
pytest auto-detects and uses more verbose output when running in CI. Change tox:regendoc to remove those environment variables, because we do not want extra verbose output in the user documentation. See pytest-dev#13938 (comment).
pytest auto-detects and uses more verbose output when running in CI. Change tox:regendoc to remove those environment variables, because we do not want extra verbose output in the user documentation. See #13938 (comment).
pytest auto-detects and uses more verbose output when running in CI. Change tox:regendoc to remove those environment variables, because we do not want extra verbose output in the user documentation. See #13938 (comment). (cherry picked from commit 82e9b97) Co-authored-by: Bruno Oliveira <bruno@pytest.org>
|
Attempting this again after #13950. |
4 participants
Created by the prepare release pr workflow.
Once all builds pass and it has been approved by one or more maintainers, start the deploy workflow, using these parameters:
Use workflow from:release-9.0.1.Release version:9.0.1.Or execute on the command line:
gh workflow run deploy.yml -r release-9.0.1 -f version=9.0.1After the workflow has been approved by a core maintainer, the package will be uploaded to PyPI automatically.