LTP Release
Hi!
Are there any pending issues/patches that should be solved/applied before the release?
I would like to get merged the fix for isofs testcase[1], if nobody objects to it and that would be all from my side.
Can we carry on with the release at the start of the next week?
[1]: [LTP] [PATCH] fs/isofs.sh: Don't use /etc/ for the image
Signature · 2 lines
Cyril Hrubis [email protected]
Hi Cyril,
Quoted 3 lines · Cyril Hrubis
Hi!
Are there any pending issues/patches that should be solved/applied before the release?
How about the following patch set? are there any possible to handle them before the release time?
http://lists.linux.it/pipermail/ltp/2016-April/001533.html
Quoted 15 lines
I would like to get merged the fix for isofs testcase[1], if nobody objects to it and that would be all from my side.
Can we carry on with the release at the start of the next week?
[1]: [LTP] [PATCH]
fs/isofs.sh: Don't use/etc/for the image--
Cyril Hrubis
[email protected]--
Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 3 lines
Regards, Li Wang Email: [email protected]
Quoted 11 lines · Li Wang
Hi Cyril,
Quoted 3 lines · Cyril Hrubis
Hi!
Are there any pending issues/patches that should be solved/applied before the release?How about the following patch set? are there any possible to handle them before the release time?
sorry, and a small one:
http://lists.linux.it/pipermail/ltp/2016-April/001529.html
Quoted 23 lines
Quoted 8 lines
I would like to get merged the fix for isofs testcase[1], if nobody objects to it and that would be all from my side.
Can we carry on with the release at the start of the next week?
Quoted 8 lines
[1]: [LTP] [PATCH]
fs/isofs.sh: Don't use/etc/for the image--
Cyril Hrubis
[email protected]--
Mailing list info: https://lists.linux.it/listinfo/ltp--
Regards,
Li Wang
Email: [email protected]
Signature · 3 lines
Regards, Li Wang Email: [email protected]
Hi!
Quoted 2 lines
sorry, and a small one:
http://lists.linux.it/pipermail/ltp/2016-April/001529.html
This does not seem do any visible change, therefore I would say that it can wait after the release.
Or do I miss something?
Signature · 2 lines
Cyril Hrubis [email protected]
Hi!
Quoted 7 lines
Quoted 2 lines
Are there any pending issues/patches that should be solved/applied before the release?
How about the following patch set? are there any possible to handle them before the release time?
Is not executed in default_scenario so the risk of changing it just before the release is low. I suppose that the testcases does not work correctly without these changes, right?
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 4 lines · Cyril Hrubis
Hi!
Quoted 3 lines
Quoted 2 lines
Are there any pending issues/patches that should be solved/applied before the release?
Quoted 8 lines
Quoted 4 lines
How about the following patch set? are there any possible to handle them before the release time?
Is not executed in
default_scenarioso the risk of changing it just before the release is low. I suppose that the testcases does not work correctly without these changes, right?
yes, right. I'm OK to skip these fix for current LTP released.
and the other simple one as well.
Quoted 4 lines
Signature · 3 lines
-- Cyril Hrubis [email protected]
Hi!
I've just pushed last two patches, the fix for isofs and one obvious fix for netns_netlink.c that causes the test exit with reasonable error rather than fail silently in recv().
I do not want to delay the release anymore, since we are quite late anyway. Is there something that absolutely must be part of the release or can I proceed with the release procedure tomorrow?
Signature · 2 lines
Cyril Hrubis [email protected]
Hi!
Quoted 3 lines
I've just pushed last two patches, the fix for isofs and one obvious fix for
netns_netlink.cthat causes the test exit with reasonable error rather than fail silently
^ in system() then later fail in recv()
Signature · 2 lines
Cyril Hrubis [email protected]