> On 3 Aug 2021, at 23:16, Nathan Chancellor <nat...@kernel.org> wrote: > > On 8/3/2021 12:52 PM, ci_not...@linaro.org wrote: >> Successfully identified regression in *linux* in CI configuration >> tcwg_kernel/llvm-master-aarch64-next-allyesconfig. So far, this commit has >> regressed CI configurations: >> - tcwg_kernel/llvm-master-aarch64-next-allyesconfig >> Culprit: >> <cut> >> commit 3d463dd5023b5a58b3c37207d65eeb5acbac2be3 >> Author: Krzysztof Kozlowski <krzysztof.kozlow...@canonical.com> >> Date: Thu Jul 29 12:40:19 2021 +0200 >> nfc: fdp: constify several pointers >> Several functions do not modify pointed data so arguments and local >> variables can be const for correctness and safety. This allows also >> making file-scope nci_core_get_config_otp_ram_version array const. >> Signed-off-by: Krzysztof Kozlowski >> <krzysztof.kozlow...@canonical.com> >> Signed-off-by: David S. Miller <da...@davemloft.net> >> </cut> ... > > As far as I can tell from these links, next-20210730 is still being tested, > whereas there have been two new linux-next releases that have had this fixed. > Would it be possible to tell the system to test the latest release, which I > believe should build without errors according to our CI? > > https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/1093846606 >
Hi Nathan, It can take a couple of days to bisect regressions when build farm is loaded. Other than that, CI automatically picks up new linux-next on every build. Regards, -- Maxim Kuvyrkov https://www.linaro.org _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
