public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat•com>
To: CKI Project <cki-project@redhat•com>,
	Rachel Sibley <rasibley@redhat•com>
Cc: catalin marinas <catalin.marinas@arm•com>,
	Memory Management <mm-qe@redhat•com>,
	Will Deacon <will@kernel•org>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.4.0-rc5-34072e5.cki (arm-next)
Date: Wed, 30 Oct 2019 07:02:34 -0400 (EDT)	[thread overview]
Message-ID: <845770535.9696874.1572433354366.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191030100631.GA17773@willie-the-truck>



----- Original Message -----
> Hi all,
> 
> On Tue, Oct 29, 2019 at 11:43:13PM -0000, CKI Project wrote:
> > We ran automated tests on a recent commit from this kernel tree:
> > 
> >        Kernel repo:
> >        git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> >             Commit: 34072e52a3fc - Merge remote-tracking branch
> >             'arm64/for-next/memory-hotremove' into for-kernelci
> > 
> > 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://artifacts.cki-project.org/pipelines/255362
> > 
> > One or more kernel tests failed:
> > 
> >     aarch64:
> >      ❌ LTP lite
> 
> As far as I can make out from the logs, this is because the following
> syscall tests failed:
> 
> 	preadv202
> 	preadv202_64
> 	readv02

@CKI: There seem to be only high level test status?
      Can you upload also verbose test output to artifacts?

The file is usually named *.run.log. It gives much better details for failures:

tst_test.c:1116: INFO: Timeout per run is 0h 05m 00s
preadv202.c:82: PASS: preadv2() failed as expected: EINVAL (22)
preadv202.c:82: PASS: preadv2() failed as expected: EINVAL (22)
preadv202.c:82: PASS: preadv2() failed as expected: EOPNOTSUPP (95)
preadv202.c:86: FAIL: preadv2() failed unexpectedly, expected EFAULT: SUCCESS (0)
preadv202.c:82: PASS: preadv2() failed as expected: EBADF (9)
preadv202.c:82: PASS: preadv2() failed as expected: EBADF (9)
preadv202.c:82: PASS: preadv2() failed as expected: EISDIR (21)
preadv202.c:82: PASS: preadv2() failed as expected: ESPIPE (29)


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-10-30 11:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 23:43 ❌ FAIL: Test report for kernel 5.4.0-rc5-34072e5.cki (arm-next) CKI Project
2019-10-30 10:03 ` Jan Stancek
2019-10-30 10:07   ` Will Deacon
2019-10-30 10:45     ` Will Deacon
2019-10-30 11:42       ` Robin Murphy
2019-10-30 15:08         ` Robin Murphy
2019-10-31 11:06           ` Catalin Marinas
2019-10-31 11:26             ` Will Deacon
2019-10-30 10:06 ` Will Deacon
2019-10-30 11:02   ` Jan Stancek [this message]
2019-10-30 12:37     ` Rachel Sibley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=845770535.9696874.1572433354366.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat$(echo .)com \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=cki-project@redhat$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=mm-qe@redhat$(echo .)com \
    --cc=rasibley@redhat$(echo .)com \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox