LTP Release
Hi!
As usuall it's time to start to prepare for a new LTP release.
My plan is to try to merge as much as possible in the first half of the next week then to drop offline util the new year passes. Once I get back we should start to concentrate on the release procedure.
Feel free to start pointing out which patches you think should be merged before the release now, I will try to do the review ASAP.
And lastly but not least Merry Christmas and a Happy New Year for everyone who will celebrate them!
Signature · 2 lines
Cyril Hrubis [email protected]
Hi Cyril, Alexey,
...
Quoted 2 lines
Feel free to start pointing out which patches you think should be merged before the release now, I will try to do the review ASAP.
I'd like to get merged my patchset "DHCP tests and AppArmor/SELinux improvements" [1] [2].
Quoted 2 lines
And lastly but not least Merry Christmas and a Happy New Year for everyone who will celebrate them!
For you as well.
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/project/ltp/list/?series=82472&state=*
[2] http://lists.linux.it/pipermail/ltp/2018-December/010327.html
Hi!
Quoted 2 lines
Feel free to start pointing out which patches you think should be merged before the release now, I will try to do the review ASAP.
This is gentle reminder to point out important fixes that should be part of the upcomming release.
Signature · 2 lines
Cyril Hrubis [email protected]
Hi!
In order to proceed I would like to declare git freeze starting next week and ask everyone for round of pre-release testing.
As for patches that should be included in the release I would like to include fixes for:
* http://patchwork.ozlabs.org/patch/1020662/
* https://github.com/linux-test-project/ltp/pull/444
Anything else I should look into?
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 11 lines · Cyril Hrubis
Hi!
In order to proceed I would like to declare git freeze starting next week and ask everyone for round of pre-release testing.As for patches that should be included in the release I would like to include fixes for:
* http://patchwork.ozlabs.org/patch/1020662/
* https://github.com/linux-test-project/ltp/pull/444Anything else I should look into?
Hi Cyril,
Can you try to review and push my patch set[1] fixing issue #408?
[1] http://patchwork.ozlabs.org/patch/1011665/
http://patchwork.ozlabs.org/patch/1011667/ http://patchwork.ozlabs.org/patch/1011666/
Best Regards,
Xiao Yang
Hi!
I've commited last patch that I found worth to be included in the release. With that I would like to tag the release early next week.
In other words now is your last chance to test the latest head and report regressions and unexpected failures that happened to slip in.
Signature · 2 lines
Cyril Hrubis [email protected]
Hi
Quoted 7 lines · Cyril Hrubis
Hi!
I've commited last patch that I found worth to be included in the release. With that I would like to tag the release early next week.In other words now is your last chance to test the latest head and report regressions and unexpected failures that happened to slip in.
I've just tested the tip of release candidate and spotted a regression on cgroup (since test_5 failure was exactly what a previous patch of mine should have fixed a few weeks ago :D)
It has been introduced probably by a typo while cleaning up the final commit for:
commit 3cac1f80d87fe7f1a6631034b82683666c80fc00
Author: Cristian Marussi <[email protected]> Date: Fri Dec 21 18:25:16 2018 +0000
cgroup: cgroup_regression_test.sh ported to newlib
This is the fix, which I've just pushed to the ML:
http://lists.linux.it/pipermail/ltp/2019-January/010518.html
if you could pick it up in time for release next week
Thanks
Regards
Cristian
Hi Cyril,
Quoted 3 lines
This is the fix, which I've just pushed to the ML:
http://lists.linux.it/pipermail/ltp/2019-January/010518.html
if you could pick it up in time for release next week
FYI: Already merged.
Kind regards,
Petr