git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] fixup??? Merge branch 'ab/ci-updates' into seen
Date: Tue, 23 Nov 2021 13:02:48 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2111231215020.63@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <211123.8635nnydmm.gmgdl@evledraar.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]

Hi Ævar,

On Tue, 23 Nov 2021, Ævar Arnfjörð Bjarmason wrote:

> On Mon, Nov 22 2021, Johannes Schindelin wrote:
>
> > On Mon, 22 Nov 2021, Ævar Arnfjörð Bjarmason wrote:
> >
> >> On Mon, Nov 22 2021, Johannes Schindelin via GitGitGadget wrote:
> >>
> >> > diff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh
> >> > index c0bae709b3b..c508c18ad44 100755
> >> > --- a/ci/run-build-and-tests.sh
> >> > +++ b/ci/run-build-and-tests.sh
> >> > @@ -45,9 +45,8 @@ linux-gcc-4.8)
> >> >  	export MAKE_TARGETS=all
> >> >  	;;
> >> >  esac
> >> > -make -C contrib/scalar test
> >> > -
> >> >  make $MAKE_TARGETS
> >> > +make -C contrib/scalar test
> >> >
> >> >  check_unignored_build_artifacts
> >>
> >> The CI breakage was introduced with the merger with ab/ci-updates, but
> >> the combination of the two just reveals an existing breakage in
> >> js/scalar.
> >
> > Which shows that I was wrong to pander to your repeated demand to include
> > Scalar in the CI builds already at this early stage.
>
> Us finding an a bug in a topic that's happening outside of CI means we
> shouldn't have added it to CI in the first place? Isn't spotting these
> issues a good thing?

Let's analyze "these issues".

Before your patch series, Scalar's `make -C contrib/scalar test` came
after the `make test` which ensured that Git was built. As designed.

After merging your patch series, the `make test` was magically moved
_after_ `make -C contrib/scalar test` (which is wrong for more reasons
than just that Git was not built yet).

So the "issue" is a simple mis-merge, and I provided a fix.

Ciao,
Johannes

P.S.: Of course, this could have been easily avoided by holding off
patches that intentionally touch the very same code as other patch series
that are already in flight. This kind of conflict seems to happen more
often than usual as of late. It happened with the FSMonitor patches and
repo-settings, with the hooks patches, the pager patch yesterday, etc.

  reply	other threads:[~2021-11-23 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 11:02 [PATCH] fixup??? Merge branch 'ab/ci-updates' into seen Johannes Schindelin via GitGitGadget
2021-11-22 15:57 ` Ævar Arnfjörð Bjarmason
2021-11-22 21:58   ` Johannes Schindelin
2021-11-22 23:12     ` Ævar Arnfjörð Bjarmason
2021-11-23 12:02       ` Johannes Schindelin [this message]
2021-11-23 12:18         ` Ævar Arnfjörð Bjarmason
2021-11-23 17:58           ` Junio C Hamano

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=nycvar.QRO.7.76.6.2111231215020.63@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --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).