linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: CKI Project <cki-project@redhat.com>,
	Jianlin Shi <jishi@redhat.com>,
	catalin marinas <catalin.marinas@arm.com>,
	Jianwen Ji <jiji@redhat.com>,
	linux-arm-kernel@lists.infradead.org,
	Hangbin Liu <haliu@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel?5.12.0-rc2 (arm-next)
Date: Fri, 12 Mar 2021 11:05:42 +0000	[thread overview]
Message-ID: <20210312110541.GA32208@willie-the-truck> (raw)
In-Reply-To: <1718119924.31068909.1615544529191.JavaMail.zimbra@redhat.com>

On Fri, Mar 12, 2021 at 05:22:09AM -0500, Veronika Kabatova wrote:
> ----- Original Message -----
> > From: "Will Deacon" <will@kernel.org>
> > To: "CKI Project" <cki-project@redhat.com>
> > Cc: "Jianlin Shi" <jishi@redhat.com>, "catalin marinas" <catalin.marinas@arm.com>, "Jianwen Ji" <jiji@redhat.com>,
> > linux-arm-kernel@lists.infradead.org, "Hangbin Liu" <haliu@redhat.com>
> > Sent: Friday, March 12, 2021 10:43:47 AM
> > Subject: Re: ❌ FAIL: Test report for kernel	5.12.0-rc2 (arm-next)
> > On Thu, Mar 11, 2021 at 08:51:04PM -0000, CKI Project wrote:
> > > Hardware testing
> > > ----------------
> > > We booted each kernel and ran the following tests:
> > > 
> > >   aarch64:
> > >     Host 1:
> > >        ❌ Networking tunnel: geneve basic test
> > 
> > Hmm, looks like this one actually passed:
> > 
> > https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/03/11/625627/build_aarch64_redhat%3A1119860/tests/Networking_tunnel_geneve_basic_test/9700954_aarch64_1_resultoutputfile.log
> > 
> > or am I looking in the wrong place?
> > 
> 
> Hi,
> 
> the test actually didn't finish but aborted. It's also a bit visible in
> the logs you linked as they are cut off after the basic_nic test started.

Ah yes, I missed that it was truncated. Thanks.

> I checked the console log and this looks like the issue we just reported
> to upstream:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=212227
> 
> as the test is killed (test timeout) after spamming the console log for
> an hour with a message about unregister_netdevice. So it's a bug, just
> not arm-tree specific.

Cheers. I don't have anything queued that I would expect to break only a
networing test (more like the machine wouldn't boot if we broke something)
so I'll go ahead with my pull request as planned.

Will

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

  reply	other threads:[~2021-03-12 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 20:51 ❌ FAIL: Test report for kernel 5.12.0-rc2 (arm-next) CKI Project
2021-03-12  9:43 ` Will Deacon
2021-03-12 10:22   ` Veronika Kabatova
2021-03-12 11:05     ` Will Deacon [this message]
2021-03-15  1:49     ` ❌ FAIL: Test report for kernel?5.12.0-rc2 (arm-next) Hangbin Liu

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=20210312110541.GA32208@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=vkabatov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).