LTP release
Hi!
It's about the time to start preparing for the LTP January release. Well we should have started at least a week ago, but my family was sick and nobody else seemd to start to work on that...
Anyways let's start with listing patches that should be considered for the release, looking at patchwork the queueu is nice and short so I suppose there will not be many and that we can start with pre-release testing now and do a git freeze at the start of the next week. Does that sound reasonable?
Also are there any volunteers for picking up various release tasks?
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Hello,
Quoted 5 lines · Cyril Hrubis
Hi!
It's about the time to start preparing for the LTP January release. Well we should have started at least a week ago, but my family was sick and nobody else seemd to start to work on that...
Quoted 11 lines
Anyways let's start with listing patches that should be considered for the release, looking at patchwork the queueu is nice and short so I suppose there will not be many and that we can start with pre-release testing now and do a git freeze at the start of the next week. Does that sound reasonable?
Also are there any volunteers for picking up various release tasks?
Signature · 2 lines
Cyril Hrubis [email protected]
My fix for fcntl36/34 doesn't seem to fully work for fcntl36 on 32bit compat. Hopefully I can fix that before next week.
Signature · 5 lines
Thank you, Richard. -- Mailing list info: https://lists.linux.it/listinfo/ltp
Hi Cyril, Richie, Wei,
Quoted 8 lines
Hello,
Quoted 4 lines · Cyril Hrubis
Hi!
It's about the time to start preparing for the LTP January release. Well we should have started at least a week ago, but my family was sick and nobody else seemd to start to work on that...
Thanks for remembering. Time flies + obviously nobody set any calendar event to remember the release months.
Quoted 5 lines
Quoted 5 lines
Anyways let's start with listing patches that should be considered for the release, looking at patchwork the queueu is nice and short so I suppose there will not be many and that we can start with pre-release testing now and do a git freeze at the start of the next week. Does that sound reasonable?
+1
Quoted 8 lines
Quoted 5 lines
Also are there any volunteers for picking up various release tasks?
Signature · 2 lines
Cyril Hrubis [email protected]My fix for fcntl36/34 doesn't seem to fully work for fcntl36 on 32bit compat. Hopefully I can fix that before next week.
+1, thanks for working on it.
I'd like to fix tst_rhost_run.sh failing.
@Wei do you plan to fix it or shell I have look into it?
BTW the move of testcases/kernel/containers/share/ content to testcases/lib which I suggested and we got Cyril's ack [1] is trivial, but as it's just a make dependency fix, it can wait after the release. The test failure is what matters more.
Kind regards,
Petr
[1] https://lore.kernel.org/ltp/Y8UubJZcN89y77AA@yuki/
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 28 lines · Petr Vorel
Hi Cyril, Richie, Wei,
Quoted 8 lines
Hello,
Quoted 4 lines · Cyril Hrubis
Hi!
It's about the time to start preparing for the LTP January release. Well we should have started at least a week ago, but my family was sick and nobody else seemd to start to work on that...Thanks for remembering. Time flies + obviously nobody set any calendar event to remember the release months.
Quoted 5 lines
Quoted 5 lines
Anyways let's start with listing patches that should be considered for the release, looking at patchwork the queueu is nice and short so I suppose there will not be many and that we can start with pre-release testing now and do a git freeze at the start of the next week. Does that sound reasonable?
+1
Quoted 5 lines
Quoted 5 lines
Also are there any volunteers for picking up various release tasks?
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 7 lines
Quoted 2 lines
My fix for fcntl36/34 doesn't seem to fully work for fcntl36 on 32bit compat. Hopefully I can fix that before next week.
+1, thanks for working on it.
I'd like to fix
tst_rhost_run.shfailing.
@Wei do you plan to fix it or shell I have look into it?
@Petr
I create following new patch today help fix tst_rhost_run.sh fail
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
Also i suggest also merge old PATH patch together then at least we can run single test case currently.
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
Info me if any further action i need take, thanks : )
Quoted 10 lines
BTW the move of testcases/kernel/containers/share/ content to testcases/lib which I suggested and we got Cyril's ack [1] is trivial, but as it's just a make dependency fix, it can wait after the release. The test failure is what matters more.
Kind regards,
Petr
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 37 lines · Petr Vorel
Quoted 28 lines
Hi Cyril, Richie, Wei,
Quoted 8 lines
Hello,
Quoted 4 lines · Cyril Hrubis
Hi!
It's about the time to start preparing for the LTP January release. Well we should have started at least a week ago, but my family was sick and nobody else seemd to start to work on that...Thanks for remembering. Time flies + obviously nobody set any calendar event to remember the release months.
Quoted 5 lines
Quoted 5 lines
Anyways let's start with listing patches that should be considered for the release, looking at patchwork the queueu is nice and short so I suppose there will not be many and that we can start with pre-release testing now and do a git freeze at the start of the next week. Does that sound reasonable?
+1
Quoted 5 lines
Quoted 5 lines
Also are there any volunteers for picking up various release tasks?
Signature · 2 lines
Cyril Hrubis [email protected]Quoted 7 lines
Quoted 2 lines
My fix for fcntl36/34 doesn't seem to fully work for fcntl36 on 32bit compat. Hopefully I can fix that before next week.
+1, thanks for working on it.
I'd like to fix
tst_rhost_run.shfailing.
@Wei do you plan to fix it or shell I have look into it?
Quoted 7 lines
@Petr
I create following new patch today help fix
tst_rhost_run.shfail
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/Also i suggest also merge old PATH patch together then at least we can run single test case currently.
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
I'll reply to the patches.
Kind regards,
Petr
Quoted 12 lines
Info me if any further action i need take, thanks : )
Quoted 9 lines
BTW the move of testcases/kernel/containers/share/ content to testcases/lib which I suggested and we got Cyril's ack [1] is trivial, but as it's just a make dependency fix, it can wait after the release. The test failure is what matters more.
Kind regards,
Petr
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Hello,
Quoted 15 lines · Richard Palethorpe
Hello,
Quoted 11 lines · Cyril Hrubis
Hi!
It's about the time to start preparing for the LTP January release. Well we should have started at least a week ago, but my family was sick and nobody else seemd to start to work on that...Anyways let's start with listing patches that should be considered for the release, looking at patchwork the queueu is nice and short so I suppose there will not be many and that we can start with pre-release testing now and do a git freeze at the start of the next week. Does that sound reasonable?
Quoted 8 lines
Quoted 5 lines
Also are there any volunteers for picking up various release tasks?
Signature · 2 lines
Cyril Hrubis [email protected]My fix for fcntl36/34 doesn't seem to fully work for fcntl36 on 32bit compat. Hopefully I can fix that before next week.
Actually these tests are fine. The problem is the OpenSUSE package is broken due to the runltp-ng Makefile. So we should fix that instead.
Signature · 5 lines
Thank you, Richard. -- Mailing list info: https://lists.linux.it/listinfo/ltp
Hi!
I did my share of pre-release testing and apart from the statvfs01 I've send a patch for there rest of results looks green.
I also did test the runltp-ng and we fixed a few bugs there in order to have a flawless experince since it will be introduced in the LTP tarball. It would be great if anyone else would do so as well.
And given that the mailing list is mostly silent I suppose, unless anybody objects, that we can freeze the git now and declare the next week as pre-release testing week. With that we would be aiming for the release either at Friday 27.01. or at Monday or Tuesday 29-30.01.
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Hi all,
Quoted 4 lines
Hi!
I did my share of pre-release testing and apart from the statvfs01 I've send a patch for there rest of results looks green.
Quoted 8 lines
I also did test the runltp-ng and we fixed a few bugs there in order to have a flawless experince since it will be introduced in the LTP tarball. It would be great if anyone else would do so as well.
And given that the mailing list is mostly silent I suppose, unless anybody objects, that we can freeze the git now and declare the next week as pre-release testing week. With that we would be aiming for the release either at Friday 27.01. or at Monday or Tuesday 29-30.01.
I'd be for Friday (given there is SUSE hackweek since Monday). I'm going to do build testing for various architectures.
I can help to tag the release and upload files (as I did last release).
But before I'll try to fix nft01.sh -6, which is broken on newest 1.8.9:
nft01 2 TINFO: Use nft to DROP packets from particular IP
nft01 2 TINFO: Rule to block icmp from ::1
nft01 2 TFAIL: nft command failed to append new rule
Error: syntax error, unexpected junk
'add rule ip6 filter INPUT meta l4proto ipv6-icmp ip6 saddr ::1 counter drop'
Kind regards,
Petr
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 19 lines
Hi all,
Quoted 4 lines
Hi!
I did my share of pre-release testing and apart from the statvfs01 I've send a patch for there rest of results looks green.Quoted 8 lines
I also did test the runltp-ng and we fixed a few bugs there in order to have a flawless experince since it will be introduced in the LTP tarball. It would be great if anyone else would do so as well.
And given that the mailing list is mostly silent I suppose, unless anybody objects, that we can freeze the git now and declare the next week as pre-release testing week. With that we would be aiming for the release either at Friday 27.01. or at Monday or Tuesday 29-30.01.
I'd be for Friday (given there is SUSE hackweek since Monday). I'm going to do build testing for various architectures.
I can help to tag the release and upload files (as I did last release).
Quoted 7 lines
But before I'll try to fix
nft01.sh-6, which is broken on newest 1.8.9:nft01 2 TINFO: Use nft to DROP packets from particular IP
nft01 2 TINFO: Rule to block icmp from ::1
nft01 2 TFAIL: nft command failed to append new rule
Error: syntax error, unexpected junk
'add rule ip6 filter INPUT meta l4proto ipv6-icmp ip6 saddr ::1 counter drop'
I'm not sure, but it looks like 83604e7f ("xlate: get rid of escape_quotes") broke the test (not sure, because xtables-nft-multi which I compiled from iptables git, which is a symlink to ip6tables-translate, which is used here always fail, but since 83604e7f the error message is the same as what I see on
openSUSE Tumbleweed iputils v1.8.9).
I'm not really sure what should be changed in this line:
$(ip${TST_IPV6}tables-translate $@ | sed 's,\\,,g')Kind regards,
Petr
Quoted 2 lines
Kind regards,
Petr
[1] https://git.netfilter.org/iptables/commit/?id=83604e7f7327b6b3197f98b4e579a2b88a4c7356
+++ testcases/network/iptables/iptables_lib.sh
@@ -22,7 +22,7 @@ NFRUN()
if [ "$use_iptables" = 1 ]; then
ip${TST_IPV6}tables $@
else
- $(ip${TST_IPV6}tables-translate $@ | sed 's,\\,,g')
+ $(ip${TST_IPV6}tables-translate $@)
fi
}
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp