* ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
@ 2019-10-02 4:27 CKI Project
2019-10-02 5:32 ` Greg KH
0 siblings, 1 reply; 6+ messages in thread
From: CKI Project @ 2019-10-02 4:27 UTC (permalink / raw)
To: Linux Stable maillist; +Cc: Xiong Zhou
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
Commit: 643b3a097f86 - selftests: pidfd: Fix undefined reference to pthread_create()
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/200069
One or more kernel tests failed:
ppc64le:
❌ xfstests: xfs
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 3 architectures:
aarch64:
make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
ppc64le:
make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
x86_64:
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
✅ xfstests: ext4
✅ xfstests: xfs
✅ selinux-policy: serge-testsuite
✅ lvm thinp sanity
✅ storage: software RAID testing
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
✅ Podman system integration test (as root)
✅ Podman system integration test (as user)
✅ Loopdev Sanity
✅ jvm test suite
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts test
✅ Networking: igmp conformance test
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking tunnel: gre basic
✅ Networking tunnel: vxlan basic
✅ audit: audit testsuite test
✅ httpd: mod_ssl smoke sanity
✅ iotop: sanity
✅ tuned: tune-processes-through-perf
✅ Usex - version 1.9-29
✅ storage: SCSI VPD
🚧 ✅ LTP lite
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ Memory function: kaslr
🚧 ✅ Networking bridge: sanity
🚧 ✅ Networking MACsec: sanity
🚧 ✅ Networking route: pmtu
🚧 ✅ Networking tunnel: geneve basic test
🚧 ✅ L2TP basic test
🚧 ✅ Networking vnic: ipvlan/basic
🚧 ✅ ALSA PCM loopback test
🚧 ✅ ALSA Control (mixer) Userspace Element test
🚧 ✅ trace: ftrace/tracer
🚧 ✅ Networking route_func: local
🚧 ✅ Networking route_func: forward
🚧 ✅ Networking ipsec: basic netns transport
🚧 ✅ Networking ipsec: basic netns tunnel
ppc64le:
Host 1:
✅ Boot test
✅ xfstests: ext4
❌ xfstests: xfs
✅ selinux-policy: serge-testsuite
✅ lvm thinp sanity
✅ storage: software RAID testing
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
✅ Podman system integration test (as root)
✅ Podman system integration test (as user)
✅ Loopdev Sanity
✅ jvm test suite
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts test
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking tunnel: gre basic
✅ Networking tunnel: vxlan basic
✅ audit: audit testsuite test
✅ httpd: mod_ssl smoke sanity
✅ iotop: sanity
✅ tuned: tune-processes-through-perf
✅ Usex - version 1.9-29
🚧 ✅ LTP lite
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ Memory function: kaslr
🚧 ✅ Networking bridge: sanity
🚧 ✅ Networking MACsec: sanity
🚧 ✅ Networking route: pmtu
🚧 ✅ Networking tunnel: geneve basic test
🚧 ✅ L2TP basic test
🚧 ✅ Networking ipsec: basic netns tunnel
🚧 ✅ Networking vnic: ipvlan/basic
🚧 ✅ ALSA PCM loopback test
🚧 ✅ ALSA Control (mixer) Userspace Element test
🚧 ✅ trace: ftrace/tracer
🚧 ✅ Networking route_func: local
🚧 ✅ Networking route_func: forward
x86_64:
Host 1:
✅ Boot test
✅ xfstests: ext4
✅ xfstests: xfs
✅ selinux-policy: serge-testsuite
✅ lvm thinp sanity
✅ storage: software RAID testing
🚧 ✅ IOMMU boot test
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
✅ Storage SAN device stress - megaraid_sas
Host 3:
✅ Boot test
✅ Storage SAN device stress - mpt3sas driver
Host 4:
⚡ 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
✅ Podman system integration test (as root)
✅ Podman system integration test (as user)
✅ Loopdev Sanity
✅ jvm test suite
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts test
✅ Networking: igmp conformance test
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking tunnel: gre basic
✅ Networking tunnel: vxlan basic
✅ audit: audit testsuite test
✅ httpd: mod_ssl smoke sanity
✅ iotop: sanity
✅ tuned: tune-processes-through-perf
✅ pciutils: sanity smoke test
✅ Usex - version 1.9-29
✅ storage: SCSI VPD
✅ stress: stress-ng
🚧 ✅ LTP lite
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ Memory function: kaslr
🚧 ✅ Networking bridge: sanity
🚧 ✅ Networking MACsec: sanity
🚧 ✅ Networking route: pmtu
🚧 ✅ Networking tunnel: geneve basic test
🚧 ✅ L2TP basic test
🚧 ✅ Networking vnic: ipvlan/basic
🚧 ✅ ALSA PCM loopback test
🚧 ✅ ALSA Control (mixer) Userspace Element test
🚧 ⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Networking route_func: local
🚧 ⚡⚡⚡ Networking route_func: forward
🚧 ⚡⚡⚡ Networking ipsec: basic netns transport
🚧 ⚡⚡⚡ Networking ipsec: basic netns tunnel
Host 5:
✅ Boot test
🚧 ✅ IPMI driver test
🚧 ✅ IPMItool loop stress test
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
2019-10-02 4:27 ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next) CKI Project
@ 2019-10-02 5:32 ` Greg KH
2019-10-02 9:55 ` ? " Jakub Racek
2019-10-02 11:34 ` ❌ " Veronika Kabatova
0 siblings, 2 replies; 6+ messages in thread
From: Greg KH @ 2019-10-02 5:32 UTC (permalink / raw)
To: CKI Project; +Cc: Linux Stable maillist, Xiong Zhou
On Wed, Oct 02, 2019 at 12:27:24AM -0400, CKI Project 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/sashal/linux-stable.git
> Commit: 643b3a097f86 - selftests: pidfd: Fix undefined reference to pthread_create()
That is 5.4-rc1?
Why are you sending those results to the stable list?
confused,
greg k-h
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ? FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
2019-10-02 5:32 ` Greg KH
@ 2019-10-02 9:55 ` Jakub Racek
2019-10-02 11:34 ` ❌ " Veronika Kabatova
1 sibling, 0 replies; 6+ messages in thread
From: Jakub Racek @ 2019-10-02 9:55 UTC (permalink / raw)
To: Greg KH; +Cc: CKI Project, Linux Stable maillist
+++ Greg KH [02/10/19 07:32 +0200]:
>On Wed, Oct 02, 2019 at 12:27:24AM -0400, CKI Project 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/sashal/linux-stable.git
>> Commit: 643b3a097f86 - selftests: pidfd: Fix undefined reference to pthread_create()
>
>That is 5.4-rc1?
I think so. The makefile says:
VERSION = 5
PATCHLEVEL = 4
SUBLEVEL = 0
EXTRAVERSION = -rc1
NAME = Bobtail Squid
Is the kernel repo above (branch stable-next) supposed to send results
to a different mailing list than stable@vger.kernel.org?
I'm not the one who usually deals with triggers/adding trees, but at
least I can confirm details until Veronika shows up.
>
>Why are you sending those results to the stable list?
>
>confused,
>
>greg k-h
>
--
Best regards,
Jakub Racek
ARK
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
2019-10-02 5:32 ` Greg KH
2019-10-02 9:55 ` ? " Jakub Racek
@ 2019-10-02 11:34 ` Veronika Kabatova
2019-10-02 13:56 ` ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next) Sasha Levin
1 sibling, 1 reply; 6+ messages in thread
From: Veronika Kabatova @ 2019-10-02 11:34 UTC (permalink / raw)
To: Greg KH; +Cc: CKI Project, Linux Stable maillist
----- Original Message -----
> From: "Greg KH" <greg@kroah.com>
> To: "CKI Project" <cki-project@redhat.com>
> Cc: "Linux Stable maillist" <stable@vger.kernel.org>
> Sent: Wednesday, October 2, 2019 7:32:02 AM
> Subject: Re: ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
>
> On Wed, Oct 02, 2019 at 12:27:24AM -0400, CKI Project 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/sashal/linux-stable.git
> > Commit: 643b3a097f86 - selftests: pidfd: Fix undefined
> > reference to pthread_create()
>
> That is 5.4-rc1?
>
> Why are you sending those results to the stable list?
>
> confused,
>
Hi,
Sasha has requested to have stable-next tested and results sent to this list:
https://gitlab.com/cki-project/pipeline-data/commit/16e0c06addbe62c689782357673f69bb7dff4d9a
Veronika
> greg k-h
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next)
2019-10-02 11:34 ` ❌ " Veronika Kabatova
@ 2019-10-02 13:56 ` Sasha Levin
2019-10-02 14:08 ` Greg KH
0 siblings, 1 reply; 6+ messages in thread
From: Sasha Levin @ 2019-10-02 13:56 UTC (permalink / raw)
To: Veronika Kabatova; +Cc: Greg KH, CKI Project, Linux Stable maillist
On Wed, Oct 02, 2019 at 07:34:33AM -0400, Veronika Kabatova wrote:
>
>
>----- Original Message -----
>> From: "Greg KH" <greg@kroah.com>
>> To: "CKI Project" <cki-project@redhat.com>
>> Cc: "Linux Stable maillist" <stable@vger.kernel.org>
>> Sent: Wednesday, October 2, 2019 7:32:02 AM
>> Subject: Re: ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
>>
>> On Wed, Oct 02, 2019 at 12:27:24AM -0400, CKI Project 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/sashal/linux-stable.git
>> > Commit: 643b3a097f86 - selftests: pidfd: Fix undefined
>> > reference to pthread_create()
>>
>> That is 5.4-rc1?
>>
>> Why are you sending those results to the stable list?
>>
>> confused,
>>
>
>Hi,
>
>Sasha has requested to have stable-next tested and results sent to this list:
>
>https://gitlab.com/cki-project/pipeline-data/commit/16e0c06addbe62c689782357673f69bb7dff4d9a
Greg, this is the stable-next thing we talked about at LPC; it's just a
subset of linux-next of stable tagged commits to help us identify issues
before it actually hits upstream.
I can drop the mails to stable@ if you'd like, but ideally it should
only be one mail a day.
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next)
2019-10-02 13:56 ` ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next) Sasha Levin
@ 2019-10-02 14:08 ` Greg KH
0 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2019-10-02 14:08 UTC (permalink / raw)
To: Sasha Levin; +Cc: Veronika Kabatova, CKI Project, Linux Stable maillist
On Wed, Oct 02, 2019 at 09:56:27AM -0400, Sasha Levin wrote:
> On Wed, Oct 02, 2019 at 07:34:33AM -0400, Veronika Kabatova wrote:
> >
> >
> > ----- Original Message -----
> > > From: "Greg KH" <greg@kroah.com>
> > > To: "CKI Project" <cki-project@redhat.com>
> > > Cc: "Linux Stable maillist" <stable@vger.kernel.org>
> > > Sent: Wednesday, October 2, 2019 7:32:02 AM
> > > Subject: Re: ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
> > >
> > > On Wed, Oct 02, 2019 at 12:27:24AM -0400, CKI Project 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/sashal/linux-stable.git
> > > > Commit: 643b3a097f86 - selftests: pidfd: Fix undefined
> > > > reference to pthread_create()
> > >
> > > That is 5.4-rc1?
> > >
> > > Why are you sending those results to the stable list?
> > >
> > > confused,
> > >
> >
> > Hi,
> >
> > Sasha has requested to have stable-next tested and results sent to this list:
> >
> > https://gitlab.com/cki-project/pipeline-data/commit/16e0c06addbe62c689782357673f69bb7dff4d9a
>
> Greg, this is the stable-next thing we talked about at LPC; it's just a
> subset of linux-next of stable tagged commits to help us identify issues
> before it actually hits upstream.
>
> I can drop the mails to stable@ if you'd like, but ideally it should
> only be one mail a day.
Ah, ok, I was thinking CKI was testing Linus's tree for some reason and
sending the results only to the stable list, which would be odd. If
this is your stuff, and you get use out of it, that's fine with me, I'll
be quiet :)
thanks,
greg k-h
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-10-02 14:08 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-02 4:27 ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next) CKI Project
2019-10-02 5:32 ` Greg KH
2019-10-02 9:55 ` ? " Jakub Racek
2019-10-02 11:34 ` ❌ " Veronika Kabatova
2019-10-02 13:56 ` ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next) Sasha Levin
2019-10-02 14:08 ` Greg KH
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.