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
Fail to find the binary if CARGO_TARGET_DIR is set #117
Comments
Thanks for reporting this! A workaround would be to use I might not have time for a couple of days to dig into this if you weren't planning to. Is this blocking you or is that workaround insufficient until then? And apparently, there are some broken links in the docs, so I created #118 |
This is not blocking me at all for now, no worries. I disabled my tests for now but I will be happy to enable them again :) |
I wonder if there is a platform or rustc specific aspect to this. I just ran assert_cmd $ TMPDIR=/Users/edpage/src/tmp/ CARGO_TARGET_DIR=/Users/edpage/src/tmp/ cargo test (the TMPDIR is to workaround an IT thing)
|
Either way, I expect #120 to help |
It may help in some cases but I tested again today and that does not seem to fix the issue. |
I think I missed the update on which crate. It looks like you are using This is documented in the limitations Going ahead and closing assuming this is the root cause. Feel free to ask for this to be re-opened if something still needs addressing. |
To reproduce:
export CARGO_TARGET_DIR=/tmp/test/
cargo test
The CLI binary, usually found when
CARGO_TARGET_DIR
is not set, will not be found:This is especially an issue when
CARGO_TARGET_DIR
is set to benefit from caching.NOTE: I am working currently on https://gitlab.com/chevdor/subwasm if you want more context
The text was updated successfully, but these errors were encountered: