[Piglit] [PATCH] framework: actually write dmesg to testresult

Dylan Baker baker.dylan.c at gmail.com
Mon Oct 12 12:20:38 PDT 2015

On Mon, Oct 12, 2015 at 09:21:15AM +0200, Daniel Vetter wrote:
> On Sat, Oct 10, 2015 at 01:10:25PM -0700, Dylan Baker wrote:
> > Everything is hooked up, except writing it. Restoring, processing, all
> > of that still works, just not writing it to the json, so fix that.
> > 
> > cc: imirkin at alum.mit.edu
> > Signed-off-by: Dylan Baker <dylanx.c.baker at intel.com>
> Just random thought: By writing into /dev/kmsg you can inject stuff into
> dmesg, which would allow us to test all the dmesg capturing stuff.
> Unfortunately only works as root :( Plan B would be to inject a mocked
> dmesg script into PATH while running dmesg-related tests.
> -Daniel

We actually have tests that do the former. I'm not sure if they work at
the moment, I generally don't run them because I'm really loath to
running the tests as root. Though I suppose now that we're using the
privileged attribute one could run them with 'nosetests framework/tests
-a privileged'. I might have a branch that fixes them.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/piglit/attachments/20151012/b6382d78/attachment.sig>

More information about the Piglit mailing list