-
Notifications
You must be signed in to change notification settings - Fork 114
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
Using --benchmark-only
hits assertion in pytest
#243
Comments
jvesely
added a commit
to jvesely/PsyNeuLink
that referenced
this issue
Jun 30, 2023
Use "--benchmark-only" together "-m benchmark". The former will fail if benchmarking is not available. The latter works around a bug in pytest test collection: ionelmc/pytest-benchmark#243 Fixes: d6f8e35 ("tests: Use worksteal xdist balancer (PrincetonUniversity#2670)") Signed-off-by: Jan Vesely <[email protected]>
This was referenced Jun 30, 2023
jvesely
added a commit
to PrincetonUniversity/PsyNeuLink
that referenced
this issue
Jun 30, 2023
Use "--benchmark-only" in addition to "-m benchmark". The former will fail if benchmarking is not available/possible. The latter works around a bug in pytest test collection: ionelmc/pytest-benchmark#243 Fixes: d6f8e35 ("tests: Use worksteal xdist balancer (#2670)") Signed-off-by: Jan Vesely <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
$ pytest --dist=no -n0 --benchmark-only --benchmark-enable
:The issue appears to be with test skipping code. Adding
-m benchmark
to the commandline works around the issue,pytest --dist=no -n0 --benchmark-only --benchmark-enable -m benchmark
works as expected.
The text was updated successfully, but these errors were encountered: