Re: new branch + more recent gcc?
Todd Kjos <[email protected]>
| Newsgroups | dev.linux.lists.kernelci |
|---|---|
| Message-ID | <CAHRSSExXLEaz9GpnBXGE383Rq_rzgxFjWqnsxX_fRGkj4848fA@mail.gmail.com> |
On Mon, Jul 1, 2024 at 10:05 AM Todd Kjos <[email protected]> wrote: > > On Mon, Jul 1, 2024 at 10:03 AM Todd Kjos <[email protected]> wrote: > > > > Our kernelci builds are currently use gcc-10 and clang-17. We have 1 > > allmodconfig failure [1] that appears to be caused by the old gcc-10 > > compiler and doesn't reproduce with gcc-11 or later. Can we switch the > > android builds to gcc-13 instead? > > > > [1] https://linux.kernelci.org/build/android/branch/android14-6.1/kernel/android14-6.1.84_r00-129-g87fb1f2f1e795/ > > > > Also, we have a new kernel branch that we'd like to add to the testing: > > > > repo: https://android.googlesource.com/kernel/common > > branch: android15-6.1 > > I specified the wrong branch. Please do not add android15-6.1. The > branch to add is android15-6.6-lts One more thing... can we disable the builds for gki_defconfig? Those always fail with no logs (probably because of pahole). We test that heavily internally so we don't need kernelci to build it. Recap of the asks on this thread: 1) use gcc-13 instead of gcc-10 for android kernel builds 2) add android15-6.6-lts branch to kernelci testing 3) discontinue all gki_defconfig builds Thanks. > > > > > Thanks. > > > > -Todd