[01:45] I'd like to buy/create an ubuntu laptop with a fairly recent chipset and a design like the single-frame titanium macbook pro [01:46] are there any ubuntu compatible hardware that might be close to that where I can start researching? === micahg_ is now known as micahg === cjohnston is now known as cwt-bugs === cwt-bugs is now known as cjohnston === _salem is now known as salem_ [11:38] Hola... So.. if i want to add a test to the upgrade tester, what do i need to do? [11:38] gema / jibel ? [11:39] Daviey: ? [11:39] gema: ^^ above [11:39] yes I am thinking [11:40] to which job do you want to add a test? [11:40] gema: bug 923685 looks like a good candidate for post upgrade inspection [11:40] Launchpad bug 923685 in resolvconf (Ubuntu) "New resolver package overwrites manually created resolv.conf on server (affects: 1) (heat: 6)" [High,New] https://launchpad.net/bugs/923685 [11:40] Daviey, Hello [11:40] hello jibel, having fun? :) [11:42] Daviey: ideally if you write a pyunit script for the test case, we should be able to create a job for it [11:42] for the time being [11:42] am I right, jibel ? [11:42] Daviey, file a bug against update-manager (this is where auto-upgrade-tester is), write your requirements, the test case and attach a test script ideally a python unittest [11:42] Daviey, and assign the report to the QA team [11:43] and I've fun, yes I do. [11:43] jibel: Do you have a good example of your unittest style? [11:44] * Daviey is seriously stoked we have unit testing framework now btw. :) [11:44] Daviey, http://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/view/head:/AutoUpgradeTester/post_upgrade_tests/test_lts_upgrade_user.py [11:44] Daviey, this is an example of what pitti write for the desktop team [11:45] jibel: So, does this get run in it's own sterile enviroment - or along with other tests? [11:45] Daviey, depends on your requirements. [11:46] jibel: how does that get declared? [11:47] it can be run in it's own environment, in this case we'll create a specific profile, or with other test, in which case, we'll add the test to an existing profile [11:47] Daviey: ideally , unless the test is destructive , you are better off running it with others [11:48] Daviey: more realistic environment [11:48] jibel: So, if i land a file into that location, it doesn't get picked up on it's own - you fiddle with jenkins? [11:48] gema: right.. just trying to understand the infrastucture. [11:48] Daviey: the infrastructure is not there yet [11:48] it 's all manual at the moment [11:48] Daviey, by default everything in post_upgrade_test is run [11:49] I manually configure the profiles to blacklist specific tests [11:49] we won't be able to pick things automatically (not that we would, because we like to review stuff) until next cycle [11:49] gema: okay, how do i invoke the tester for local test development? [11:49] jibel: ah! [11:49] for example it doesn't make sense to run desktop test on server upgrades [11:49] or lts test on oneiric to precise upgrades [11:49] right [11:50] jibel: well, seemed pitti coded logic to drop out if it's mot LTS->LTS [11:50] Daviey, https://wiki.ubuntu.com/QATeam/UpgradeTestingSetup [11:51] Daviey, yup, I added that logic, don't bother with that now. write the test, describe the test environment and conditions required to run the test, and we'll figure how to fit it in. [11:52] * jibel -> lunch. back in 45mn [11:54] thanks jibel & gema [12:28] jibel: are we using lxc in the main QA lab? [12:46] jamespage, I used it in the lab to setup an environment for litmus and for package testing. [12:46] jibel: ack - I'm just looking at the work m_3 has done to automatically test charms - it uses the lxc local provider for juju [12:47] linking about where to deploy longer term... === greyback is now known as greyback|bia === Ursinha` is now known as Ursinha === greyback|bia is now known as greyback === salem_ is now known as _salem === _salem is now known as salem_ === bladernr_afk is now known as bladernr_ [16:03] balloons: hey! an Ubuntu Friendly meeting is starting in #ubuntu-meeting, in case you're interested [16:04] balloons: I think the topics today are mainly technical, still I thought I'd give you a heads-up === bladernr_ is now known as bladernr_afk === yofel_ is now known as yofel [16:11] roadmr, on ,y wat thanks === bladernr_afk is now known as bladernr_ === salem_ is now known as _salem === bladernr_ is now known as bladernr_afk === koolhead17 is now known as koolhead17|zzZZ [23:54] hey guys , I want to ask if there's any way of using the update manager to get alpha 1 or the daily builds or must I go through the USB/CD install ?