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.

Sign up for GitHub

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

Jump to bottom

BUG: --environment-type doesn't do anything with pytest #1446

Open
HaoZeke opened this issue Nov 25, 2024 · 0 comments · May be fixed by #1450
Open

BUG: --environment-type doesn't do anything with pytest #1446

HaoZeke opened this issue Nov 25, 2024 · 0 comments · May be fixed by #1450

Comments

@HaoZeke
Copy link
Member

HaoZeke commented Nov 25, 2024

Essentially when passed with pytest the tests are run with virtualenv always, no matter what is actually requested. Essentially:

  • Requesting virtualenv -- works fine
  • conda -- doesn't work, falls back to virtualenv
  • mamba -- errors out (since it doesn't fallback if requested)
HaoZeke added a commit to HaoZeke/asv that referenced this issue Nov 25, 2024
@HaoZeke
TST: Use alternate environments correctly
edf5b1f 
Closes airspeed-velocitygh-1446
@HaoZeke HaoZeke mentioned this issue Nov 25, 2024
Open
HaoZeke added a commit to HaoZeke/asv that referenced this issue Nov 25, 2024
@HaoZeke
BUG: Fix alternate environment logic in tests
57d9c36 
In a pretty hacky way, also part of airspeed-velocitygh-1446
@HaoZeke HaoZeke linked a pull request Dec 13, 2024 that will close this issue
Draft
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

TST: Fix testsuite rattler HaoZeke/asv
1 participant
@HaoZeke