[11:17] <xnox> jibel and DanChapman added to the team to solely maintain / have commit access to the autopilot ubiquity tests which are now in lp:ubiquity & jenkins tests running in the lab against all/most gtk based ISOs.
[11:20] <cjwatson> ack
[15:04] <superm1> xnox: where are results for these autopilot tests publishing?
[15:05] <xnox> superm1: https://jenkins.qa.ubuntu.com/view/Trusty/view/All/search/?q=ubiquity_ap&max=40
[15:06] <superm1> thanks!
[15:06] <xnox> superm1: we don't have oem-config auto-pilot test yet ;-)
[15:06] <xnox> superm1: but there is a way to "watch" the clicks/installation when run manualy and to record the install with recordmydesktop. But it looks like we stopped recording the desktop (or publishing the movies)
[15:08] <superm1> ah cool.  i'm sure stack traces are pretty useful in their own though when this finds problems
[15:10] <jibel> recordmydesktop generated huge videos that crashed the test because it writes frames to /tmp which is small during installation.
[15:10] <jibel> then encoding takes twice the time of installation
[15:12] <xnox> jibel: on debian install tests only screenshots are taken e.g. every N seconds or so, and then compreseed together into a video. I wonder if one can trigger the screenshot in autopilot? cause to be honest we only really want screenshot per page.
[15:13] <superm1> are all of these autopilot tests dependent upon having all the ubiquity plugins in tree as well?
[15:13] <xnox> (also that will save me from making screenshots manually from time to time at https://wiki.ubuntu.com/Ubiquity/SlideDecks )
[15:14] <xnox> superm1: at the moment autopilot tests do assume certain order of the plugins. But the top-level test is quite generic and specifies the expected order of pages. It should be easy to extend/modify to run against customized ubiquity.
[15:14] <xnox> look at trunk/autopilot/ubiquity_autopilot_tests/tests
[15:16] <jibel> xnox, I'll ask thomi, but I'm pretty sure AP cannot trigger screenshots. I'll see how to add it. Taking a screenshot when an assertion or a test fails would be useful
[15:17] <xnox> jibel: well, i can always do subprocess call to do gnome-screenshot ;-)
[15:18] <xnox> but yeah something Autopilotish would be nice.
[15:19] <superm1> all looks pretty neat.  i might have to mess with trying to extend this at some point
[19:13] <antarus> is there a guide for signed booting?
[19:13] <antarus> I see people working on the shim ;p
[19:14] <xnox> antarus: there is the test guide written by security team:
[19:14] <xnox> https://wiki.ubuntu.com/SecurityTeam/SecureBoot
[19:15] <xnox> not sure there is anything specific about "working on the shim"
[19:15] <antarus> haha
[19:15] <antarus> sorry, I just saw some commits to it
[19:15] <antarus> and I was pondering what features we could try to do in trusty
[19:15] <antarus> at work
[19:16] <antarus> and we are considering switching to the Ubuntu kernel anyway
[19:16] <antarus> so if it was easy to do, then we might just do it
[19:17] <xnox> last commit to shim is from september. we do SRU it back to precise. but that's about it. shim work is all/mostly done upstream.
[19:18] <antarus> the doc was helpful in any case, tanks ;)
[19:18] <antarus> er thanks*