LTP release
Hi!
Just now I'm testing last set of changes for cgroup_fj tests (in the end these were too bugy so I've did a partial rewrite) and once that is done and pushed the release is green from my side. Minus the ROD problem that I've posted earlier but that can be workarounded for the release.
What is the status from the rest of you?
Can we do the release on Monday or Tuesday?
Signature · 2 lines
Cyril Hrubis [email protected]
----- Original Message -----
Quoted 5 lines
From: "Cyril Hrubis" <[email protected]>
To: [email protected]
Sent: Thursday, 21 January, 2016 6:41:02 PM
Subject: [LTP] LTP release
Quoted 7 lines
Hi!
Just now I'm testing last set of changes forcgroup_fjtests (in the end these were too bugy so I've did a partial rewrite) and once that is done and pushed the release is green from my side. Minus the ROD problem that I've posted earlier but that can be workarounded for the release.What is the status from the rest of you?
Hi,
I did compile + run test (with subset of runtest files) on RHEL5.6/RHEL6.2/6.7/7.2 (i386/x86_64/ppc64/s390x), which worked OK with one exception below.
One issue I keep hitting is oom0X hang [1], but since it's there for months we don't need to hold release for that (I don't have any tested patch yet).
What I'm thinking is to introduce a parameter to control how many threads we allow to race towards OOM. At the moment it's NCPU-1, which appears to be too stressful for regular runtest files. It hangs kernels from 3.10 up to 4.4 and there's no fix atm.
[1] http://lists.linux.it/pipermail/ltp/2016-January/000807.html
Quoted 2 lines
Can we do the release on Monday or Tuesday?
Fine by me.
Regards,
Jan
Quoted 8 lines
--
Cyril Hrubis
[email protected]--
Mailing list info: http://lists.linux.it/listinfo/ltp
Hi!
Quoted 7 lines · Cyril Hrubis
Hi!
Just now I'm testing last set of changes forcgroup_fjtests (in the end these were too bugy so I've did a partial rewrite) and once that is done and pushed the release is green from my side. Minus the ROD problem that I've posted earlier but that can be workarounded for the release.What is the status from the rest of you?
I observe several failures in my environment (a sparc64 in-house kernel), but they look like environmental/kernel issues and should not be considered as blockers.
Quoted 3 lines
Can we do the release on Monday or Tuesday?
Fine by me.
Hi,
Quoted 9 lines · Cyril Hrubis
Hi!
Just now I'm testing last set of changes forcgroup_fjtests (in the end these were too bugy so I've did a partial rewrite) and once that is done and pushed the release is green from my side. Minus the ROD problem that I've posted earlier but that can be workarounded for the release.What is the status from the rest of you?
Can we do the release on Monday or Tuesday?
There is fallocate04 test that is failing on UEK1 (kernel 2.6.32). I think we need to apply Shuang's patch that fixes it:
[PATCH] syscall/fallocate04:skip test02 before kernel 2.6.38
fallocate() doesn't return EOPNOTSUPP errno there, but silently proceed with FALLOC_FL_PUNCH_HOLE flag.
Thanks,
Alexey
Hi!
Quoted 7 lines
Quoted 7 lines
Just now I'm testing last set of changes for
cgroup_fjtests (in the end these were too bugy so I've did a partial rewrite) and once that is done and pushed the release is green from my side. Minus the ROD problem that I've posted earlier but that can be workarounded for the release.What is the status from the rest of you?
Quoted 8 lines
Quoted 1 line
Can we do the release on Monday or Tuesday?
There is fallocate04 test that is failing on UEK1 (kernel 2.6.32). I think we need to apply Shuang's patch that fixes it:
[PATCH] syscall/fallocate04:skip test02 before kernel 2.6.38
fallocate()doesn't return EOPNOTSUPP errno there, but silently proceed withFALLOC_FL_PUNCH_HOLEflag.
Ok. I will have a look at the patch.
Signature · 2 lines
Cyril Hrubis [email protected]
Hi!
Quoted 1 line
Can we do the release on Monday or Tuesday?
I've just pushed the cgroup_fj fix. Please have a look at it and ideally run cgroup_fj the tests today, it should take less than hour.
The only two outstanding issues should now be fallocate04 and ROD with redirection. I will have a look at the fallocate04 patch now, then try to do something about the ROD redirection.
If nothing else shows up I will tag the git and do the release tomorrow.
Signature · 2 lines
Cyril Hrubis [email protected]
Hi,
Quoted 10 lines · Cyril Hrubis
Hi!
Quoted 1 line
Can we do the release on Monday or Tuesday?
I've just pushed the
cgroup_fjfix. Please have a look at it and ideally runcgroup_fjthe tests today, it should take less than hour.The only two outstanding issues should now be fallocate04 and ROD with redirection. I will have a look at the fallocate04 patch now, then try to do something about the ROD redirection.
I did a quick ltp/mem[sched] test on RHEL7.2 with upstream-v4.4 kernel, it works fine except one thp05.c fails.
looks like the issue exist so long time with any kernel on x86_64 numa system.I just post a simple patch try to fix that.
Quoted 3 lines
If nothing else shows up I will tag the git and do the release tomorrow.
Fine.
Quoted 8 lines
--
Cyril Hrubis
[email protected]--
Mailing list info: http://lists.linux.it/listinfo/ltp
Signature · 6 lines
Regards, Li Wang Email: [email protected] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20160126/99982a58/attachment.html>
Quoted 5 lines · Cyril Hrubis
Hi!
Quoted 1 line
Can we do the release on Monday or Tuesday?
I've just pushed the
cgroup_fjfix. Please have a look at it and ideally runcgroup_fjthe tests today, it should take less than hour.
Executed cgroup_fj with an in-house sparc64 kernel - they all passed, and the current 4.1-based kernel in Linux for SPARC - the stress tests cause a panic (but it's a known not-yet-fixed issue in the kernel).
Quoted 7 lines
The only two outstanding issues should now be fallocate04 and ROD with redirection. I will have a look at the fallocate04 patch now, then try to do something about the ROD redirection.
If nothing else shows up I will tag the git and do the release tomorrow.