[06:50] <jibel> good morning
[11:47] <DanChapman> Wow! saucy is not liking me today, keep crashing Xorg :S
[14:19] <balloons> DanChapman, let's see if autopilot is unbroken today.. or if I too have to rollback
[14:29] <DanChapman> balloons, mine is fine today after updates so fingers crossed for you :)
[14:39] <balloons> ok third times the charm
[14:41] <DanChapman> balloons, i ran fileroller on a very small vm to test that hack held up ok, and it worked fine
[14:42] <balloons> perfect works fine as expected
[14:42] <balloons> and autopilot too :-)
[14:42] <DanChapman> :-)
[14:44] <balloons> it's in :-)
[14:44] <balloons> so what happened with evince?
[14:45] <DanChapman> Ive started it again as the new UI means we can have better introspection. Will have a new branch there soon :D
[14:45] <balloons> ohh really? that's exciting!
[14:46] <balloons> changes that help make our lives easier :-)
[14:47] <DanChapman> Indeed they do :D they were considerate and put a nice little settings button in the window and done away with the global menu's  :)
[14:48] <DanChapman> saucy is giving me a hard time today though, keep crashing xorg :(
[14:50] <DanChapman> balloons with the 'current' evince test it has a test full screen opens test and a seperate full screen closes test. Would it not be better to put it into one?
[14:50] <DanChapman> check it opens then check it closes again
[14:52] <balloons> DanChapman, lol, yes I would place them into one :-)
[14:52] <DanChapman> sweet :D i never understood why they were seperate
[14:57] <balloons> DanChapman, don't ever be afraid to change things up if they don't make sense :-) Likely you'll find people will appreciate the change. At worst it's simply is picked up in the merge request review
[14:58] <balloons> your going to have a moment where you go back to add something to a previous test and change your own old code :-)
[14:58] <balloons> those are fun moments.. you get a what the? moment and realize you wrote it
[14:59] <DanChapman> lol yeah those are great moments
[15:23] <balloons> xnox, if your about -- you got ubiquity and autopilot working eh? :-) I want to see!
[15:26] <xnox> balloons: i did =)
[15:26] <balloons> <3
[15:30] <DanChapman> ooo that sounds interesting balloons :D
[15:31] <balloons> xnox, so when/if your ready can you share a branch for us to look at or hack on?
[15:31] <balloons> ohh.. I see the branch now in your mail, sorry :-)
[15:31] <xnox> balloons: indeed. =)
[15:34] <balloons> xnox, so I wonder if we can use otto to provision this and run these tests.. jibel ?
[15:35] <xnox> balloons: what's "otto"? utah? well at the moment the only tests there is, checks the "title" of the window =)
[15:36] <DanChapman> this is going to drive me nuts!!
[15:37] <balloons> xnox, sure.. otto is a tool jibel made that uses an image to provision a lxc container.. https://launchpad.net/otto
[15:38] <balloons> not sure if testing the actual installer bits can work in it, but ..
[15:38] <xnox> balloons: not sure that would work for ubiquity, as it needs raw access to disk drive devices nodes e.g. /dev/sda
[15:38] <balloons> indeed :-)
[15:38] <balloons> but doing vm provisioning will certainly work
[15:42] <jibel> xnox, otto is the tool we made with didrocks to replace utah for autopilot testing. We are deploying it for daily release testing http://10.97.0.1:8080/job/autopilot-raring-daily_release/label=autopilot-nvidia/ (don't worry about failures, we are testing that it fails as expected =))
[15:44] <balloons> jibel, do you think it would work for something as low level as ubiquity.. could you passthrough or emulate a disk?
[15:46] <jibel> balloons, we could certainly create fake block devices
[15:46] <jibel> balloons, I'd rather not use the disks of the host system, since there is only one on the machines in the lab :)
[15:46] <balloons> jibel, ohh trust me, I agree :-)
[15:48] <balloons> xnox, so I think I'll hack on this a bit and try and get a full test done for a basic auto-resize install
[15:48] <xnox> balloons: good luck =) hit me up, if there are any questions.
[15:49] <balloons> thanks.. and thank you for making this work.. this is exciting!
[16:49] <phillw> balloons: you about?
[16:50] <balloons> phillw, halfway