-
Notifications
You must be signed in to change notification settings - Fork 30
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
Speed up list_available #133
Speed up list_available #133
Conversation
The test seem to be playing up, no sure if this is related to PR, because running the test suite on the master isn't working - see for example https://github.com/ericpre/gator/actions/runs/722378324. |
Cool, thanks for working on this! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ericpre for this PR. I left a few improvements.
Could you also add a test for it?
For that the best would be to check the call of f
in
You could test the call with something like:
f.assert_called_with(...)
after line 975. Note the call arguments will depend on the manager.
3b9c184
to
0d8f43e
Compare
Sorry, I am not sure that I understand, what should be tested exactly? Do you want to have the ouptut of |
As you said, the output is already tested. I would like only to add a test to be sure the proper command is invoked depending on the manager; i.e. if conda, Does it clarify the intention? |
Yes, it makes sense, thanks! |
… mamba is available to speed up the list_available method.
0d8f43e
to
31b9c55
Compare
Thanks @ericpre I added the tests. |
Thanks for sorting out the test and finishing the PR! |
As discussed in #132 and mamba-org/mamba#835, use
mamba repoquery search "*" --json
in favour ofmamba search --json
(orconda search --json
), since the later is significantly slower thanmamba repoquery
.