Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Cc: Ross Burton <ross.burton@arm.com>,
	Chuck Wolber <chuck.wolber@boeing.com>,
	 Adrian Freihofer <adrian.freihofer@siemens.com>,
	Marta Rybczynska <marta.rybczynska@syslinbit.com>,
	Jon Mason <Jon.Mason@arm.com>,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] Latest AB-INT unexplained mystery failure
Date: Mon, 14 Oct 2024 17:11:57 +0100	[thread overview]
Message-ID: <eb5b6f2f2de5796ed7f757ef7f1680d5a2be6130.camel@linuxfoundation.org> (raw)
In-Reply-To: <17FE55BCAF4D83DD.4702@lists.openembedded.org>

On Mon, 2024-10-14 at 14:46 +0100, Richard Purdie via lists.openembedded.org wrote:
> c) source mirroring failing on AB
> ---------------------------------
> 
> https://valkyrie.yoctoproject.org//#/builders/82/builds/15
> https://valkyrie.yoctoproject.org//#/builders/82/builds/16
> 
> Sources are still mirrored off typhoon but we've stopped that cluster
> and are running off valkyrie. This could mean sources don't appear
> "fast" in the mirror until that mirroring moves to the new NAS.
> 
> Who/Plan: Michael to transition mirroring to run of valkyrie NAS

I talked with Michael and there is no automated rsync. Software has
been updated since the last one and that is why things are not
updating. As the mirroring is transitioned this issue will go away.

> f) CVE database corruption
> --------------------------
> 
> See list discussion:
> 
> https://lists.openembedded.org/g/openembedded-core/message/205715
> 
> Has a bug:
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14899
> 
> I'm at a loss on this one. Started to wonder if an rsync job is
> trampling the file. Check with Michael.
> 
> Who/Plan: Ask Michael about rsync job

There is no issue with any rsync job. I did realise I'd not merged the
patch I thought I had though. I will do so and see if that isolates the
issue.

Cheers,

Richard



  parent reply	other threads:[~2024-10-14 16:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17FE0CA1425F2338.24631@lists.openembedded.org>
2024-10-14 13:46 ` [OE-core] Latest AB-INT unexplained mystery failure Richard Purdie
2024-10-22 13:30   ` Ross Burton
2024-10-15  8:18 ` Richard Purdie
     [not found] ` <17FE55BCAF4D83DD.4702@lists.openembedded.org>
2024-10-14 16:11   ` Richard Purdie [this message]
2024-10-14 20:40   ` Richard Purdie
2024-10-15  8:23   ` Richard Purdie
2024-10-15 10:09   ` Richard Purdie
2024-10-19 11:05 ` Richard Purdie
     [not found] ` <17FFD5DF016C394D.24795@lists.openembedded.org>
2024-10-19 21:48   ` Richard Purdie
2024-10-21 10:55     ` Alexander Kanavin
2024-10-22  9:58       ` Richard Purdie
2024-10-22 19:48         ` Michael Halstead
2024-10-23 15:28         ` Khem Raj
2024-10-23 15:33           ` Alexander Kanavin
2024-10-23 15:35             ` Richard Purdie

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=eb5b6f2f2de5796ed7f757ef7f1680d5a2be6130.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Jon.Mason@arm.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=chuck.wolber@boeing.com \
    --cc=marta.rybczynska@syslinbit.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=mhalstead@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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