All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: randy.macleod@windriver.com
Cc: "Frédéric Martinsons" <frederic.martinsons@gmail.com>,
	"Richard Purdie" <richard.purdie@linuxfoundation.org>,
	"Yash Shinde" <yashinde145@gmail.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>,
	Umesh.Kallapa@windriver.com, Naveen.Gowda@windriver.com,
	Sundeep.Kokkonda@windriver.com,
	Shivaprasad.Moodalappa@windriver.com, Yash.Shinde@windriver.com
Subject: Re: [OE-core] [PATCH v14] Rust Oe-Selftest implementation
Date: Tue, 30 May 2023 22:48:39 +0200	[thread overview]
Message-ID: <20230530204839cb0000a8@mail.local> (raw)
In-Reply-To: <d07d99ab-865b-0d1a-1efb-4e8c167415b8@windriver.com>

Hello,

On 30/05/2023 14:28:24-0400, Randy MacLeod via lists.openembedded.org wrote:
> On 2023-05-30 11:05, Fr�d�ric Martinsons wrote:
> > Oh okay, didn't try that personnaly.
> > the class is currently tied to cargo behavior so for performing rust
> > core tests, it will not be suitable (at least in its present form)
> 
> Well, that's good news in that we won't have to change our approach for v15
> !
> 
> 
> On 2023-05-30 09:59, Richard Purdie wrote:
> > I did put this into a build for testing on the autobuilder. It hasn't
> > been running long and I can already see build failures such as:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/103/builds/6077
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/7200
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/7190
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2923
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/37/builds/7200
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/7217
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/104/builds/6080
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/7146
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/7184
> > 
> > and there will likely be more.
> > 
> > I'm finding this rather frustrating and am not sure how this was
> > tested.
> 
> That's probably my fault. I've been asking Yash to keep pushing and
> suggesting that
> I could help him with testing but the bad news is that we (Wind River)
> have the tail end of a product release cycle happening now.
> 
> I'd like to help out with this, but it'll have to wait for at least 2 months
> and
> that puts us close to the end of M3 so we might have to wait for the
> beginning
> of the fail development cycle.
> 
> Let me talk with Yashe and Sundeep and reply with info on what to expect.

I can run builds on the autobuilders on free cycles as long as it is
clearly communicated that the patch has not been tested so it doesn't
impair other patch testing.



-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-05-30 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 10:51 [PATCH v14] Rust Oe-Selftest implementation Yash Shinde
2023-05-30 13:59 ` Richard Purdie
2023-05-30 14:35   ` [OE-core] " Frédéric Martinsons
2023-05-30 14:44     ` Richard Purdie
2023-05-30 15:05       ` Frédéric Martinsons
2023-05-30 18:28         ` Randy MacLeod
2023-05-30 20:48           ` Alexandre Belloni [this message]
2023-05-30 21:20           ` Richard Purdie
2023-05-31  0:19             ` Randy MacLeod
2023-05-31  6:19             ` Frédéric Martinsons
2023-05-31  6:49   ` Kokkonda, Sundeep
2023-06-02  7:25     ` Shinde, Yash
2023-06-02 11:32       ` Richard Purdie
2023-06-02 11:42         ` Shinde, Yash
2023-06-06  9:47         ` sundeep.kokkonda
2023-06-06 11:06           ` [OE-core] " 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=20230530204839cb0000a8@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Naveen.Gowda@windriver.com \
    --cc=Shivaprasad.Moodalappa@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=Umesh.Kallapa@windriver.com \
    --cc=Yash.Shinde@windriver.com \
    --cc=frederic.martinsons@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yashinde145@gmail.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.