? FAIL: Test report for kernel 5.13.0-rc4 (arm-next, 8124c8a6)

[Mark Rutland]

On Wed, Jun 02, 2021 at 11:12:27AM +0100, Will Deacon wrote:
> Hi all,
> 
> On Wed, Jun 02, 2021 at 01:35:01AM -0000, CKI Project wrote:
> > We ran automated tests on a recent commit from this kernel tree:
> > 
> >        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> >             Commit: 8124c8a6b353 - Linux 5.13-rc4
> 
> As above, this is a run against plain -rc4 in preparation for testing the
> 5.14 queue on top to detect any regressions.
> 
> > The results of these automated tests are provided below.
> > 
> >     Overall result: FAILED (see details below)
> >              Merge: OK
> >            Compile: OK
> >              Tests: FAILED
> > 
> > All kernel binaries, config files, and logs are available for download here:
> > 
> >   https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/06/01/313156257
> > 
> > One or more kernel tests failed:
> > 
> >     aarch64:
> >      ❌ LTP
> 
> The two tests failing here are 'statx04' and 'hugeshmat04':
> 
> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/06/01/313156257/build_aarch64_redhat%3A1310052388/tests/LTP/10079826_aarch64_1_resultoutputfile.log
> 
> (grep for FAIL). I've not had a chance to dig into them yet.

I'm dumping some info below in case this is helpful for anyone.

For statx04, the logs at:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/06/01/313156257/build_aarch64_redhat%3A1310052388/tests/LTP/10079826_aarch64_1_syscalls.run.log

... have a bunch of successful successful statx04 tests, then one fails
on a FUSE directory:

| tst_test.c:899: TINFO: Trying FUSE...
| tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s
| statx04.c:44: TPASS: sys_statx(AT_FDCWD, mntpoint/test_dir1, 0, 0, &buf)
| statx04.c:53: TFAIL: STATX_ATTR_COMPRESSED flag is not set
| statx04.c:58: TFAIL: STATX_ATTR_APPEND flag is not set
| statx04.c:63: TFAIL: STATX_ATTR_IMMUTABLE flag is not set
| statx04.c:68: TFAIL: STATX_ATTR_NODUMP flag is not set
| statx04.c:77: TPASS: sys_statx(AT_FDCWD, mntpoint/test_dir2, 0, 0, &buf)
| statx04.c:86: TPASS: STATX_ATTR_COMPRESSED flag is not set
| statx04.c:91: TPASS: STATX_ATTR_APPEND flag is not set
| statx04.c:96: TPASS: STATX_ATTR_IMMUTABLE flag is not set
| statx04.c:101: TPASS: STATX_ATTR_NODUMP flag is not set
| tst_test.c:1379: TINFO: Testing on tmpfs
| tst_test.c:888: TINFO: Skipping mkfs for TMPFS filesystem
| tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s
| statx04.c:127: TCONF: FS_IOC_GETFLAGS not supported: ENOTTY (25)

I don't know whether that's expected or not -- do we have a good run to
compare to? ... and is this potentially the first time we've tested
this?

For hugeshmat04 the logs at:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/06/01/313156257/build_aarch64_redhat%3A1310052388/tests/LTP/10079826_aarch64_1_hugetlb.run.log

... don't give much of an indication of the problem:

| tst_hugepage.c:58: TINFO: 1 hugepage(s) reserved
| tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s
| tst_hugepage.c:58: TINFO: 513 hugepage(s) reserved
| hugeshmat04.c:60: TBROK: shmat: EINVAL (22)

Thanks,
Mark.