> Still, I think it's good to include these tests. If anything they may > just provide more motivation to address the underlying issue. :-)
Absolutely! I'll start a thread on lttng-dev to see how we can deal with the current testsuite limitations. >>> ++prove --merge -v --exec '' - < $1 | sed \ >>> ++ -e 's|^ok \(.*\)|PASS: \1|' \ >>> ++ -e 's|^not ok \(.*\)|FAIL: \1|' \ >>> ++ | egrep -h 'PASS|FAIL' >> This is sadly needed because we are using TAP as our standardized test >> output format across the multiples lttng codebases. > > Do you think it would be worthwhile submitting this patch upstream ? This is pretty much OpenEmbedded specific and I don't think it is of much use outside of ptest support. > (The output format of prove is not the easiest to understand, and even > with the above some information may be lost. A more robust fix would > probably include a dedicated TAP formatter plugin > (http://perldoc.perl.org/TAP/Formatter/Console.html) that produces > ptest-compatible output. Yes that would be a cleaner way of dealing with it. We would only need to feed the appropriate 'testlist' file to this script and get proper conversion of TAP to Automake-style test output. I'm wondering if such a script would be useful for other projects/recipes using TAP tests within oe/yocto? Thanks, Christian Babeux EfficiOS Inc. http://www.efficios.com _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core