I should add, I sent a patch to fix that. On Sat, Oct 10, 2015 at 1:13 PM, Dylan Baker <[email protected]> wrote:
> Yeah, I hooked everything up but actually writing the dmesg output into > the result (the conversion to dmesg-* statuses is currently working). > > And we do need those __type__ things, they're hints to the framework to > tell it how to turn the json back into objects. they get removed when the > json is processed. > > On Sat, Oct 10, 2015 at 12:45 AM, Ilia Mirkin <[email protected]> > wrote: > >> Hey Dylan, >> >> I've noticed that dmesg errors no longer appear -- the tests are still >> qualified as dmesg-fail or whatever, but the actual dmesg is just not >> there. It's not there in the results file, which is probably why it's >> not making its way to the template. Coincidentally, I happened to >> notice the following oddity in the results file: >> >> "time": { >> "start": 1444460713.804859, >> "end": 1444460730.525851, >> "__type__": "TimeAttribute" >> }, >> "subtests": { >> "__type__": "Subtests" >> }, >> "__type__": "TestResult", >> >> Probably don't need those __type__ things. >> >> Any ideas? >> >> -ilia >> > >
_______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
