=== bladernr_ is now known as bladernr_afk === _salem is now known as salem_ [14:48] jamespage: hey, so I'd like to hook up an automated run of lp:~serge-hallyn/+junk/lxc-test [14:49] * jamespage looking [14:50] it ain't purty, but catches bugs [14:52] hallyn: so can it run in a KVM instance? [14:52] or does it need to run on bare-metal? === kalosaurusrex is now known as albrigha [15:02] yup, it can run in kvm instance [15:17] hallyn: sorry thinking about this - its not quite like anything else we already have automated [15:18] jamespage: is there a url showing me how to make it more like the tests you have automated? [15:19] jamespage: would the libvirt tests in lp:qa-regression-testing fit better? [15:19] hallyn, not sure TBH [15:22] hallyn: so we could make it a set of tests off the end of an install test [15:22] like we do for lamp [15:22] automated install of ISO with required packages and then execute your test. [15:24] they run as root [15:24] so that would be OK [15:27] jamespage: that'd be great [15:29] hallyn: OK so can you take a look at bzr branch lp:~ubuntu-server-iso-testing-dev/+junk/server-tests-precise [15:30] this is really a new test_case (see subdirectories) [15:30] at the moment the tests that are run in each test case are python unittests [15:31] which means we can grab the results and display in jenkins [15:31] they must all be in a file called 'test' in the test_case directory [15:31] you can handle some of the package install stuff using the preseed - see one of the other test cases for an example === Ursinha is now known as Ursinha-lunch [15:36] hallyn: do you think that you can refactor what you have into that framework? [15:37] we can get it up and running for precise hoepfully [15:38] absolutely - well, in time for precise will depend, but it can definately be refactored like that [15:38] jamespage: thanks [15:39] hallyn: I say for precise because I know the QA team are going to be working on a new test framework for delivery early next cycle [15:43] hallyn, if you can provide a test that is an executable and its output is junit xml then its good. [15:43] For precise we should be able to hack something into the existing tool like we did for software-center. [15:47] (*$&%(*$&% xml *$&%*($&% ) [15:48] so to be clear, if i refactor it like this now, i'll have to do it again for p+1? [15:48] if so, it may be a better use of my time to run the testsuite by hand and refactor for p+1 [15:49] no, you wont because we'll use the same output format for p+1 [15:49] ah, ok [15:50] thanks guys, made some notes, will looka t this after ff [15:52] hallyn, did you still need me to run the lxc test on arm? I think you asked me to hold on the other day? [15:59] rbasak: yeah that'd be great [16:06] jamespage, could you help verifying bug 708548 and bug 810068 in lucid ? I've no iscsi setup [16:06] Launchpad bug 708548 in kickseed (Ubuntu Natty) (and 3 other projects) "kickstart not removing logical volume data (affects: 1) (heat: 11)" [Medium,Fix committed] https://launchpad.net/bugs/708548 [16:06] Launchpad bug 810068 in partman-iscsi (Ubuntu Natty) (and 7 other projects) "kickstart iscsi option broken (affects: 2) (heat: 16)" [High,Fix committed] https://launchpad.net/bugs/810068 [16:11] jibel: hmm - I might not have either - had a slight accident - let me see [16:14] jibel: I think I can resurrect it but do we have any example kickstarts for testing this? [16:18] jamespage, I thought there was one attached to the report, but apparently not :/ [16:18] jibel: may make it a little difficult [16:18] indeed === Ursinha-lunch is now known as Ursinha [16:45] jamespage, and could you test a "default" preseeded iscsi install ? do you have a preseed for that ? [16:45] jibel: I don't have preseeds for any type of iscsi install [16:46] jamespage, you should fix that :) [16:46] jibel: sorry - not trying to be difficult [16:46] thats happening all by itself! [16:47] jibel: I can easily setup a rig to let me do manual iscsi installs; still have scripts [16:51] weekly qa meeting in #ubuntu-meeting in 10 mins :-) [17:02] hallyn: lxc-test.sh seems to be trying to download armhf oneiric which doesn't exist [17:02] I had another weird error as well, so I'm reinstalling to see if it happens again [17:05] jibel: when do these need to be verified by? [17:05] I know i should know.... [17:06] jamespage, should have been done already, but no later than tomorrow [17:06] if we want them in 10.04.4 images [17:06] jibel: right - I see [17:07] jibel: I can't do it right now but I can take a look first thing tomorrow? would that be OK [17:08] jamespage, sure, that would be. === koolhead17 is now known as koolhead17|zzZZ === greyback|lunch is now known as greyback === koolhead17|zzZZ is now known as koolhead17 === christoffer_ is now known as Christoffer === salem_ is now known as _salem === kalosaurusrex is now known as albrigha [23:17] if somebody could confirm bug 928447 that'd be neat [23:17] Launchpad bug 928447 in ubiquity (Ubuntu) "possible to use a number for your computer's name (affects: 1) (heat: 6)" [Medium,New] https://launchpad.net/bugs/928447