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

[Python][CI] Remove upper pin on pytest #39958

Closed
2 of 3 tasks
AlenkaF opened this issue Feb 6, 2024 · 1 comment · Fixed by #40487
Closed
2 of 3 tasks

[Python][CI] Remove upper pin on pytest #39958

AlenkaF opened this issue Feb 6, 2024 · 1 comment · Fixed by #40487
Assignees
Milestone

Comments

@AlenkaF
Copy link
Member

AlenkaF commented Feb 6, 2024

Describe the bug, including details regarding any error messages, version, and platform.

The latest version of pytest (8.0.0) can't be used on our CI as it breaks couple of things. This issue is an umbrella issue for all needed fixes that would enable the removal of the upper pin on pytest:

Component(s)

Python

@jorisvandenbossche jorisvandenbossche added this to the 16.0.0 milestone Feb 7, 2024
jorisvandenbossche added a commit that referenced this issue Mar 19, 2024
### Rationale for this change

The latest version of pytest (`8.0.0`) is breaking our CI:
- S3 fixture from out test suite fails
- `doctest-cython` check fails

### What changes are included in this PR?

- added `allow_bucket_creation=True` to the `s3_example_fs` fixture
- removed the pin on pytest, except for the doc builds

### Are these changes tested?

Yes.

### Are there any user-facing changes?
No

Closes:

- Closes #39958
- Closes #39957

* GitHub Issue: #39958

Lead-authored-by: AlenkaF <[email protected]>
Co-authored-by: Joris Van den Bossche <[email protected]>
Signed-off-by: Joris Van den Bossche <[email protected]>
@jorisvandenbossche
Copy link
Member

Issue resolved by pull request 40487
#40487

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

Successfully merging a pull request may close this issue.

2 participants