From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Martin Doucha <martin.doucha@suse.com>,
LTP List <ltp@lists.linux.it>,
automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] September LTP release
Date: Fri, 9 Sep 2022 16:36:45 +0200 [thread overview]
Message-ID: <YxtPfXA6I64lS2oK@pevik> (raw)
In-Reply-To: <YxsfGUpRLAx6uIU7@yuki>
Hi all,
[ Cc automated-testing ML ]
> Hi!
> > Maye split this work into pieces? something like:
> > - announcement email,
> > - collecting patch lists for a new release,
> > - writing release notes, or paperwork,
> > - uploading tarballs
> > - pre-testing against different Linux distribution
> > You can still send the announcement email, and other volunteers do the rest.
> > (if applicable, I can take patch reviews or upload tarballs work)
> I guess that would work too, as long as we have volunteers.
I could do part of work as well. I volunteer to upload the tarballs.
I also try to help with reviewing and testing pre release fixes.
I usually do network tests changelog, which is tiny part of whole changelog.
I try to do at least some of runtime tests on SLES and Tumbleweed, I suppose
Martin helps with it as usually. Obviously more people should do pre-release
testing.
And in my non work time build testing on Buildroot (finds various build problems
on other libc and generally the embedded world).
> > Btw, I'll also cover the full pre-test against the RHEL series before
> > release.
> > > And in order not to delay things further, please start pointing out
> > > patches that should go in before the release. I guess Martin runtime
> > > fixes should go in. Anything else?
> > The "Track minimal size per filesystem" from Petr should be included as
> > well.
> > (I guess it is still WIP)
Yes, it's still in WIP. I'll finish the "Track minimal size per filesystem"
patchset after merging $TST_ALL_FILESYSTEMS.
I'd really prefer to get reviewed and merged "v5 shell: df01.sh:
$TST_ALL_FILESYSTEMS (.all_filesystems)" [1] [2]. Martin has suggested for v4 to
use 2 different enums (TST_FS_UNAVAILABLE and TST_FS_UNSUPPORTED instead of
TST_FS_UNSUPPORTED) [3]. I'm willing to implement that in Monday if are others
ok and hope this is the last change and whole thing can be merged.
> Ah, right, we have to do something about xfs, I guess that if we do not
> manage until the release a minimal fix would be to increase the minimal
> device size.
I don't mind to merge "Fix mkfs.xfs 300MB min size requirement (v5.19.0)" [4]
[5] as a temporary fix before release.
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/project/ltp/list/?series=317639
[2] https://lore.kernel.org/ltp/20220909141840.18327-1-pvorel@suse.cz/
[3] https://lore.kernel.org/ltp/70df29e7-0097-c698-b6ba-e3f87da3893f@suse.cz/
[4] https://patchwork.ozlabs.org/project/ltp/list/?series=314303&state=*
[5] https://lore.kernel.org/ltp/20220818100945.7935-1-pvorel@suse.cz/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-09 14:37 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 [this message]
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
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=YxtPfXA6I64lS2oK@pevik \
--to=pvorel@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@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 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.