From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yoann Congal <yoann.congal@smile.fr>,
openembedded-core@lists.openembedded.org,
Tim Orling <ticotimo@gmail.com>,
Martin Jansa <martin.jansa@gmail.com>,
Ross Burton <ross.burton@arm.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [OE-core] [PATCH v3] strace: Disable bluetooth support by default
Date: Thu, 14 Dec 2023 12:30:17 +0000 [thread overview]
Message-ID: <32526832f7e19b83551e786f0ab185cf7b879d1b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8bin4UjXK=gj-aR35t=ajQmNFsD8LKsiX_7x2-z08fYg@mail.gmail.com>
On Thu, 2023-12-14 at 13:17 +0100, Alexander Kanavin wrote:
> On Thu, 14 Dec 2023 at 13:11, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>
> > I've wondered about this. The "prebuild" ends up quite slow as it would
> > involve rust for example and when I last tried this, it ended up being
> > a pain and just increased overall testing times even of the overall
> > load on the AB might have been lower. So I'm really not sure. I suspect
> > it wouldn't help the pain points as much as you think as there are
> > other sstate reuse issues at play too.
>
> But is it worth experimenting with it anyway, to collect some data?
> The more we know, the more we can rule out.
I think it would have a huge impact on the throughput of patches :( An
hour or two before the majority of the tests even start.
Cheers,
Richard
next prev parent reply other threads:[~2023-12-14 12:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 8:56 [PATCH v3] strace: Disable bluetooth support by default Yoann Congal
2023-12-14 9:09 ` [OE-core] " Alexander Kanavin
2023-12-14 9:50 ` Richard Purdie
2023-12-14 12:03 ` Alexander Kanavin
2023-12-14 12:11 ` Richard Purdie
2023-12-14 12:17 ` Alexander Kanavin
2023-12-14 12:30 ` Richard Purdie [this message]
2023-12-14 12:34 ` Alexander Kanavin
2023-12-14 12:37 ` Richard Purdie
2023-12-14 13:02 ` Jose Quaresma
2023-12-14 18:29 ` Khem Raj
2023-12-14 18:53 ` Khem Raj
2023-12-14 19:33 ` Alexandre Belloni
2023-12-14 19:36 ` Khem Raj
2023-12-15 10:49 ` Yoann Congal
2023-12-15 11:59 ` Ross Burton
2023-12-15 12:24 ` Richard Purdie
2023-12-14 13:23 ` 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=32526832f7e19b83551e786f0ab185cf7b879d1b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=ticotimo@gmail.com \
--cc=yoann.congal@smile.fr \
/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.