-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Tweak Travis to use GCE #28500
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
Merged
Merged
Tweak Travis to use GCE #28500
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
FROM ubuntu:latest | ||
|
||
RUN echo 'deb http://llvm.org/apt/trusty/ llvm-toolchain-trusty-3.7 main' | \ | ||
sudo tee -a /etc/apt/sources.list | ||
RUN echo 'deb-src http://llvm.org/apt/trusty/ llvm-toolchain-trusty-3.7 main' | \ | ||
sudo tee -a /etc/apt/sources.list | ||
RUN apt-get update | ||
RUN apt-get -y install curl make g++ python2.7 git zlib1g-dev libedit-dev | ||
RUN apt-get -y --force-yes install llvm-3.7-tools | ||
|
||
RUN mkdir /build | ||
WORKDIR /build | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -625,17 +625,20 @@ mod tests { | |
drop(p.wait()); | ||
} | ||
|
||
#[cfg(unix)] | ||
#[cfg(all(unix, not(target_os="android")))] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @alexcrichton did you mean to remove this? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Gah oops! I did indeed not mean to! |
||
#[test] | ||
fn signal_reported_right() { | ||
use os::unix::process::ExitStatusExt; | ||
|
||
let p = Command::new("/bin/sh").arg("-c").arg("kill -9 $$").spawn(); | ||
assert!(p.is_ok()); | ||
let mut p = p.unwrap(); | ||
let mut p = Command::new("/bin/sh") | ||
.arg("-c").arg("read a") | ||
.stdin(Stdio::piped()) | ||
.spawn().unwrap(); | ||
p.kill().unwrap(); | ||
match p.wait().unwrap().signal() { | ||
Some(9) => {}, | ||
result => panic!("not terminated by signal 9 (instead, {:?})", result), | ||
result => panic!("not terminated by signal 9 (instead, {:?})", | ||
result), | ||
} | ||
} | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule llvm
updated
10 files
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexcrichton IIRC, each
RUN
creates a new file system layer. Combining theRUN
s into one (just using&&
) might speed up yourdocker build
.If this image is cached anywhere (which might make sense), you might also want append some clean up calls to the
RUN
callingapt-get
to reduce the size. I'm no authority on this, but I've often seen stuff likeapt-get autoremove -y && apt-get clean all && rm -rf /var/lib/apt/lists/*
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Right now I don't think that this is anywhere near the limiting factor of our builds, however, so it may not be too bad one way or the other.
If building an image ends up taking too long in the future we'll probably want to just send it up to the hub and download it from there, but hopefully it won't be taking too too long!