Skip to contentSkip to conversation

LTP Release preparations

LTP Cyril Hrubis 6 participants 9 messages Apr 30 – May 27

lore
Share & tools
lore
#0 lore raw

Hi!
Given that we have a SUSE Labs konference in the week starting 18. May I would like to start LTP May release preparations a bit sooner.

I would like to do the usual patch review that decides what goes into the release during the first two weeks of May. Followed by the pre-release freeze starting at the 18. May and final release at the end of the Month.

If there are any patches that should be considered to be included before the release, please reply to this email.

Signature · 5 lines
Cyril Hrubis
[email protected]

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp
#1 lore raw
Quoted 11 lines · Cyril Hrubis

Hi!
Given that we have a SUSE Labs konference in the week starting 18. May I would like to start LTP May release preparations a bit sooner.

I would like to do the usual patch review that decides what goes into the release during the first two weeks of May. Followed by the pre-release freeze starting at the 18. May and final release at the end of the Month.

If there are any patches that should be considered to be included before the release, please reply to this email.

- [LTP] [PATCH] userfaultfd: Use two-step handshake to probe features
- [LTP] [PATCH v3] userfaultfd: Minor fixes

Maybe also:
- [LTP] [PATCH] userfaultfd: Add test using UFFDIO_CONTINUE

Best,

Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
#3 lore raw
In reply to Cyril Hrubis
Quoted 11 lines · Cyril Hrubis

Hi!
Given that we have a SUSE Labs konference in the week starting 18. May I would like to start LTP May release preparations a bit sooner.

I would like to do the usual patch review that decides what goes into the release during the first two weeks of May. Followed by the pre-release freeze starting at the 18. May and final release at the end of the Month.

If there are any patches that should be considered to be included before the release, please reply to this email.

I have a cleanup patch (tested by me) to standardize the naming of commonly used macros throughout LTP. This way, contributors don't need to define various similar macros (e.g., /proc, /sys) everywhere, we can manage/unify them all in one place.

It doesn't change any functionality, but it make sense for engineering specifications.

Please consider merging this patch before release:
https://lists.linux.it/pipermail/ltp/2026-May/048154.html

Signature · 5 lines
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp
#4 lore raw
In reply to Cyril Hrubis

Hi!

Quoted 2 lines

Given that we have a SUSE Labs konference in the week starting 18. May I would like to start LTP May release preparations a bit sooner.

If you have anything that isn't a bugfix and should go to the release please point it out ASAP. I would like to start with the freeze and pre-release testing starting next week.

Signature · 5 lines
Cyril Hrubis
[email protected]

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp
#5 lore raw

Hi all,

Quoted 7 lines

Hi!

Quoted 2 lines

Given that we have a SUSE Labs konference in the week starting 18. May I would like to start LTP May release preparations a bit sooner.

If you have anything that isn't a bugfix and should go to the release please point it out ASAP. I would like to start with the freeze and pre-release testing starting next week.

Could we please include these pre-release fixes?

tst_net.sh: tst_rhost_run(): Go to LTP temporary directory first
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
https://lore.kernel.org/ltp/[email protected]/T/#u

checkpatch: Pass git root (tooling, not test itself)
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
https://lore.kernel.org/ltp/[email protected]/T/#t

I'd really get thermal to be merged (at least 1 of 3 tests from Intel). IMHO v20 is better than 21, I'll reply to it

[v20] thermal: add new test group
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/

[v21] thermal: add new test group
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/

Kind regards,
Petr

Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
#6 lore raw
In reply to Cyril Hrubis
Quoted 11 lines · Cyril Hrubis

Hi!
Given that we have a SUSE Labs konference in the week starting 18. May I would like to start LTP May release preparations a bit sooner.

I would like to do the usual patch review that decides what goes into the release during the first two weeks of May. Followed by the pre-release freeze starting at the 18. May and final release at the end of the Month.

If there are any patches that should be considered to be included before the release, please reply to this email.

Hi,
I have one pending bugfix which I'd like to have merged into the new release:
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/

Signature · 10 lines
Martin Doucha   [email protected]
SW Quality Engineer
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp
#7 lore raw
In reply to Cyril Hrubis

I have manually built and tested the main branch locally, everything looks good. (c10s, x86_64, vm)

Hopefully this gives more confidence in the release.

Signature · 5 lines
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp
#8 lore raw

Hi!

Quoted 4 lines

I have manually built and tested the main branch locally, everything looks good. (c10s, x86_64, vm)

Hopefully this gives more confidence in the release.

Thanks!

I've chased down a strange regression that eventually turned out not to be a regression but is likely worth fixing before the release anyways:

https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/

Signature · 5 lines
Cyril Hrubis
[email protected]

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp