-
Notifications
You must be signed in to change notification settings - Fork 291
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
Simplify Travis CI builds. #942
Conversation
9634b42
to
d703c92
Compare
c01894f
to
4349346
Compare
d29286a
to
8bfd522
Compare
e0454d9
to
f558b6a
Compare
Reviewed 35 of 36 files at r1, 2 of 2 files at r2, 1 of 1 files at r3. .travis/cmake-linux, line 15 at r2 (raw file):
Stray whitespace Comments from Reviewable |
@@ -79,7 +83,7 @@ build() | |||
if [ "${ALLOW_TEST_FAILURE}" = "true" ]; then | |||
set +e | |||
fi | |||
cmake --build . --target test | |||
cmake --build . --target test -- ARGS="-j50" |
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.
50?
Review status: complete! 1 of 1 LGTMs obtained .travis/cmake-linux, line 15 at r2 (raw file): Previously, robinlinden (Robin Lindén) wrote…
Done. other/docker/windows/build_toxcore.sh, line 86 at r4 (raw file): Previously, nurupo wrote…
Yes, 50 is greater than the number of tests we have at the moment, and up to 50 is probably easily ok. These tests sleep almost all the time, so running them all in parallel doesn't cost much cpu but saves a whole lot of time. Comments from Reviewable |
Have one script per build. This means more duplication between the scripts, but it's much easier to understand and to run locally.
Have one script per build. This means more duplication between the
scripts, but it's much easier to understand and to run locally.
I mostly didn't touch the freebsd stuff. I may move that at some point in the future. It's using
source
as done byphase
too cleverly, so I couldn't easily break it out of the current place.This change is