Nested TAP 13 output

[Shuah Khan <shuahkh@xxxxxxxxxxxxxxx>]

Hi Tim,

As I am converting tests to TAP13, I am encountering cases where
a test invokes other tests. For example, say test1 invokes test2
and test3, the output will have nested TAP 13 headers and footers.

Example:

TAP version 13

test1 output

    TAP version 13
    test2 output
    1..1

    TAP version 13
    test3 output
    1..1

1..1


This is the case with timers tests. Some tests invoke 3 to 4 tests.
As these tests can be run independently, they all will need to be
converted. So we can't avoid nested TAP headers and footers.

Do you see any problems with nesting?

thanks,
-- Shuah

-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@xxxxxxxxxxxxxxx
--
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