From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>,
Richard Palethorpe <rpalethorpe@suse.com>,
Martin Doucha <martin.doucha@suse.com>,
automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] September LTP release
Date: Fri, 30 Sep 2022 16:00:48 +0200 [thread overview]
Message-ID: <Yzb2kPIErlgJVUe6@pevik> (raw)
In-Reply-To: <CAEemH2eb3EvUL7c3M1=FgPoYmYTcYDgQAM7NUxY7pSAN0xUjuw@mail.gmail.com>
Hi Li,
> Petr Vorel <pvorel@suse.cz> wrote:
> > 185 df01 42 TFAIL: 'df -T -P' failed, not expected.
> > This is known:
> > https://lore.kernel.org/linux-xfs/YvZTpQFinpkB06p9@pevik/
> > I've mention that yesterday, that I'll fix it after the release
> > https://lore.kernel.org/ltp/YzGDdC76DLmrJyys@pevik/
> > I'll try to send a patch soon and we can decide whether we merge it before
> > release or not.
FYI It looks like this has been fixed, it works on machine with Tumbleweed,
kernel 6.0.0-rc7-1.g74aafe0-default, mkfs.xfs version 5.19.0. It also works on
Tumbleweed with stable kernel 5.19.10-1-default. I started to bisect, but
haven't found first broken commit (too lazy to get deeper into this).
Kind regards,
Petr
> Ah, yes, I shouldn't skip reading emails so careless :).
> Thanks for the upcoming fix, let's see what it looks like and then decide
> to merge or not.
> And zram01.sh fails due XFS minimal size. I also try to send a patch soon.
> Thanks! Next, I will only investigate the io_uring failures.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-30 14:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 8:49 [LTP] September LTP release Cyril Hrubis
2022-09-09 10:39 ` Li Wang
2022-09-09 11:10 ` Cyril Hrubis
2022-09-09 14:36 ` Petr Vorel
2022-09-13 7:11 ` Li Wang
2022-09-13 11:50 ` Cyril Hrubis
2022-09-26 9:58 ` Cyril Hrubis
2022-09-26 10:13 ` Li Wang
2022-09-26 12:26 ` Petr Vorel
2022-09-27 7:44 ` Li Wang
2022-09-27 8:10 ` Petr Vorel
2022-09-27 8:25 ` Li Wang
2022-09-30 14:00 ` Petr Vorel [this message]
2022-09-26 10:43 ` Petr Vorel
2022-09-26 10:48 ` Petr Vorel
2022-09-09 14:56 ` Petr Vorel
2022-09-12 9:36 ` Cyril Hrubis
2022-09-12 9:45 ` Petr Vorel
2022-09-13 8:19 ` xuyang2018.jy
2022-09-13 9:23 ` Cyril Hrubis
2022-09-19 15:31 ` Petr Vorel
2022-09-23 11:01 ` Petr Vorel
2022-09-23 11:59 ` Cyril Hrubis
2022-09-23 12:16 ` Petr Vorel
2022-09-26 9:49 ` Cyril Hrubis
2022-09-30 10:05 ` Petr Vorel
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=Yzb2kPIErlgJVUe6@pevik \
--to=pvorel@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.com \
--cc=rpalethorpe@suse.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