Skip to content
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

Nightly fails to build unless git is installed #59565

Closed
jbeich opened this issue Mar 30, 2019 · 5 comments
Closed

Nightly fails to build unless git is installed #59565

jbeich opened this issue Mar 30, 2019 · 5 comments
Labels
C-bug Category: This is a bug. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Comments

@jbeich
Copy link

jbeich commented Mar 30, 2019

Regressed by #59303. Source archives don't have .git subdirectory, so missing git executable shouldn't be fatal.

thread 'main' panicked at 'Command::new("git").args(&["rev-parse", "--verify",
                           &format!("@:./{}" ,
                                    submodule)]).current_dir(&builder.src).output() failed with No such file or directory (os error 2)', src/bootstrap/native.rs:82:26

http://beefy9.nyi.freebsd.org/data/112amd64-default/497233/logs/errors/rust-nightly-1.35.0.20190330_1.log

@jonas-schievink jonas-schievink added T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) C-bug Category: This is a bug. labels Mar 30, 2019
@Mark-Simulacrum
Copy link
Member

cc @euclio and @cuviper

It might be worth just always rebuilding in source archives -- it seems reasonable to assume most people aren't editing the code in those. Unsure though; perhaps that's not a correct assumption.

@cuviper
Copy link
Member

cuviper commented Mar 30, 2019

It might be worth just always rebuilding in source archives

Yes, that was the intention, which you can see in the else case after checking git_output.status.success(). But I guess missing git entirely fails sooner, in the Command::output() call.

@cuviper
Copy link
Member

cuviper commented Mar 30, 2019

Perhaps we should be using GitInfo::new for this, which has conditions for ignoring git or missing .git. That would also return the current actual hash in that path, which is probably even better to use than the submodule recorded in rust's HEAD (@:./path) or index (:./path).

@cuviper
Copy link
Member

cuviper commented Mar 30, 2019

Actually, the Build already contains in_tree_llvm_info and emscripten_llvm_info!

@euclio
Copy link
Contributor

euclio commented Mar 30, 2019

Thanks for the quick fix!

bors added a commit that referenced this issue Mar 31, 2019
Use the existing LLVM GitInfo for checking rebuilds

Fixes #59565
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Projects
None yet
Development

No branches or pull requests

5 participants