From: Will Deacon <will@kernel.org>
To: Rachel Sibley <rasibley@redhat.com>
Cc: Jianwen Ji <jiji@redhat.com>, Hangbin Liu <haliu@redhat.com>,
catalin.marinas@arm.com, Jianlin Shi <jishi@redhat.com>,
CKI Project <cki-project@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.5.0-rc6-e31626d.cki (arm-next)
Date: Wed, 15 Jan 2020 18:27:18 +0000 [thread overview]
Message-ID: <20200115182717.GC31673@willie-the-truck> (raw)
In-Reply-To: <5d991a60-f98e-cc47-7188-d996d0832bb3@redhat.com>
Hi Rachel,
On Wed, Jan 15, 2020 at 01:11:04PM -0500, Rachel Sibley wrote:
> On 1/15/20 12:54 PM, Will Deacon wrote:
> > On Wed, Jan 15, 2020 at 05:38:26PM -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: e31626d443db - Merge branches 'for-next/asm-annotations', 'for-next/cpufeatures', 'for-next/e0pd', 'for-next/kexec/cleanup', 'for-next/kexec/file-kdump', 'for-next/misc', 'for-next/nofpsimd' and 'for-next/perf' 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/383787
> > >
> > > One or more kernel tests failed:
> > >
> > > aarch64:
> > > ❌ Networking tunnel: geneve basic test
> > > ❌ Networking tunnel: gre basic
> >
> >
> > Hmm. If I look at the files corresponding to those tests in the logs linked
> > to above, they all seem to have passed. For example:
> >
> > https://artifacts.cki-project.org/pipelines/383787/logs/aarch64_host_1_Networking_tunnel__gre_basic_resultoutputfile.log
> >
> > Am I missing something?
>
> This is an infrastructure problem with restraint harness, it's taking too
> long extracting the tests-beaker repo where our tests live and watchdog is
> aborting the tests during setup phase. We are actively debugging this
> problem. Feel free to ignore these failures, sorry for the noise!
Okey doke, I'm more than happy to ignore them :)
Thanks for the quick reply.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-15 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 17:38 ❌ FAIL: Test report for kernel 5.5.0-rc6-e31626d.cki (arm-next) CKI Project
2020-01-15 17:54 ` Will Deacon
2020-01-15 18:11 ` Rachel Sibley
2020-01-15 18:27 ` Will Deacon [this message]
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=20200115182717.GC31673@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=haliu@redhat.com \
--cc=jiji@redhat.com \
--cc=jishi@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rasibley@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.