On 06/13/2017 06:50 AM, Greg KH wrote: > On Tue, Jun 13, 2017 at 08:38:28PM +0800, Fengguang Wu wrote: >>> p.s. I have noticed: Documentation/kselftest.txt, but it says nothing >>> about output format used/required program exit codes. >> >> That could be trouble for auto test runners. It'd be great if there is >> a standard on exit codes and a set of common output patterns that the >> output parser can rely on. So that when new tests are added, the >> output parsing will just work in various test infrastructures. > > We are working on unifying this to follow the TAP13 standard. See > recent patches on the kselftest mailing list for progress toward that > goal. > This is great. We have lots of tests now in the suite and it is becoming difficult to identify differences from run to run. I am glad this effort is in progress. My thanks to Greg KH and Tim Bird for getting this started. Once the TAP infrastructure patches go in, I am going to require all new tests to use it and be compliant before accepting them, with the goal towards all tests are TAP compliant by the next release or two. thanks, -- Shuah -- To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
