For some reason I didn't notice this at the end of the message I replied to. This is a much simpler system than the ones I proposed in my brainstorming. You can ignore my overengineered ideas - this one is much better. :-) > -----Original Message----- > From: Shuah Khan [mailto:shuah@xxxxxxxxxx] > Instead of changes to functions or adding a new function, a new > environment > variable to indicate nesting will meet the needs. There is a need to drive > the nesting externally to minimize changes to the tests as well as being > able to use it from run_tests target. > > run_tests target runs all tests in a loop. Shell scripts need coverage and > I added it in run_tests in 4.14-rc1. > > ksft_print_header() could check this env and determine if it has to omit > printing the header based on what Tim pointed out in his earlier response > that in the case of nesting, header is omitted from sub-levels. Did I say that? I think I commented that it's missing in the examples used by the Jenkins TAP plugin. I'm not sure whether it would be good or bad as a general practice to omit the header for nested output. I suppose we could decide. Since the header is on the un-nested output, I can't think of a reason to duplicate it on the nested output. But I can't think of any harm having it there either (unless it freaks out the Jenkins TAP plugin). I'll try to do some testing to see. > Nesting can > be a value 1,2,3 etc. Number of tabs can be derived from this. I think I have > a good idea on what will work. I will get a patch out in a day or two. > > I kind of moved this to my back burner with the make O=dir work. -- Tim ��.n��������+%������w��{.n�����{��K ����n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
