You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of nightly-2019-10-21, cargo seems to be unable to find the Cargo.toml file in the current working directory of a docker-based gitlab CI job:
$ pwd
/builds/jhf/functionary
$ head -1 /builds/jhf/functionary/Cargo.toml
###
$ CARGO_LOG="trace" cargo build
[2019-10-22T20:16:20Z DEBUG cargo] exit_with_error; err=CliError { error: Some(ErrorMessage { msg: "could not find `Cargo.toml` in `/builds/jhf/functionary` or any parent directory" }), unknown: false, exit_code: 101 }
error: could not find `Cargo.toml` in `/builds/jhf/functionary` or any parent directory
Can you run this with strace to find out whether this is due to statx?
I ran with strace but I'm not sure what I'm looking for -- I don't see any statx calls in the trace, but I do see a bunch of ENOENT (and other failures). It's hard to tell which are happening "normally" as part of checking for things. I'll work on sanitizing a trace to post.
As of
nightly-2019-10-21
, cargo seems to be unable to find theCargo.toml
file in the current working directory of a docker-based gitlab CI job:(maybe related to #65662 ?)
The text was updated successfully, but these errors were encountered: