Hi! > > > Hummm, wondering how LTP sched tests could trigger this, since a quick > > > grep into ltp didn't show DEADLINE usage. > > > > See kernel/syscalls/sched_setattr/sched_setattr01.c > > Right, saw that. I was still thinking though why the report seemed to > point to sched, and not syscalls, tests.
These collections of tests have sometimes non empty intersections. In this case the particular test is both part of the sched and syscall testruns (grep sched_setattr01 runtest/*). So I suppose that the test fails both in the sched and syscall run but the sched one was simply picked first here. > Thanks for pointing this out. Glad to help :-). -- Cyril Hrubis chru...@suse.cz