Re: [sched] d50dde5a1: LTP sched_setparam* TFAILs

[Fengguang Wu <fengguang.wu@intel.com>]

On Wed, Jan 15, 2014 at 02:09:38PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 15, 2014 at 08:47:39PM +0800, Fengguang Wu wrote:
> > Hi Dario,
> > 
> > We notice the below LTP failures since commit d50dde5a1 ("sched: Add
> > new scheduler syscalls to support an extended scheduling parameters
> > ABI") in tip tree's sched/core branch:
> > 
> > ltp.sched_setparam02.1.TFAIL
> > ltp.sched_setparam02.2.TFAIL
> > ltp.sched_setparam02.3.TFAIL
> > ltp.sched_setparam03.1.TFAIL
> > 
> > It seems that the LKP test failures are somehow expected due to the
> > change of ABI. However it does mean that these test cases will need to
> > be updated.
> 
> So with LTP from https://github.com/linux-test-project/ltp.git
> and a tip/master build, I get:
> 
> root@westmere:/usr/local/src/ltp/testcases/kernel/syscalls/sched_setscheduler# ./sched_setscheduler01 
> sched_setscheduler01    1  TPASS  :  expected failure - errno = 3 : No such process
> sched_setscheduler01    2  TPASS  :  expected failure - errno = 22 : Invalid argument
> sched_setscheduler01    3  TPASS  :  expected failure - errno = 14 : Bad address
> sched_setscheduler01    4  TPASS  :  expected failure - errno = 22 : Invalid argument
> root@westmere:/usr/local/src/ltp/testcases/kernel/syscalls/sched_setscheduler# ./sched_setscheduler02 
> sched_setscheduler02    1  TPASS  :  got EPERM

It's sched_setparam02 that TFAIL, not sched_setscheduler02. :)

Thanks,
Fengguang