All of lore.kernel.org
 help / color / mirror / Atom feed
From: Veronika Kabatova <vkabatov@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jianwen Ji <jiji@redhat.com>, Hangbin Liu <haliu@redhat.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Jianlin Shi <jishi@redhat.com>,
	CKI Project <cki-project@redhat.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: ❌ FAIL: Test report for kernel 5.5.0-rc6-40f39e8.cki (arm-next)
Date: Thu, 16 Jan 2020 09:14:49 -0500 (EST)	[thread overview]
Message-ID: <1309735432.2414024.1579184089001.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAKv+Gu-CEGOdTvektx_pqD=WqUXFi3YKXmj=pka5CiHc-6dCSQ@mail.gmail.com>

----- Original Message ----- 

> From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
> To: "CKI Project" <cki-project@redhat.com>
> Cc: "Jianwen Ji" <jiji@redhat.com>, "Hangbin Liu" <haliu@redhat.com>,
> "Catalin Marinas" <catalin.marinas@arm.com>, "Jianlin Shi"
> <jishi@redhat.com>, "Will Deacon" <will@kernel.org>, "linux-arm-kernel"
> <linux-arm-kernel@lists.infradead.org>
> Sent: Thursday, January 16, 2020 2:30:06 PM
> Subject: Re: ❌ FAIL: Test report for kernel 5.5.0-rc6-40f39e8.cki (arm-next)

> On Thu, 16 Jan 2020 at 14:20, CKI Project < cki-project@redhat.com > wrote:

> > Hello,
> 

> > 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: 40f39e8372fe - Merge branch 'for-next/core' 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/385274
> 

> > One or more kernel tests failed:
> 

> > aarch64:
> 
> > ❌ Networking tunnel: gre basic
> 
> > ❌ Networking tunnel: vxlan basic
> 

> > We hope that these logs can help you find the problem quickly. For the full
> 
> > detail on our testing procedures, please scroll to the bottom of this
> > message.
> 

> > Please reply to this email if you have any questions about the tests that
> > we
> 
> > ran or if you have any suggestions on how to make future tests more
> > effective.
> 

> May I kindly suggest that you stop cc'ing the mailing list on automated,
> unmoderated CI results?

> It's great that you run a CI system, but you should really have the minimal
> courtesy to double check failure reports before sending them out into the
> world.

Hi Ard,

we are sorry about that. The testing and emails to the list were requested
by Will a while ago. If he or Catalin change their minds about them we will
stop sending them, in the meanwhile you can always set up a filter.

We are not paid by ARM so the testing is a "strive for the best" effort,
as we have a bunch of ARM machines we're willing to lend to community for
extra coverage. We always cc the test maintainers and also us to take a
look at the issues if they do occur. As Rachel mentioned, we already put
a workaround in place to prevent these issues from happening further so
hopefully you won't get more emails because of these Beaker bugs.


Thanks,
Veronika

> > ,-. ,-.
> 
> > ( C ) ( K ) Continuous
> 
> > `-',-.`-' Kernel
> 
> > ( I ) Integration
> 
> > `-'
> 
> > ______________________________________________________________________________
> 

> > Compile testing
> 
> > ---------------
> 

> > We compiled the kernel for 1 architecture:
> 

> > aarch64:
> 
> > make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
> 

> > Hardware testing
> 
> > ----------------
> 
> > We booted each kernel and ran the following tests:
> 

> > aarch64:
> 
> > Host 1:
> 
> > ✅ Boot test
> 
> > ✅ Podman system integration test (as root)
> 
> > ✅ Podman system integration test (as user)
> 
> > ✅ LTP
> 
> > ✅ Loopdev Sanity
> 
> > ✅ Memory function: memfd_create
> 
> > ✅ AMTU (Abstract Machine Test Utility)
> 
> > ✅ Networking bridge: sanity
> 
> > ✅ Ethernet drivers sanity
> 
> > ✅ Networking MACsec: sanity
> 
> > ✅ Networking socket: fuzz
> 
> > ✅ Networking sctp-auth: sockopts test
> 
> > ✅ Networking: igmp conformance test
> 
> > ✅ Networking route: pmtu
> 
> > ✅ Networking route_func: local
> 
> > ✅ Networking route_func: forward
> 
> > ✅ Networking TCP: keepalive test
> 
> > ✅ Networking UDP: socket
> 
> > ✅ Networking tunnel: geneve basic test
> 
> > ❌ Networking tunnel: gre basic
> 
> > ✅ L2TP basic test
> 
> > ❌ Networking tunnel: vxlan basic
> 
> > ✅ Networking ipsec: basic netns transport
> 
> > ✅ Networking ipsec: basic netns tunnel
> 
> > ✅ audit: audit testsuite test
> 
> > ✅ httpd: mod_ssl smoke sanity
> 
> > ✅ tuned: tune-processes-through-perf
> 
> > ✅ ALSA PCM loopback test
> 
> > ✅ ALSA Control (mixer) Userspace Element test
> 
> > ✅ storage: SCSI VPD
> 
> > ✅ trace: ftrace/tracer
> 
> > 🚧 ✅ CIFS Connectathon
> 
> > 🚧 ✅ POSIX pjd-fstest suites
> 
> > ⏱ jvm test suite
> 
> > ⏱ Memory function: kaslr
> 
> > ⏱ LTP: openposix test suite
> 
> > ⏱ Networking vnic: ipvlan/basic
> 
> > ⏱ iotop: sanity
> 
> > ⏱ Usex - version 1.9-29
> 
> > ⏱ storage: dm/common
> 

> > Host 2:
> 

> > ⚡ Internal infrastructure issues prevented one or more tests (marked
> 
> > with ⚡⚡⚡) from running on this architecture.
> 
> > This is not the fault of the kernel that was tested.
> 

> > ✅ Boot test
> 
> > ✅ xfstests: ext4
> 
> > ✅ xfstests: xfs
> 
> > ✅ selinux-policy: serge-testsuite
> 
> > ✅ lvm thinp sanity
> 
> > ✅ storage: software RAID testing
> 
> > ✅ stress: stress-ng
> 
> > 🚧 ⚡⚡⚡ IPMI driver test
> 
> > 🚧 ✅ IPMItool loop stress test
> 
> > 🚧 ✅ Storage blktests
> 

> > Test sources: https://github.com/CKI-project/tests-beaker
> 
> > 💚 Pull requests are welcome for new tests or improvements to existing
> > tests!
> 

> > Waived tests
> 
> > ------------
> 
> > If the test run included waived tests, they are marked with 🚧. Such tests
> > are
> 
> > executed but their results are not taken into account. Tests are waived
> > when
> 
> > their results are not reliable enough, e.g. when they're just introduced or
> > are
> 
> > being fixed.
> 

> > Testing timeout
> 
> > ---------------
> 
> > We aim to provide a report within reasonable timeframe. Tests that haven't
> 
> > finished running are marked with ⏱. Reports for non-upstream kernels have
> 
> > a Beaker recipe linked to next to each host.
> 

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


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

  parent reply	other threads:[~2020-01-16 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 13:19 ❌ FAIL: Test report for kernel 5.5.0-rc6-40f39e8.cki (arm-next) CKI Project
2020-01-16 13:55 ` Rachel Sibley
     [not found] ` <CAKv+Gu-CEGOdTvektx_pqD=WqUXFi3YKXmj=pka5CiHc-6dCSQ@mail.gmail.com>
2020-01-16 14:14   ` Veronika Kabatova [this message]
2020-01-16 14:33     ` Will Deacon
     [not found]       ` <CAKv+Gu_BqEz_Q1H9CXe1ZTCkExEnAtsrdEQcPXZthsgGhWxK9A@mail.gmail.com>
2020-01-16 16:26         ` Veronika Kabatova
     [not found]     ` <CAKv+Gu_Q5tpf1UakSHuDKq7_3BgMavpwucK6cz_k=VcDD0y8dw@mail.gmail.com>
2020-01-16 15:31       ` Jakub Racek

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=1309735432.2414024.1579184089001.JavaMail.zimbra@redhat.com \
    --to=vkabatov@redhat.com \
    --cc=ard.biesheuvel@linaro.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=will@kernel.org \
    /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.