Total jobs: 68
Total errors: 33 (48.53%)
LAVA errors: 0 (0.00%)
Test errors: 1 (1.47%)
Job errors: 11 (16.18%)
Infra errors: 21 (30.88%)
Canceled jobs: 0 (0.00%)
Device type: dragonboard-845c
Total jobs: 68
Total errors: 33 (48.53%)
Error type: Job
Error count: 11 (16.18%)
Error: No match for error type 'Job', message 'login-action timed out after 870 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6011428
Error: No match for error type 'Job', message 'login-action timed out after 869 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6008583
Error: wait for prompt timed out
Count: 3 (4.41%)
IDs:
db845c-03:
6008580 6008581 6008582
Error: No match for error type 'Job', message 'login-action timed out after 828 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6008573
Error: No match for error type 'Job', message 'login-action timed out after 864 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6008571
Error: No match for error type 'Job', message 'login-action timed out after 616 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6008565
Error: No match for error type 'Job', message 'login-action timed out after 872 seconds'
Count: 2 (2.94%)
IDs:
db845c-03:
6008539 6008547
Error: No match for error type 'Job', message 'login-action timed out after 873 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6008541
Error type: Infrastructure
Error count: 21 (30.88%)
Error: Connection closed
Count: 21 (30.88%)
IDs:
db845c-03:
6008528 6008534 6008535 6008536 6008538
6008540 6008543 6008545 6008549 6008568
6008569 6008570 6008572 6008574 6008577
6008578 6008579 6008584 6008585
db845c-05:
6008508
db845c-07:
6008546
Error type: Test
Error count: 1 (1.47%)
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 283 seconds'
Count: 1 (1.47%)
IDs:
db845c-03:
6008562
On Mon, 26 Dec 2022 at 09:47, Nathan Chancellor <nathan(a)kernel.org> wrote:
>
> On Fri, Dec 16, 2022 at 03:15:58PM -0500, Josef Bacik wrote:
> > We had a recent bug that would have been caught by a newer compiler with
> > -Wmaybe-uninitialized and would have saved us a month of failing tests
> > that I didn't have time to investigate.
> >
> > Signed-off-by: Josef Bacik <josef(a)toxicpanda.com>
>
> This needs to be moved to the condflags section, as
> -Wmaybe-uninitialized is a GCC only flag, so this breaks our builds with
> clang on next-20221226:
>
> error: unknown warning option '-Wmaybe-uninitialized'; did you mean '-Wuninitialized'? [-Werror,-Wunknown-warning-option]
LKFT test farm also noticed these build breaks with clang on next-20221226.
Regressions found on arm64, riscv, s390 and powerpc
- build/clang-lkftconfig
- build/clang-15-lkftconfig
- build/clang-15-defconfig-40bc7ee5
- build/clang-15-defconfig
- build/clang-nightly-defconfig
- build/clang-15-lkftconfig-compat
- build/clang-nightly-defconfig-40bc7ee5
- build/clang-nightly-lkftconfig
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=1
ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- 'HOSTCC=sccache clang'
'CC=sccache clang'
error: unknown warning option '-Wmaybe-uninitialized'; did you mean
'-Wuninitialized'? [-Werror,-Wunknown-warning-option]
make[4]: *** [/builds/linux/scripts/Makefile.build:252:
fs/btrfs/super.o] Error 1
> I can send a patch on Tuesday unless the original commit can be amended.
ref:
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221226/te…
- Naresh