[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [OSSTEST PATCH v11 16/20] ts-openstack-tempest: Update list of skipped tests
On Fri, Jun 30, 2017 at 06:58:43PM +0100, Anthony PERARD wrote: > On Fri, Jun 30, 2017 at 05:32:56PM +0100, Ian Jackson wrote: > > Anthony PERARD writes ("Re: [OSSTEST PATCH v11 16/20] ts-openstack-tempest: > > Update list of skipped tests"): > > > But it can be told to print subunit v2, which can be pipped to a different > > > program to transform into want we want, including simple cvs, subunit v1, > > > and > > > other. > > > > > > I thing we could try to parse subunit v1, grab the start and finish time > > > of a test, the result, and the output of the tests. And have all that as > > > subunit. During my manual tests, `tempest run --subunit ... | > > > subunit-2to1` > > > only print the stuff about a tests once it is finish, so I guess we'll > > > have to rewrite substep_start() (or another function) to take time as > > > parameter. > > > > That sounds quite good really. > > > > I guess you don't want to write a parser for subunit v2 but if there > > is one in Perl already in some package in Debian we could use it. Or > > subunit-2to1 is fine. > > There is one, libsubunit-perl, but its only for subunit v1 :-(. So I > guess I'll use both, the package and subunit-2to1. :( the package does not work with the output of `Tempest | subunit-2to1` there are a few things that are not parsed properly. That the parser: https://github.com/testing-cabal/subunit/blob/master/perl/lib/Subunit.pm I'm kind of tempted to write one that's will be easier to integrate with Osstest, especially because subunit v1 is simple enough. -- Anthony PERARD _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |