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

Error in pytest possibly relating to pytest-benchmark in version 5.0.0 #271

Closed
dpanici opened this issue Oct 29, 2024 · 2 comments
Closed

Comments

@dpanici
Copy link

dpanici commented Oct 29, 2024

Hello,

Unsure if this is the main source of. the error or if it is an upstream bug with a package that depends on pytest-benchmark, but we use pytest-benchmark in our CI, in addition to other plugins to run jupyter notebooks as part of the CI.

Upon the update from 4.0.0 to 5.0.0 we've found our CI failing, with the exact cause unclear, but it seems to relate to pytest-benchmark from the error logs.
The CI runner is on Linux, the details of the specifics and the environment are in the aforementioned linked error logs.

With 4.0.0 our tests pass. Again, unsure if this is a specific issue with pytest-benchmark or related to another package we use which depends on pytest-benchmark that broke when 5.0.0 was released, but if you have any insight into the error we are getting that would be greatly appreciated!

If it helps, our CI yml that is failing is https://github.com/PlasmaControl/DESC/blob/master/.github/workflows/notebook_tests.yml and line 79 of said file has the specific pytest command that results in the error.

@ionelmc
Copy link
Owner

ionelmc commented Oct 29, 2024

Yeah I added a type check so that the "benchmark" fixture is not defined to something else. The goal was to give a clear error message for situations like #265.

In your project apparently that is not a problem (I guess you do define a "benchmark" fixture but it's scoping prevents the bad interaction in #265). I'll convert that to a warning....

@ionelmc
Copy link
Owner

ionelmc commented Oct 30, 2024

So it's still an error but I fixed the check. Released a 5.0.1.

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

2 participants