From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Wed, 26 Oct 2016 11:05:34 -0600 Subject: [U-Boot] [PATCH 4/6] travis-ci: use buildman -P everywhere In-Reply-To: <20161026170536.2367-1-swarren@wwwdotorg.org> References: <20161026170536.2367-1-swarren@wwwdotorg.org> Message-ID: <20161026170536.2367-4-swarren@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de From: Stephen Warren 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: Stephen Warren --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 119dec8df5b2..6e72e0bb233f 100644 --- a/.travis.yml +++ b/.travis.yml @@ -72,7 +72,7 @@ script: # Exit code 129 means warnings only. - if [[ "${BUILDMAN}" != "" ]]; then set +e; - tools/buildman/buildman ${BUILDMAN}; + tools/buildman/buildman -P ${BUILDMAN}; ret=$?; if [[ $ret -eq 0 || $ret -eq 129 ]]; then exit 0; -- 2.10.1