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
unconditionally generate lockfile #53
Comments
There doesn't seem to be a way to replicate |
|
Looks like this was fixed in 0.1.5. |
I'm still seeing this issue, using the latest version. Here's a log https://travis-ci.org/mgattozzi/alchemist/jobs/204565275#L524 |
You should let cross do it with |
The error still shows up with that not there, I added it to test if it would help, I'll remove it and try again though... |
I think #67 is the cause, This issue should be reopened. |
OK. I think I found the problem. This is a workspace so Using |
Its looking for sqlite3 since that (for the moment) is the database we are using for alchemist. |
`cross` runs tests on a read-only version of the project, so it makes sure to generate the Cargo.lock file on the host before it does that. However, the --manifest-path flag confuses it, and it puts the lockfile in the wrong place, and the subsequent container build crashes with a permissions error. Similar issue: cross-rs/cross#53
Right now, something like this produces an error:
The text was updated successfully, but these errors were encountered: