Re: [linux-yocto] Seeking information on use of linux-yocto-dev
On 28 Apr 2024, at 20:29, Sourabh Banerjee (QUIC) wrote: > For the builds that Autobuilder runs how are the test cases run? The autobuilder runs oe-selftest, and testimage inside the images that it builds for qemu. > Does AB support any remote test invocation, such that the artifacts created by > Autobuilder are sent to a remotely connected device to be tested? No. >> Our meta-arm CI does do builds with linux-yocto-dev, and we find new >> regressions or failures every few weeks or so. It fails enough due to >> upstream >> churn that we tell it to consider failures in linux-yocto-dev to be warnings >> not >> errors… > > I suppose this is meta-arm CI at some ARM location? And it different from the > meta-arm CI in AB? > Is this CI just a build or a it runs a test as well? Yes, this is the meta-arm CI that is defined by meta-arm/.gitlab-ci.yml. The primary instance of this is internal to Arm but the co-maintainer has an instance of this publicly available, for example: https://gitlab.com/jonmason00/meta-arm/-/pipelines/1272833190 This also runs testimage on images that can run inside a qemu or a FVP. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13880): https://lists.yoctoproject.org/g/linux-yocto/message/13880 Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
> -Original Message- > From: Ross Burton > Sent: Wednesday, April 24, 2024 4:30 PM > To: Sourabh Banerjee (QUIC) > Cc: Bruce Ashfield ; linux- > yo...@lists.yoctoproject.org > Subject: Re: [linux-yocto] Seeking information on use of linux-yocto-dev > > WARNING: This email originated from outside of Qualcomm. Please be wary of > any links or attachments, and do not enable macros. > On 23 Apr 2024, at 17:33, Sourabh Banerjee (QUIC) > <mailto:quic_sbane...@quicinc.com> wrote: > > 2. Is linux-yocto-dev tested by the autobuilder or a similar CI? > > We've had adding it to the autobuilder CI on the wishlist for quite a while. I > thought > Ross added something a few months ago, but I can't recall the details. We do > need > to decide on exactly what to test, making sure it is lighter than what is run > against > the release kernels that I generate. > > If it was in CI there might be some breakage due to the bleeding edge nature > of > the updates. We just wouldn't want it to block any project milestones if run > as > part of CI. > > Added Ross to get a bit more clarity on autobuilder setup to linux-yocto-dev. > > The public autobuilder doesn’t -- yet -- do linux-yocto-dev builds. Mainly > because it would need to be ran separately as it does break more than the > stable > kernels so would need to be monitored by a human but not impact the existing > builds, and the extra load on the AB would ideally be balanced out by some > other changes so the net change is zero. For the builds that Autobuilder runs how are the test cases run? Does AB support any remote test invocation, such that the artifacts created by Autobuilder are sent to a remotely connected device to be tested? > > Our meta-arm CI does do builds with linux-yocto-dev, and we find new > regressions or failures every few weeks or so. It fails enough due to upstream > churn that we tell it to consider failures in linux-yocto-dev to be warnings > not > errors… I suppose this is meta-arm CI at some ARM location? And it different from the meta-arm CI in AB? Is this CI just a build or a it runs a test as well? > > Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13879): https://lists.yoctoproject.org/g/linux-yocto/message/13879 Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
On 23 Apr 2024, at 17:33, Sourabh Banerjee (QUIC) wrote: 2. Is linux-yocto-dev tested by the autobuilder or a similar CI? We've had adding it to the autobuilder CI on the wishlist for quite a while. I thought Ross added something a few months ago, but I can't recall the details. We do need to decide on exactly what to test, making sure it is lighter than what is run against the release kernels that I generate. If it was in CI there might be some breakage due to the bleeding edge nature of the updates. We just wouldn't want it to block any project milestones if run as part of CI. Added Ross to get a bit more clarity on autobuilder setup to linux-yocto-dev. The public autobuilder doesn’t -- yet -- do linux-yocto-dev builds. Mainly because it would need to be ran separately as it does break more than the stable kernels so would need to be monitored by a human but not impact the existing builds, and the extra load on the AB would ideally be balanced out by some other changes so the net change is zero. Our meta-arm CI does do builds with linux-yocto-dev, and we find new regressions or failures every few weeks or so. It fails enough due to upstream churn that we tell it to consider failures in linux-yocto-dev to be warnings not errors… Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13863): https://lists.yoctoproject.org/g/linux-yocto/message/13863 Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
On Tue, Apr 23, 2024 at 12:34 PM Sourabh Banerjee (QUIC) <
quic_sbane...@quicinc.com> wrote:
>
>
> > -Original Message-
> > From: Bruce Ashfield
> > Sent: Tuesday, April 23, 2024 7:22 AM
> > To: Sourabh Banerjee (QUIC)
> > Cc: linux-yocto@lists.yoctoproject.org
> > Subject: Re: [linux-yocto] Seeking information on use of linux-yocto-dev
> >
> >
> > On Mon, Apr 22, 2024 at 4:29 PM quic_sbanerje via
> http://lists.yoctoproject.org
> > mailto:quicinc@lists.yoctoproject.org> wrote:
> > From a previous discussion with Richard, I understand, that the
> linux-yocto-dev
> > recipe exists for anyone needing more recent kernels. Bruce is
> maintaining is
> > as a rolling update, and version upgrades are quite frequent.
> >
> > I am seeking information on following to understand use of
> linux-yocto-dev
> > better:
> > 1. When there's a version bump for linux-yocto-dev is there a test suite
> that is
> > run?
> >
> > I have some simple scripts and manual tests that I run against each bump
> of -
> > dev.
> >
> > In particular core-image-kernel-dev and the tightly coupled tools (lttng,
> > systemtap, etc).
> >
> > A boot of systemd based images tends to shake out most of the major
> issues, so
> > that
> > is what I do.
>
> Thank you for pointing to core-image-kernel-dev.
> When building this image do you generally use poky-altcfg, as it includes
> systemd?
>
>
I have my own distro and configuration that I use. But I also do test with
poky and poky-altcfg.
> How is the decision made to create a linux-yocto_${version} recipe from
> linux-yocto-dev recipe? Is it guided by a set cadence?
>
It follows guidance we put together about 10 years ago now, it is somewhere
on the project wiki. I've also covered it in several presentations over the
past
few years as well.
But generally speaking on our non-LTS releases, it is three kernel versions
the latest lts, the latest released kernel around the -m3 timeframe and the
-dev kernel. For our LTS releases, we drop the "latest released" kernel, and
just do lts + dev.
>
> >
> > 2. Is linux-yocto-dev tested by the autobuilder or a similar CI?
> >
> > We've had adding it to the autobuilder CI on the wishlist for quite a
> while. I
> > thought
> > Ross added something a few months ago, but I can't recall the details.
> We do
> > need
> > to decide on exactly what to test, making sure it is lighter than what
> is run
> > against
> > the release kernels that I generate.
> >
> > If it was in CI there might be some breakage due to the bleeding edge
> nature of
> > the updates. We just wouldn't want it to block any project milestones if
> run as
> > part of CI.
> >
>
> Added Ross to get a bit more clarity on autobuilder setup to
> linux-yocto-dev.
>
> >
> > 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the
> BSP layer
> > against kernel upstream?
> >
> > There are some developers that do that, yes. Others use it for the
> AUTOREV
> > and rolling nature of it, etc. Now that even linux-yocto-dev uses
> versioned
> > branches, we could in theory just use linux-yocto for all of those
> purposes, but
> > I still strongly prefer that only our supported versions appear in
> linux-yocto.
> >
> If a BSP maintainer chooses to use linux-yocto-dev and expands the test
> scope
> to frameworks such as Weston, pulseaudio etc., let's say while testing
> detects
> bugs what should be the next step?
>
If the bug is in the kernel, hopefully they'll take it to lkml, since
that's why we
have the -dev kernel tracking the latest. It makes upstream discussions
easier
and more relevant. If it is an issue with the -dev kernel and the rest of OE
core interacting in an unexpected way, then the linux-yocto or oe-core
mailing
lists are used to discuss.
Since -dev kernels are highlighting issues that we will eventually have in a
release, the issues are valid and treat them as such
Bruce
> I am trying to understand can a BSP maintainer use this as a reference to
> test
> and plan ahead.
>
> > Bruce
> >
> >
> >
> >
> >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at
> > its end
> > - "Use the force Harry" - Gandalf, Star Trek II
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13859):
https://lists.yoctoproject.org/g/linux-yocto/message/13859
Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
> -Original Message-
> From: Bruce Ashfield
> Sent: Tuesday, April 23, 2024 7:22 AM
> To: Sourabh Banerjee (QUIC)
> Cc: linux-yocto@lists.yoctoproject.org
> Subject: Re: [linux-yocto] Seeking information on use of linux-yocto-dev
>
>
> On Mon, Apr 22, 2024 at 4:29 PM quic_sbanerje via
> http://lists.yoctoproject.org
> mailto:quicinc@lists.yoctoproject.org> wrote:
> From a previous discussion with Richard, I understand, that the
> linux-yocto-dev
> recipe exists for anyone needing more recent kernels. Bruce is maintaining is
> as a rolling update, and version upgrades are quite frequent.
>
> I am seeking information on following to understand use of linux-yocto-dev
> better:
> 1. When there's a version bump for linux-yocto-dev is there a test suite that
> is
> run?
>
> I have some simple scripts and manual tests that I run against each bump of -
> dev.
>
> In particular core-image-kernel-dev and the tightly coupled tools (lttng,
> systemtap, etc).
>
> A boot of systemd based images tends to shake out most of the major issues, so
> that
> is what I do.
Thank you for pointing to core-image-kernel-dev.
When building this image do you generally use poky-altcfg, as it includes
systemd?
How is the decision made to create a linux-yocto_${version} recipe from
linux-yocto-dev recipe? Is it guided by a set cadence?
>
> 2. Is linux-yocto-dev tested by the autobuilder or a similar CI?
>
> We've had adding it to the autobuilder CI on the wishlist for quite a while. I
> thought
> Ross added something a few months ago, but I can't recall the details. We do
> need
> to decide on exactly what to test, making sure it is lighter than what is run
> against
> the release kernels that I generate.
>
> If it was in CI there might be some breakage due to the bleeding edge nature
> of
> the updates. We just wouldn't want it to block any project milestones if run
> as
> part of CI.
>
Added Ross to get a bit more clarity on autobuilder setup to linux-yocto-dev.
>
> 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the BSP
> layer
> against kernel upstream?
>
> There are some developers that do that, yes. Others use it for the AUTOREV
> and rolling nature of it, etc. Now that even linux-yocto-dev uses versioned
> branches, we could in theory just use linux-yocto for all of those purposes,
> but
> I still strongly prefer that only our supported versions appear in
> linux-yocto.
>
If a BSP maintainer chooses to use linux-yocto-dev and expands the test scope
to frameworks such as Weston, pulseaudio etc., let's say while testing detects
bugs what should be the next step?
I am trying to understand can a BSP maintainer use this as a reference to test
and plan ahead.
> Bruce
>
>
>
>
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee at
> its end
> - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13858):
https://lists.yoctoproject.org/g/linux-yocto/message/13858
Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
On Mon, Apr 22, 2024 at 4:29 PM quic_sbanerje via lists.yoctoproject.org wrote: > From a previous discussion with Richard, I understand, that the > linux-yocto-dev > recipe exists for anyone needing more recent kernels. Bruce is maintaining > is > as a rolling update, and version upgrades are quite frequent. > > I am seeking information on following to understand use of linux-yocto-dev > better: > 1. When there's a version bump for linux-yocto-dev is there a test suite > that is run? > I have some simple scripts and manual tests that I run against each bump of -dev. In particular core-image-kernel-dev and the tightly coupled tools (lttng, systemtap, etc). A boot of systemd based images tends to shake out most of the major issues, so that is what I do. > 2. Is linux-yocto-dev tested by the autobuilder or a similar CI? > We've had adding it to the autobuilder CI on the wishlist for quite a while. I thought Ross added something a few months ago, but I can't recall the details. We do need to decide on exactly what to test, making sure it is lighter than what is run against the release kernels that I generate. If it was in CI there might be some breakage due to the bleeding edge nature of the updates. We just wouldn't want it to block any project milestones if run as part of CI. > 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the > BSP layer > against kernel upstream? > There are some developers that do that, yes. Others use it for the AUTOREV and rolling nature of it, etc. Now that even linux-yocto-dev uses versioned branches, we could in theory just use linux-yocto for all of those purposes, but I still strongly prefer that only our supported versions appear in linux-yocto. Bruce > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13855): https://lists.yoctoproject.org/g/linux-yocto/message/13855 Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] Seeking information on use of linux-yocto-dev
>From a previous discussion with Richard, I understand, that the linux-yocto-dev recipe exists for anyone needing more recent kernels. Bruce is maintaining is as a rolling update, and version upgrades are quite frequent. I am seeking information on following to understand use of linux-yocto-dev better: 1. When there's a version bump for linux-yocto-dev is there a test suite that is run? 2. Is linux-yocto-dev tested by the autobuilder or a similar CI? 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the BSP layer against kernel upstream? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13853): https://lists.yoctoproject.org/g/linux-yocto/message/13853 Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
