Uh oh!
There was an error while loading. Please reload this page.
GH-39849: [Python] Remove the use of pytest-lazy-fixture - #39850
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
AlenkaF
commented
Jan 30, 2024
The failures shouldn't be related, but I do not see them on any other build 🤷♀️ |
jorisvandenbossche
commented
Feb 1, 2024
@github-actions crossbow submit python |
Revision: c740098 Submitted crossbow builds: ursacomputing/crossbow @ actions-34647c76a2 |
AlenkaF
commented
Feb 1, 2024
Maybe the failures are connected to the new version of pytest. WIll pin it back to see if that is true. |
jorisvandenbossche
commented
Feb 1, 2024
@github-actions crossbow submit -g python |
Revision: e4146cb Submitted crossbow builds: ursacomputing/crossbow @ actions-07f4a3b8ab |
Uh oh!
There was an error while loading. Please reload this page.
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 44d5597. There were 2 benchmark results with an error:
There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…e#39850) ### Rationale for this change Removing the use of `pytest-lazy-fixture` in our test suite as it is unmaintained. Changes in this PR include: - Remove the use of `pytest-lazy-fixture` - Remove marks from fixtures to avoid future error, see ``` PytestRemovedIn9Warning: Marks applied to fixtures have no effect See docs: https://docs.pytest.org/en/stable/deprecations.html#applying-a-mark-to-a-fixture-function ``` - Catch two different warnings in `def test_legacy_int_type()` ### Are these changes tested? The changes affect the tests so they must pass. ### Are there any user-facing changes? No. * Closes: apache#39849 Lead-authored-by: AlenkaF <frim.alenka@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
### Rationale for this change Removing the use of `pytest-lazy-fixture` in our test suite as it is unmaintained. Changes in this PR include: - Remove the use of `pytest-lazy-fixture` - Remove marks from fixtures to avoid future error, see ``` PytestRemovedIn9Warning: Marks applied to fixtures have no effect See docs: https://docs.pytest.org/en/stable/deprecations.html#applying-a-mark-to-a-fixture-function ``` - Catch two different warnings in `def test_legacy_int_type()` ### Are these changes tested? The changes affect the tests so they must pass. ### Are there any user-facing changes? No. * Closes: #39849 Lead-authored-by: AlenkaF <frim.alenka@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
pytest-lazy-fixture is no longer used apache/arrow#39850
Rationale for this change
Removing the use of
pytest-lazy-fixturein our test suite as it is unmaintained.Changes in this PR include:
pytest-lazy-fixturedef test_legacy_int_type()Are these changes tested?
The changes affect the tests so they must pass.
Are there any user-facing changes?
No.