On Mon, Sep 18, 2017 at 2:27 PM, Greg KH gregkh@google.com wrote:
On Mon, Sep 18, 2017 at 11:02:57AM -0700, Todd Kjos wrote:
All that said, as I recall in the past, there had been discussion on CTS tests to run. Looking at it from a strategic point of view, do we want to go forward with running a full CTS as part of LKFT or is the current subset what we want to use for LKFT going forward?
Thoughts?
To me the value in running CTS is just to give downstream partners confidence that there is no regression in android due to changes in the kernel -- however, I don't think CTS really exercises the kernel in a meaningful way, so a thoughtfully selected subset is fine. Again, if we have capacity, it would be nice to test as much as possible.
I think there are binder tests in CTS that are not in VTS that would be great to see run, to ensure that the recent backports are all working properly. And I think that there are some kernel security checks burried somewhere in CTS as well, although it might be good to sort that all out and move all kernel tests to VTS one day.
But testing binder would be good to see happen, that is not in LTP or kselftest at the moment.
Thanks for the feedback. I added them to our backlog of tests to tackle.
Cheers! anmar