public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Zorro Lang <zlang@redhat.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] tests/*/Makefile: make sure group.list DIRT exists before install
Date: Mon, 26 Feb 2024 08:57:03 -0800	[thread overview]
Message-ID: <20240226165703.GQ6188@frogsfrogsfrogs> (raw)
In-Reply-To: <CA+chaQdFJkmc540nzz0PKJLtXMGg4yCfHYkMZaxCooCZ6PdaLw@mail.gmail.com>

On Sun, Feb 25, 2024 at 07:01:48PM +0100, Martin Jansa wrote:
> On Sun, Feb 25, 2024 at 5:35 PM Zorro Lang <zlang@redhat.com> wrote:
> >
> > On Thu, Feb 08, 2024 at 11:52:41PM +0100, Martin Jansa wrote:
> > > * sometimes make install was failing with:
> > >   cp: cannot stat 'group.list': No such file or directory
> > >   and bunch of non-fatal messages:
> > >   mv: failed to preserve ownership for 'group.list': Invalid argument
> >
> > I'm wondering ... isn't that expected?
> >
> > Why not let "make install" fail directly, if there's not a completed "make" ?
> > Isn't that more familiar?
> 
> It might if it fails reliably, but in OpenEmbedded builds where I was
> seeing this in some CI builds it failed in about 1% of the builds, which is
> enough to make the failure annoying and if this is meant to be expected
> behavior than not failing reliably, for context see:
> https://git.openembedded.org/meta-openembedded/commit/?id=e8a1c9823b7e55dd2ca7f19a3fd3a05ae676bfe2

Aha, that explains the weird language in the commit message about
"removing tests/*/group.list" and "adding some sleep" even though the
patch doesn't actually do that.

> so here it calls make in do_compile task (defined in autotools-brokensep),
> then make install in do_install task and do_install was failing
> _sometimes_, and I haven't seen single failure since this change was
> applied.
> 
> I'm not very familiar with xfstests, I wasn't even building it
> intentionally (it's just part of one CI job which builds everything
> available), so I might be missing something.

Huh, that looks like the result of make trying to run the 'default' and
'install' targets in parallel because there's no "install: default"
clause in the Makefile.

Soooo... are you folks using 'make -jXX default install' in your CI
system?

--D

> Regards,
> 

  reply	other threads:[~2024-02-26 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 22:52 [PATCH] tests/*/Makefile: make sure group.list DIRT exists before install Martin Jansa
2024-02-25 16:30 ` Zorro Lang
2024-02-25 18:01   ` Martin Jansa
2024-02-26 16:57     ` Darrick J. Wong [this message]
2024-02-26 17:31       ` Martin Jansa
2024-02-26 19:12         ` Darrick J. Wong
2024-02-27  3:05         ` Zorro Lang

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=20240226165703.GQ6188@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=martin.jansa@gmail.com \
    --cc=zlang@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