[08:48] <xnox> I would like to contribute to UTAH, I want to work on installation/reboot testing with unusual filesystem's setup. How do I get started? Where are the current installation tests?
[09:56] <gema> xnox: we are in the process of migrating them, but we haven't really started yet.
[09:57] <xnox> gema: ok. so where are the current ones? are they for jenkins?
[09:57] <xnox> gema: or should I just fiddle/start with UTAH?
[09:57] <xnox> are there any good existing UTAH examples?
[09:57] <gema> xnox: the current ones are here http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/ubuntu-server-iso-testing/trunk/files
[09:58] <gema> xnox: but if I were you I'd start with utah directly, nuclearbob is finishing off the part where you can preseed installation and we are adding automated testing for utah for that to jenkins this week
[09:58] <gema> xnox: so early next week we should be in a good position to start adding that kind of tests
[09:59] <xnox> sounds good to me =)
[09:59] <gema> xnox: you are welcome to work with us on the moving current tests to utah
[09:59] <xnox> we'll see =) if the work overlaps with my goals then sure ;)
[09:59] <gema> xnox: cool, let us know your goals so that we can figure that out
[10:00] <gema> our goals are to have existing smoke testing working with utah
[10:00] <xnox> my goals is to add more smoke tests for raid, lvm, btrfs
[10:01] <xnox> across all affected images
[10:01]  * xnox grammar fail "my goals are"
[10:01] <gema> xnox: ok, so whenever we get to migrate those cases, I will ping you
[10:01] <xnox> =)))))
[10:01] <gema> we should have a clearer view on how to do it properly by then
[10:02] <gema> expect a ping either during this week or early next ;)
[10:02] <gema> xnox: we don't have the capacity to train everyone individually, so we are going to be working with you guys to get all the testing off the ground as we go
[10:04] <xnox> I was hoping I will be able to learn by myself from the migrated scripts and make changes/additions & merge proposals for additional tests
[10:57] <gema> xnox: then you'll have to wait two/three weeks
=== _salem is now known as salem_
=== Ursinha` is now known as Ursinha
=== zyga is now known as zyga-food
=== zyga-food is now known as zyga
=== yofel_ is now known as yofel
=== zyga is now known as zyga-afk
[19:10] <balloons> phillw, you about?
[19:10] <phillw> balloons: yup :)
[19:11] <balloons> did you notice something about http://iso.qa.ubuntu.com/?
[19:12] <phillw> I'm on http://iso.qa.ubuntu.com/qatracker/milestones/219/builds and have not noticed anything?
[19:12] <balloons> http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/17439/testcases/4/results
[19:12] <balloons> look a bit different? :-) Anyways, the new build has landed.
[19:13] <balloons> I was hoping it would land today, and boom.. it's live
[19:13] <stgraber> balloons: told you they wouldn't notice ;)
[19:13] <balloons> stgraber, it's a good thing in many ways!
[19:13] <balloons> so what that means now is we've got to get the help pages revamped for user facing help, and convert the testcases out of the wiki and into the tracker
[19:14] <balloons> which is awesome.. I'm super excitied
[19:14] <balloons>  and while "converting" we get to verify the testcases, and enhance their presentation by putting them all into the templated format, and have them be easy to use
[19:18] <phillw> looks good,  few typos to correct :)
[19:19] <phillw> +a
[19:20] <balloons> Have a look at this: http://packages.qa.dev.stgraber.org/qatracker/milestones/223/builds/16266/testcases/1300/results
[19:20] <balloons> notice we can do things in the "Link to the installation instructions", and "Link to bug reporting instructions"
[19:21] <balloons> also, the testcase is in our templated form, and has a bolierplate on the bottom for quicklinks to record what happened