All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stefan Herbrechtsmeier
	<stefan.herbrechtsmeier-oss@weidmueller.com>,
	openembedded-core@lists.openembedded.org
Cc: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Subject: Re: [OE-core] [PATCH 1/4] recipetool: Set master branch only as fallback
Date: Wed, 08 Dec 2021 09:12:33 +0000	[thread overview]
Message-ID: <dedd57475517425d6802a71fb4d46b804dd5eca7.camel@linuxfoundation.org> (raw)
In-Reply-To: <3cda9bd5-1c75-7269-921c-97c1ac6c4fb5@weidmueller.com>

On Wed, 2021-12-08 at 08:45 +0100, Stefan Herbrechtsmeier wrote:
> Hi Richard,
> 
> Am 07.12.2021 um 16:45 schrieb Richard Purdie:
> > On Mon, 2021-12-06 at 09:04 +0100, Stefan Herbrechtsmeier wrote:
> > > From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
> > > 
> > > The commit 'meta/scripts: Manual git url branch additions (dc53fe75cc)'
> > > sets the branch= parameter too early to master and thereby breaks the
> > > -B/--srcbranch option.
> > > 
> > > ERROR: branch= parameter and -B/--srcbranch option cannot both be specified - use one or the other
> > > 
> > > Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
> > > ---
> > > 
> > >   scripts/lib/recipetool/create.py | 15 +++++++--------
> > >   1 file changed, 7 insertions(+), 8 deletions(-)
> > 
> > I think something in this series is causing:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2926/steps/14/logs/stdio
> 
> Sorry I missed the adaption of the test test_devtool_add_fetch_git. It 
> doesn't expect a "branch=master" which is wrong.
> 
> - gitsm://git.yoctoproject.org/mraa;branch=master
> ?                                  --------------
> + gitsm://git.yoctoproject.org/mraa

I suspected something like that, thanks.

> I will update my patch series but need some time to test it locally. The 
> devtool test build a lot of recipe on every run because it use a private 
> sstate cache. How does the autobuilder overcome this problem?

The autobuilder doesn't. We stopped devtool using the public shared cache as it
is shared between autobuilder workers and one worker could delete artefacts
whilst another is using them. This caused all kinds of weird races and there
isn't much extra build time from the autobuilder perspective. The autobuilder
never deletes things from the shared cache outside of the timeout cron job which
removes objects that haven't been accessed in a month or so.

> > 
> > (the other selftest builds also failed)
> What do you mean by this?

I mean that we run oe-selftest on 4 different distros and they all failed the
same way so there were four failures in the build and I just pasted a link to
one of them.

Cheers,

Richard



      parent reply	other threads:[~2021-12-08  9:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  8:04 [PATCH 1/4] recipetool: Set master branch only as fallback Stefan Herbrechtsmeier
2021-12-06  8:04 ` [PATCH 2/4] selftest/recipetool: Split tests into separate test classes Stefan Herbrechtsmeier
2021-12-06  8:04 ` [PATCH 3/4] selftest/recipetool: Add tests for branch parameter and srcbranch option Stefan Herbrechtsmeier
2021-12-06  8:04 ` [PATCH 4/4] selftest: devtool: Separate common functions and devtool sstate setup into two classes Stefan Herbrechtsmeier
2021-12-07 15:45 ` [OE-core] [PATCH 1/4] recipetool: Set master branch only as fallback Richard Purdie
2021-12-08  7:45   ` Stefan Herbrechtsmeier
2021-12-08  8:10     ` Alexander Kanavin
2021-12-08  8:27       ` Stefan Herbrechtsmeier
2021-12-08  8:32         ` Alexander Kanavin
2021-12-08  8:48           ` Stefan Herbrechtsmeier
2021-12-08  9:13       ` Richard Purdie
2021-12-08  9:12     ` Richard Purdie [this message]

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=dedd57475517425d6802a71fb4d46b804dd5eca7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefan.herbrechtsmeier-oss@weidmueller.com \
    --cc=stefan.herbrechtsmeier@weidmueller.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.