Skip to content
Snippets Groups Projects
Commit 440d8467 authored by Stephen Warren's avatar Stephen Warren Committed by Tom Rini
Browse files

travis-ci: use buildman -P everywhere


This places build results into a board-specific directory rather than a
buildman-thread-specific directory. This is required so that we can
access the directory from test.py, and there's no risk of a particular
build's results being over-written by another build performed by the
same thread.

In theory, this can lead to slower builds when building many different
boards in a single buildman thread, since it removes the possibility of
incremental builds between boards. In practice however I didn't notice
longer build times when when enabling this option; if anything build
times decreased although I suspect that's simply due to general
variations in build performance across different machines within the
Travis CI infra-structure.

Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Reviewed-by: default avatarHeiko Schocher <hs@denx.de>
parent 2ded4bf9
No related branches found
No related tags found
No related merge requests found
...@@ -72,7 +72,7 @@ script: ...@@ -72,7 +72,7 @@ script:
# Exit code 129 means warnings only. # Exit code 129 means warnings only.
- if [[ "${BUILDMAN}" != "" ]]; then - if [[ "${BUILDMAN}" != "" ]]; then
set +e; set +e;
tools/buildman/buildman ${BUILDMAN}; tools/buildman/buildman -P ${BUILDMAN};
ret=$?; ret=$?;
if [[ $ret -eq 0 || $ret -eq 129 ]]; then if [[ $ret -eq 0 || $ret -eq 129 ]]; then
exit 0; exit 0;
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment