-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
rust/cargo: add support for a custom target directory #3164
rust/cargo: add support for a custom target directory #3164
Conversation
0dc9675
to
a15f678
Compare
This pull request has been automatically marked as stale because it has not been updated recently. Make sure to write tests and document your changes. See |
Ping @w0rp to un-stale this :) . It's not clear to me how to test this since it is controlling a |
a15f678
to
cdcc0e4
Compare
Thanks. Trying to run tests locally seems to hang with no CPU usage from the processes in the container...seeing what CI says. |
Yeah, I get that on my machine too. I haven't been able to figure out why the tests can do that, but if you just let them run for a while they will eventually exit and give you the results. At some point I'll try to figure out what is going on and fix that. |
The upshot of them taking a while with low CPU usage is that you can go off and do whatever else you want for a while, because your CPUs will be free to do other work. |
b58988a
to
a0bfd58
Compare
This can avoid having to wait for ALE or ALE being blocked on other cargo actions within the same crate.
a0bfd58
to
506a853
Compare
Finally all green :) . |
Cheers! 🍻 |
This can avoid having to wait for ALE or ALE being blocked on other
cargo actions within the same crate.
Where should I add them? I don't see any existing ones testing this kind of feature already.
Seriously, read
:help ale-dev
and write tests.