On Tue, Sep 24, 2024 at 04:42:17PM +0200, Anders Roxell wrote:
Hi Sasha,
We're happy to assist from the LKFT side.
Our main focus is validating LTS kernels, while testing mainline and next kernels remains more of a best-effort approach. We'll start by enabling the same set of builds and running them on virtual hardware, then move on to boot tests on the DUTs. If needed, we can discuss expanding DUT testing later.
We'll run this once per day to help manage costs.
Thank you!
For more context, it would inderectly help the LTS trees as well: we often end up releasing commits that came vie pull requests to Linus during the merge window right after -rc1 is released, so this process will help improve the testing story behind those.
Regarding the merge SHAs - will Linus be pulling yours into his tree? If not, we might end up testing the same kernel with different SHAs. Are you two coordinating to ensure consistency?
Not yet, this is "experimental" to see if it catches real issues that Linus would have missed. It's very possible that a year for now I'll be asking to remove this tree :)
Long term, is the plan to shift testing from Linus' tree to yours, once we've ramped up on your side?
In a sense: I think that the longer term is to prevent Linus from pulling branches that would break tests, so it would make sense to focus more in linus-next
Also, how would you like to collaborate on regression reports?
What works best for you here? I don't really mind looking at mails/dashboards/etc.
Just trying to get a better sense of the workload.
Thanks for your efforts on this!
Thanks for looking into this!