GitHub PushEvent at 2014-02-01 01:02:44
Repository: piglit
Actor: dcbaker
Payload: {"shas":[["fd3ea54b9b9e606ba2ea913735731d77f21b597c","91de990240e6abc00928035c476e6ad54ab72b92@gmail.com","framework/dmesg: Adds a new module for dmesg\n\nThis modules implements two classes and a helper function. The two\nclasses are both dmesg wrapper classes, one, PosixDmesg is used on posix\nsystems when requested to actually do checks on dmesg. The second class,\nDummyDmesg, is used to reduce code complexity by providing dummy\nversions of the methods in PosixDmesg. This means that we don't need\nseperate code paths for Posix systems wanting to check dmesg, Posix\nsystems not wanting to check dmesg, and non-posix systems which lack\ndmesg.\n\nBeyond reducing complexity this module also gives better isolation,\ndmesg is only used in Test.execute(), no where else. Additional classes\ndon't need to worry about dmesg that way, it's just available. The third\nadvantage is performance, this module doesn't search for timestamps and\ncompare from there, instead it creates snapshots of dmesg as lists, and\ndoes a linear comparison between them.\n\nSigned-off-by: Dylan Baker <baker.dylan.c@gmail.com>","Dylan Baker",true],["ff6cd5be9f23587d9bcb9fbea0e9687270348bb5","91de990240e6abc00928035c476e6ad54ab72b92@gmail.com","Adds unittests for the dmesg class\n\nThis adds a few tests for the dmesg class.\n\nIt also adds a test hook into core.Test. This is a little ugly, but I\njust couldn't come up with any other solution that didn't involve\nmaking the dmesg code more invasive or harder to read.\n\nSigned-off-by: Dylan Baker <baker.dylan.c@gmail.com>","Dylan Baker",true],["2a3d7572cb36047e7fb6d6142e6f1105fc2ad016","91de990240e6abc00928035c476e6ad54ab72b92@gmail.com","Use the new dmesg class\n\nThis actually makes use of the new dmesg class rather than the dmesg\nfunctions. It touches a lot of files, but almost all of these changes\nare code removal rather than code addition.\n\nSigned-off-by: Dylan Baker <baker.dylan.c@gmail.com>","Dylan Baker",true],["db495e51dcce67162392136b921ee772f20f2305","91de990240e6abc00928035c476e6ad54ab72b92@gmail.com","piglit-run.py: Restrict dmesg to serial runs\n\nDmesg reporting has always been inaccurate with concurrent runs, and the\nsolution to concurrent runs would be to have each run take out a lock,\nremoving the chance that another test generated an error in dmesg while\nit was running. But this effectively makes them a serial run, and at the\ncost of greater code complexity. With that in mind it makes more sense\nto just force --dmesg to imply -1.\n\nSigned-off-by: Dylan Baker <baker.dylan.c@gmail.com>","Dylan Baker",true]],"size":4,"ref":"refs/heads/dmesg-v2","head":"db495e51dcce67162392136b921ee772f20f2305"}