Tap output from runtime test

[mrunalp]

This gets us to this output:

-----------------------------------------------------------------------------------
VALIDATING RUNTIME: runc
-----------------------------------------------------------------------------------
TAP version 13
ok 1 - root filesystem
ok 2 - hostname
ok 3 - mounts
ok 4 - capabilities
ok 5 - default symlinks
ok 6 - default file system
ok 7 - default devices
ok 8 - linux devices
ok 9 - linux process
ok 10 - masked paths
ok 11 - oom score adj
ok 12 - read only paths
ok 13 - rlimits
ok 14 - sysctls
ok 15 - uid mappings
ok 16 - gid mappings
Runtime runc passed validation

@hqhq @Mashimiao @wking @liangchenye PTAL

[mrunalp]

@RobDolinMS I think this will help us to easily add link to anchors. We can just add another field to the validation struct as a pointer to an anchor in the spec that is being tested.

[Mashimiao]

That looks like what I have done in d76bbd7e28600f005

[wking]

On Tue, Jan 10, 2017 at 06:20:22PM -0800, Ma Shimiao wrote: That looks like what I have done in [d76bbd7](d76bbd7)

But TAP is a standardized format, and it's nice to not have to roll our own [1]. And in #285, d76bbd7 was tied up with the change from #232 that broke test_runtime.sh's exit code (as far as I know, nobody has written the subreaper wrapper needed to make that work [2]). I've filed mrunalp/runtime-tools#1 with a more granular take on this PR (to get squashed in if it looks useful). That PR also uses prove (a TAP harness) so we get an appropriate exit code from test_runtime.sh. It's still using ‘start’ (where modern runC's use ‘run’), but I'm leaving the subreaper wrapper and create/start split for somebody else to handle ;). [1]: #285 (comment) [2]: #232 (comment)

[Mashimiao]

LGTM

[liangchenye]

LGTM

[liangchenye]

This frame is much smaller than ginkgo.