stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	LTP List <ltp@lists.linux.it>
Cc: Linux Stable maillist <stable@vger.kernel.org>,
	CKI Project <cki-project@redhat.com>,
	Memory Management <mm-qe@redhat.com>
Subject: Re: ❌ FAIL: Stable queue: queue-5.3
Date: Sun, 27 Oct 2019 05:32:23 -0400 (EDT)	[thread overview]
Message-ID: <2111263587.9218283.1572168743324.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYurG8gSO+xFc5LJvLMrqTyHG85oxH9=pSQ1LmPCa6PkqQ@mail.gmail.com>



----- Original Message -----
> Hi Jan,
> 
> On Sun, 27 Oct 2019 at 04:04, CKI Project <cki-project@redhat.com> wrote:
> >
> >
> > Hello,
> >
> > We ran automated tests on a patchset that was proposed for merging into
> > this
> > kernel tree. The patches were applied to:
> >
> >        Kernel repo:
> >        https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> >             Commit: 365dab61f74e - Linux 5.3.7
> >
> > 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/249576
> >
> > One or more kernel tests failed:
> >
> >     x86_64:
> >      ❌ LTP lite
> 
> I see these three failures from the logs,

[CC LTP list]

> 
> LTP syscalls:
> fallocate05                                        FAIL       1

tst_mkfs.c:89: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
mke2fs 1.45.3 (14-Jul-2019)
tst_test.c:1116: INFO: Timeout per run is 0h 05m 00s
tst_fill_fs.c:29: INFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:29: INFO: Creating file mntpoint/file1 size 8070086
tst_fill_fs.c:29: INFO: Creating file mntpoint/file2 size 3971177
tst_fill_fs.c:29: INFO: Creating file mntpoint/file3 size 36915315
tst_fill_fs.c:29: INFO: Creating file mntpoint/file4 size 70310993
tst_fill_fs.c:29: INFO: Creating file mntpoint/file5 size 4807935
tst_fill_fs.c:29: INFO: Creating file mntpoint/file6 size 90739786
tst_fill_fs.c:29: INFO: Creating file mntpoint/file7 size 76896492
tst_fill_fs.c:49: INFO: write(): ENOSPC (28)
fallocate05.c:50: PASS: write() wrote 8192 bytes
fallocate05.c:54: FAIL: fallocate() succeeded unexpectedly

So, test filled filesystem and fallocate() succeeded anyway.

> 
> LTP mm:
> oom03                                              FAIL       2
> oom05                                              FAIL       2

This looks like test issue. systemd on Fedora31 started using cgroup2 exclusively:
  cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate)

Tests are trying to mount single hierarchy on cgroup1:
[pid 283933] 04:57:26 mkdir("/dev/cgroup", 0777) = 0
[pid 283933] 04:57:26 mount("memcg", "/dev/cgroup", "cgroup", 0, "memory") = -1 EBUSY (Device or resource busy)


  reply	other threads:[~2019-10-27  9:32 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 22:33 ❌ FAIL: Stable queue: queue-5.3 CKI Project
2019-10-27  7:02 ` Naresh Kamboju
2019-10-27  9:32   ` Jan Stancek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-26  2:00 CKI Project
2019-11-22  1:23 CKI Project
2019-11-18 15:00 CKI Project
     [not found] ` <8e0fa6de-b6b1-23ac-9e77-d425c8d1ba22@redhat.com>
2019-11-19 12:37   ` Laura Abbott
2019-11-19 12:44     ` Greg KH
2019-11-19 12:50       ` Laura Abbott
2019-11-21 17:53         ` Greg KH
2019-11-11 21:58 CKI Project
2019-11-11 19:57 CKI Project
2019-11-11 15:36 CKI Project
2019-11-11 20:10 ` Rachel Sibley
2019-11-11 20:47   ` Laura Abbott
2019-11-11 12:50 CKI Project
2019-11-11 11:43 CKI Project
2019-11-10 16:12 CKI Project
2019-11-08 23:24 CKI Project
2019-11-08 21:16 CKI Project
2019-11-08 21:55 ` Ondrej Mosnacek
2019-11-08  5:51 CKI Project
2019-11-06 20:56 CKI Project
2019-11-07 10:22 ` Hangbin Liu
2019-11-05  2:51 CKI Project
2019-11-05  1:14 CKI Project
2019-11-05  6:37 ` Greg KH
2019-11-05  8:15   ` Naresh Kamboju
2019-11-04 11:21 CKI Project
2019-10-30 20:12 CKI Project
2019-10-29 20:22 CKI Project
2019-10-29 17:48 CKI Project
2019-10-28  2:44 CKI Project
2019-10-28  2:30 CKI Project
2019-10-28  1:22 CKI Project
2019-10-27 23:47 CKI Project
2019-10-27 14:34 CKI Project
2019-10-27  9:18 CKI Project
2019-10-27  9:08 CKI Project
2019-10-27  9:20 ` Sasha Levin
2019-10-25 11:25 CKI Project
2019-10-22  2:54 CKI Project
2019-10-16 14:03 CKI Project
2019-10-16 13:56 CKI Project
2019-10-15 22:30 CKI Project
2019-10-15  6:39 CKI Project
2019-10-15  4:49 CKI Project
2019-10-10 13:17 CKI Project
2019-10-10 10:26 CKI Project
2019-10-10 10:51 ` Veronika Kabatova
2019-10-10  6:43 CKI Project
2019-10-09 22:11 CKI Project
2019-10-09 22:44 ` Sasha Levin
2019-10-10  1:09   ` Don Zickus
2019-10-10  6:30     ` Naresh Kamboju
2019-10-16 17:25       ` ? " Jakub Racek
2019-10-08 19:17  " CKI Project
2019-10-08 19:10 CKI Project
2019-10-08 18:03 CKI Project
2019-10-08 18:57 ` Greg KH
2019-10-06  4:57 CKI Project
2019-10-01 19:25 CKI Project
2019-10-01 18:32 CKI Project
2019-10-01 19:19 ` Greg KH

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=2111263587.9218283.1572168743324.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=mm-qe@redhat.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=stable@vger.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 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).