[08:46] <jibel> jamespage, ping
[08:46] <jamespage> jibel: pong
[08:46] <jibel> jamespage, good morning
[08:46] <jamespage> ah - thresholds!
[08:46] <jibel> jamespage, yep :)
[08:46] <jamespage> sorry
[08:46] <jamespage> forgot to reply
[08:47] <jibel> np
[08:47] <jibel> balloons, I get the scrollbars with vmware too
[08:47] <jamespage> jibel: I'd go for current figures + 5%
[08:47] <jamespage> we will know when it grows then
[08:48] <gema> jamespage: what are the current numbers based on?
[08:48] <jibel> jamespage, ok, I'll update the check
[08:48] <gema> jamespage: I am trying to figure out if those tests are worth keeping or why they were added
[08:49] <jamespage> gema, http://testcases.qa.ubuntu.com/Install/ServerMinimalVirtualInstall
[08:49] <gema> jamespage: I know, I was looking at them yesterday, the source code
[08:49] <jamespage> the original target was a < 500 MB install
[08:49] <gema> looks quite random
[08:49] <gema> yeah, but why?
[08:49] <jamespage> the test case generally is worth keeping as it keeps an eye on the kernel size
[08:50] <jamespage> gema, why predates mw
[08:50] <gema> it measures the size of the whole install
[08:50] <jamespage> me
[08:50] <jamespage> gema, the purpose on the minimal virtual install is to have as small an install as possible for virtualized systems
[08:50] <gema> ahh, hold on, I wasn't talking about that one x)
[08:51] <gema> was talking about the installsize one
[08:51] <gema> jamespage: http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/ubuntu-server-iso-testing/trunk/view/head:/templates/test_cases/minimal-virtual/test
[08:52] <jamespage> gema, so am I
[08:52] <gema> jamespage: self.assertTrue( used < 590000, "Used: %s" % (used))
[08:52] <gema> that tests the size of the whole install
[08:53] <jamespage> gema, this is the test for quantal - http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-quantal/view/head:/test_cases/minimal-virtual/test
[08:53] <jamespage> gema, yeah - spot on
[08:54] <gema> jamespage: ok, my next question then would be, is that a smoke test or a regression test?
[08:55] <gema> jamespage: that affects 0 the usability of the system
[08:55] <gema> jamespage: nor we are going to fix it in a matter of hours
[08:56] <jamespage> gema, no
[08:56] <gema> jamespage: ?
[08:56] <jamespage> gema, no - its not going to be fixed in a matter of hours
[08:57] <gema> ok, then it is not a smoke test
[08:57] <gema> it should be run once a week or so
[08:57] <jamespage> gema, fine
[08:57] <gema> ok
[08:57] <jamespage> so long as the test run and we can see the results I'm not worried
[08:57] <jamespage> :-)
[08:57] <gema> jamespage: yep, I am trying to classify things the right way, so that we end up with the right tests in the right places
[08:57] <gema> jamespage: thanks
[08:57] <jamespage> gema, thats good with me
[08:58] <jamespage> we just need to ensure people don't just look at smoke testing as a measure of quality
[08:58] <gema> jamespage: for that we first need to have something else as well :)
[08:58] <jamespage> gema, agreed
[08:58] <jamespage> old habits die hard tho
[08:58] <jamespage> :-)
[08:58] <gema> yep
[08:59] <gema> jamespage: it'll take a while, but we'll get there
[09:01] <jamespage> gema, I guess once all of the tests are in a nice library assembling suites for smoke and regression focus will be much easier
[09:01] <gema> jamespage:  I hope so
[09:02] <gema> jamespage: the only thing that should be different for smoke testing is the runlist
[09:02] <gema> we can still have the tests in the same pool
[09:02] <jamespage> gema, +1
[09:02] <jamespage> that was how I was thing about it
[09:02] <gema> but have two different runlists, or as many as we need
[09:02] <gema> it may be that for arm we want to run different things
[09:02] <gema> for instance
[09:03] <gema> jamespage: but the current tests are going to end up in a legacy pool
[09:03] <gema> until we have a better home for them
[09:03] <gema> which will be built on the second step
[10:30] <jibel> desktop on mac is ok
[10:30] <jibel> testing alternate on mac
[10:39] <jibel> wubi's good on amd64 and i386
[13:12] <astraljava> balloons: Apologies, but I cannot attend the meeting. But I'm sure people are present afterwards, too, considering the milestone testing. I'll report directly to you later this evening.
[14:25] <phillw1> balloons: no meeting today?
[14:34] <jibel> first question is: no ballons today ?
[14:34] <jibel> *balloons even
[14:38] <phillw1> jibel I don't know, just popped on while taking a break from revision.
[14:38] <balloons> phillw1, jibel ahh
[14:39] <balloons> too engrossed in testing!
[14:39] <phillw1> lol
[14:42] <jibel> good morning balloons
[14:43] <balloons> morning jibel :-)
[14:51] <jibel> stgraber, what is your opinion on bug 1018271
[14:51] <jibel> stgraber, not the prompt but the second part of the bug report
[14:51] <jibel> dhcp setting not preserved upon installation
[15:07] <jibel> Daviey, should I go and populate the results for server from automated tests or someone on your team doing ?
[15:07] <Daviey> jibel: do you have the script?
[15:09] <jibel> Daviey, yes, not perfect, but kind of.
[15:13] <Daviey> jibel: If you are happy to, that would be great!
[15:14] <Daviey> jibel: would you mind committing the script to bzr somewhere.. as i only have what was emailed around.
[15:15] <jibel> Daviey, https://code.launchpad.net/~jibel/+junk/qatracker
[15:16] <Daviey> jibel: somewhere, less jibleised?
[15:16] <jibel> I can probably do that too.
[15:17] <Daviey> thanks :)
[17:42] <stgraber> jibel: did you manage to reproduce this bug? (1018271)
[17:42] <stgraber> jibel: I'm not aware of any change that would have affected netcfg in quantal
[17:43] <stgraber> as for the 127.0.0.1 part, it's the expected behaviour on a desktop running network-manager (netcfg probably discarded that dns info as it's on dhcp)
[18:13] <jibel> stgraber, I tried but I didn't reproduce it.
[18:24] <jibel> stgraber, I really cannot. The only way I found is to press 'cancel' when during dchp configuration in d-i. Which is not what I'd call an 'unexpected prompt'
[18:24] <jibel> unless the cat jumped on the keyboard
[18:25] <jibel> s/when //
[18:25] <stgraber> right :)
[18:25] <jibel> s/dchp/dhcp
[18:44] <patdk-wk> jeos is just hardly oversized now