From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] ci: split linux-gcc into linux-gcc and linux-gcc-extra
Date: Thu, 13 Jun 2019 05:53:50 -0700 (PDT) [thread overview]
Message-ID: <pull.266.git.gitgitgadget@gmail.com> (raw)
For people like me, who often look at our CI builds, it is hard to tell
whether test suite failures in the linux-gcc job stem from the first make
test run, or from the second one, after setting all kinds of GIT_TEST_*
variables to non-default values.
Let's make it easier on people like me.
This also helps the problem where the CI builds often finish the other jobs
waaaay before linux-gcc finally finishes, too: linux-gcc and linux-gcc-extra
can be run in parallel, on different agents.
Johannes Schindelin (1):
ci: split the `linux-gcc` job into two jobs
.travis.yml | 4 ++++
azure-pipelines.yml | 39 ++++++++++++++++++++++++++++++++++++++
ci/install-dependencies.sh | 4 ++--
ci/lib.sh | 4 ++--
ci/run-build-and-tests.sh | 5 ++---
5 files changed, 49 insertions(+), 7 deletions(-)
base-commit: b697d92f56511e804b8ba20ccbe7bdc85dc66810
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-266%2Fdscho%2Fsplit-gcc-ci-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-266/dscho/split-gcc-ci-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/266
--
gitgitgadget
next reply other threads:[~2019-06-13 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 12:53 Johannes Schindelin via GitGitGadget [this message]
2019-06-13 12:53 ` [PATCH 1/1] ci: split the `linux-gcc` job into two jobs Johannes Schindelin via GitGitGadget
2019-06-13 15:33 ` SZEDER Gábor
2019-06-13 15:56 ` Junio C Hamano
2019-06-13 16:51 ` Johannes Schindelin
2019-06-13 17:43 ` SZEDER Gábor
2019-06-14 19:35 ` Johannes Schindelin
2019-06-25 8:56 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.266.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).