From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, "Thomas Huth" <thuth@redhat.com>,
berrange@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>,
f4bug@amsat.org, stefanha@redhat.com, pbonzini@redhat.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
aurelien@aurel32.net
Subject: [PATCH v1 5/6] travis.yml: Limit simultaneous jobs to 3
Date: Wed, 17 Feb 2021 12:19:31 +0000 [thread overview]
Message-ID: <20210217121932.19986-6-alex.bennee@linaro.org> (raw)
In-Reply-To: <20210217121932.19986-1-alex.bennee@linaro.org>
From: Thomas Huth <thuth@redhat.com>
Even though the host machines that run the Travis CI jobs have
quite a lot of CPUs (e.g. nproc in an aarch64 job reports 32), the
containers on Travis are still limited to 2 vCPUs according to:
https://docs.travis-ci.com/user/reference/overview/#approx-boot-time
So we do not gain much when compiling with a job number based on
the output of "getconf _NPROCESSORS_ONLN" - quite the contrary, the
aarch64 containers are currently aborting quite often since they
are running out of memory. Thus let's rather use a fixed number
like 3 in the jobs here, so that e.g. two threads can actively run
while a third one might be waiting for I/O operations to complete.
This should hopefully fix the out-of-memory failures in the aarch64
CI jobs.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210217102531.1441557-1-thuth@redhat.com>
[AJB: add comment]
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
.travis.yml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index fc27fd6330..4609240b5a 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -86,9 +86,11 @@ git:
submodules: false
# Common first phase for all steps
+# We no longer use nproc to calculate jobs:
+# https://travis-ci.community/t/nproc-reports-32-cores-on-arm64/5851
before_install:
- if command -v ccache ; then ccache --zero-stats ; fi
- - export JOBS=$(($(getconf _NPROCESSORS_ONLN) + 1))
+ - export JOBS=3
- echo "=== Using ${JOBS} simultaneous jobs ==="
# Configure step - may be overridden
--
2.20.1
next prev parent reply other threads:[~2021-02-17 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 12:19 [PATCH v1 0/6] my current testing/next queue (meson/gitlab/fedora bump) Alex Bennée
2021-02-17 12:19 ` [PATCH v1 1/6] meson.build: expose TCG cross compiler information in summary Alex Bennée
2021-02-17 12:19 ` [PATCH v1 2/6] gitlab-ci: Display Avocado log content when tests timeout Alex Bennée
2021-02-17 13:38 ` Thomas Huth
2021-02-17 12:19 ` [PATCH v1 3/6] gitlab-ci.yml: Run check-tcg with TCI Alex Bennée
2021-02-17 16:38 ` Philippe Mathieu-Daudé
2021-02-17 17:51 ` Richard Henderson
2021-02-17 12:19 ` [PATCH v1 4/6] docker: Bump Fedora images to release 33 Alex Bennée
2021-02-17 12:19 ` Alex Bennée [this message]
2021-02-17 12:19 ` [PATCH v1 6/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test Alex Bennée
2021-02-17 13:20 ` Marc-André Lureau
2021-02-19 15:53 ` Willian Rampazzo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210217121932.19986-6-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).