Re: UM-Linux compilation on Android Common Kernels

On Fri, Mar 1, 2024 at 10:34 AM Gustavo Padovan
<[email protected]> wrote:
>
>
>
> On 3/1/24 15:30, Todd Kjos wrote:
>
> On Fri, Mar 1, 2024 at 10:22 AM Gustavo Padovan
> <[email protected]> wrote:
>
> Hi Todd,
>
> On 3/1/24 15:15, Todd Kjos wrote:
>
> On Thu, Jul 13, 2023 at 12:08 AM Guillaume Tucker
> <[email protected]> wrote:
>
> On 06/07/2023 19:00, Todd Kjos wrote:
>
> Any progress on this? (at least doing the um builds?)
>
> On Thu, Mar 16, 2023 at 3:46 PM Todd Kjos <[email protected] <mailto:[email protected]>> wrote:
>
>     On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker
>     <[email protected] <mailto:[email protected]>> wrote:
>     >
>     > Hi Todd,
>     >
>     > On 14/09/2022 22:36, Todd Kjos via groups.io <http://groups.io> wrote:
>     > > Is there an ETA for at least doing the builds?
>     >
>     > I don't think anyone else is asking for user-mode builds, and
>     > adding this new architecture with a new sub-architecture
>     > parameter is not as trivial as adding a few lines of YAML config.
>     > So unless someone on this list is interested, or someone wants to
>     > run an internship topic around that, I think you'll have to go
>     > and find someone to do the work.
>     >
>     > KernelCI is starting to run KUnit which does involve UM-Linux
>     > builds but that's all done "under the hood" by the KUnit
>     > framework.  Still, I guess it would catch some build errors as a
>     > side-effect.  So an alternative is to wait for that to be fully
>     > in production (first half 2023) and we can consider enabling it
>     > on some Android kernel trees.
>
>     Is this in production now?
>
> No, the timeline for making the new API & Pipeline as the new
> production system is basically bumped to 2024.  However, KUnit
> jobs are now being run every day on our staging instance and
> we're planning to have an "early access" stable instance online
> in the next couple of months.  I think we'll get back to you at
> that point.
>
> Any update on the schedule for the new API/Pipeline or the "early access"?
>
>
> We are enabling the new system as we speak, but slowly with a handful of trees we are building and a handful of tests as a first step. We are also sorting out ways for to share the results, since the new system won't have a web dashboard for the time being.
>
> I am getting to this thread just now, but it seems that for your need, in a first step, would be adding user-mode builds. Is that correct? What would be in your scope after that?
>
> Currently no expectations beyond UM builds. Right now the point is to
> catch cases where we might inadvertently break UM since it isn't part
> of our workflow, but might be part of the workflow for downstream
> users of ACK kernels. We'll make a separate request if we need more
> than builds.
>
>
> Okay. Let me see if we add yours soon in the new system. (it is really painful to add new things to the legacy system).
>
> Would you be a recipient of the build breakages? I also want to figure out the regression reporting structure.

Yes, several of us on the Android kernel team are closely monitoring
kernelci breakages. These can be reported to us in the same way as
other breakages (visible as build breaks at
https://linux.kernelci.org/job/android/)

>
> Best regards,
>
> Gustavo
>
> --
> Gustavo Padovan
> Kernel Lead
>
> Collabora Ltd.
> Platinum Building, St John's Innovation Park
> Cambridge CB4 0DS, UK
> Registered in England & Wales, no. 5513718
>
>
> --
> Gustavo Padovan
> Kernel Lead
>
> Collabora Ltd.
> Platinum Building, St John's Innovation Park
> Cambridge CB4 0DS, UK
> Registered in England & Wales, no. 5513718