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: Tue, 27 Sep 2022 10:10:36 +0200 [thread overview]
Message-ID: <YzKv/ClILufSy3up@pevik> (raw)
In-Reply-To: <CAEemH2e6Dzm1ydZt1VZvoxZN4xXyrSZua5jmfxeci8SyXNc2tw@mail.gmail.com>
Hi Li,
...
> 2. df01 got strange failures on XFS (I was unable to reproduce it manually)
> 71 df01 37 TINFO: === Testing on xfs ===
> 72 df01 37 TINFO: Formatting xfs with opts='/dev/loop0'
> 73 df01 37 TINFO: Mounting device: mount -t xfs /dev/loop0
> /mnt/testarea/ltp-pgxzTJRwdG/LTP_df01.IFAhWHNrYb/mntpoint
> 74 df01 37 TINFO: timeout per run is 0h 10m 0s
> 75 df01 37 TPASS: 'df -P' passed.
> 76 total: 301728, used: 17736
> 77 df saved output:
> ...
> 135 df01 38 TFAIL: 'df -a -P' failed, not expected.
> 136 df01 39 TPASS: 'df -i -P' passed.
> ...
> 160 df01 40 TFAIL: 'df -k -P' failed, not expected.
> 161 df01 41 TPASS: 'df -t xfs -P' passed.
> ...
> 185 df01 42 TFAIL: 'df -T -P' failed, not expected.
> 186 df01 43 TPASS: 'df -v /dev/loop0 -P' passed.
> 187 df01 44 TPASS: 'df -h' passed.
> 188 df01 45 TPASS: 'df -H' passed.
> 189 df01 46 TPASS: 'df -m' passed.
> 190 df01 47 TPASS: 'df --version' passed.
> 191 df01 48 TPASS: 'df -x xfs -P' passed.
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.
And zram01.sh fails due XFS minimal size. I also try to send a patch soon.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-27 8:10 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 [this message]
2022-09-27 8:25 ` Li Wang
2022-09-30 14:00 ` Petr Vorel
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=YzKv/ClILufSy3up@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