elopio_ | veebers: do you have any reply for this? https://code.launchpad.net/~townsend/autopilot/fix-gcalctool-desktop-file/+merge/256702 | 04:57 |
---|---|---|
elopio_ | I wanted to tell him to change his test to do a normal launch hardcoding the app info in his branch instead, but I'm not sure if you have other plans. | 04:58 |
veebers | elopio_: lol that fix is the opposite of the fix that we needed recently for autopilot. I have no comment, a quick fix for the legacy branch seems fine | 05:01 |
veebers | I want to fix that within autopilot though, it's pretty crummy | 05:01 |
veebers | elopio_: I'm off, I might be back later though | 05:02 |
veebers | elopio_: to answer your questions: legacy reasons :-) this is really old part of autopilot / unity7 tests (i.e. launching known apps to test the desktop with). | 05:03 |
pitti | jibel: FTR, I created wily i386/amd64 VMs everywhere, and updated most vivid->wily things in lp:a-p-t | 07:26 |
pitti | jibel: so I guess we'll need to copy the jobs now, to give adt-britney something to chew? :-) | 07:27 |
pitti | http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html | 07:27 |
jibel | pitti, yep, I'll create the views on jenkins | 07:28 |
pitti | jibel: the views are nice of course, but what will cause the actual jobs to get created? does that need further changes somewhere? | 07:29 |
pitti | jibel: or just the RELEASE= bit in a-p-t? | 07:29 |
jibel | pitti, no, that won't create the job, I'll create the job afterwards, otherwise I won't be able to see what is created automatically | 07:29 |
jibel | actually I might not be able to do that anymore, they removed my privileges | 07:30 |
jibel | I'll try | 07:30 |
pitti | jibel: want me to copy/set up setup-testbed and setup-lxc for now? | 07:30 |
pitti | jibel: or will that get in the way of your mass-copy? | 07:30 |
jibel | pitti, i'll do it | 07:30 |
pitti | *nod* | 07:31 |
pitti | jibel: we'll need to leave setup-testbed disabled for now (I'll update the VMs manually every now and then until we get cloud images) | 07:31 |
jibel | pitti, you setup proposed-migration on snakefruit? | 07:43 |
pitti | jibel: I didn't; if you tell me how, I'm happy to | 07:43 |
jibel | pitti, someone did it apparently | 07:43 |
pitti | jibel: then infinity, I guess | 07:44 |
pitti | jibel: he asked me this morning about adt-britney support for wily | 07:44 |
jibel | ok | 07:44 |
pitti | jibel: I pulled a-p-t there now | 07:44 |
pitti | jibel: can we disable the old-style VMs part in http://d-jenkins.ubuntu-ci:8080/job/wily-adt-setup-testbed/configure and enable your new DKMS bit now? | 08:36 |
jibel | pitti, no, not yet, we still need it for custom kernels | 08:37 |
pitti | jibel: I'll verify and enable setup-lxc | 08:37 |
pitti | jibel: ah, I'll build the old-style VMs for wily on wazn then | 08:37 |
jibel | pitti, the new dkms bit only works for the default kernle | 08:37 |
pitti | jibel: ok; can we still turn this on to see how it goes? | 08:37 |
jibel | pitti, sure, I'll push the code | 08:38 |
jibel | pitti, don't you prefer to wait for a first successful run of britney? | 08:38 |
pitti | jibel: ah, ok | 08:39 |
dkessel | DanChapman: thanks for wanting to look into the automatic image testing issues! | 09:40 |
brendand_ | ubuntu-qa - a review of https://code.launchpad.net/~canonical-platform-qa/unity-scope-click/wait_for_search_button/+merge/258002 much appreciated | 09:43 |
davmor2 | brendand_: why the _ ? | 09:45 |
brendand_ | davmor2, dunno | 09:52 |
brendand_ | davmor2, won't let me change it | 09:52 |
brendand_ | davmor2, probably someone else logged in with it | 09:52 |
jibel | pitti, there are 2 jobs in the queue but no executors | 09:58 |
pitti | jibel: because of the long build queue? | 09:59 |
pitti | http://d-jenkins.ubuntu-ci:8080/job/wily-adt-mpich/1/console | 10:00 |
pitti | jibel: that just says that it's waiting for an executor? | 10:00 |
jibel | pitti, yes | 10:00 |
jibel | pitti, new glibc in vivid? | 10:01 |
pitti | jibel: new KDE | 10:01 |
jibel | ah | 10:02 |
jibel | + new kernel | 10:02 |
pitti | jibel: old-style VMs created for wily on wazn | 10:28 |
jibel | pitti, thanks, I'll find some time to finish porting the old-style dkms tests to autopkgtest | 10:40 |
pitti | jibel: http://d-jenkins.ubuntu-ci:8080/view/Wily/view/AutoPkgTest/ \o/ | 10:53 |
jibel | pitti, do you want me to trigger $world for wily or wait a bit? | 11:43 |
pitti | jibel: oh, do we need to? i. e. not just copy the last successful result? | 12:33 |
jibel | pitti, no we don't have to | 12:33 |
pitti | jibel: if so, sure -- aside from armhf the queues have caught up | 12:33 |
pitti | but we need to copy the last successful vivid result either way, no? | 12:34 |
jibel | pitti, history has been copied over from vivid, it's all good | 12:34 |
pitti | to detect regressions | 12:34 |
pitti | ah, great | 12:34 |
pitti | jibel: many thanks | 12:34 |
jibel | lets save some CPU cycle and some trees :) | 12:34 |
jibel | pitti, I'll wait next publisher run to make sure results are copied back to britney and push the code to enable dkms | 12:35 |
pitti | \o/ | 12:36 |
jibel | pitti, results have been synced. pushing the patch for dkms | 13:02 |
jibel | well, I've to fix the grep-dctrl command first :) | 13:08 |
=== elopio_ is now known as elopio | ||
jibel | pitti, the expression in detect in autodep8 returns 23 dkms packages while there are 40 in vivid | 13:25 |
jibel | with main, universe, restricted and multiverse enabled | 13:25 |
jibel | nm, if I consider all the apt index files it's better :) | 13:33 |
jibel | pitti, so, there'll be some dkms packages missing because proposed migration only uses sources files | 13:39 |
jibel | for example there is nothing in restricted_source that tells if nvidia is a dkms package or not | 13:41 |
pitti | jibel: ah, I thought we were looking at binary packages | 14:50 |
pitti | jibel: wrote that down as TODO, it's quick email/UOS time now | 14:50 |
jibel | pitti, proposed-migration reads source packages for an XS-Testsuite header matching autopkgtest. The place where we added dkms detection will read the same sources | 14:52 |
jibel | pitti, anyway we can start with that | 14:53 |
pitti | jibel: agreed, let's see how these 24 perform now | 14:53 |
jibel | pitti, okay to push http://paste.ubuntu.com/10990321/ ? | 14:53 |
jibel | pitti, it's basically the same thing we did at the sprint fixed to be python compliant | 14:54 |
jibel | (removed some quotes and escape characters and use source files instead of debian/control) | 14:55 |
pitti | jibel: LGTM, let's roll with that and see how it goes? | 14:55 |
pitti | jibel: and we'll refine later (maybe just add a static list for now) | 14:55 |
jibel | pitti, pushed | 15:21 |
pitti | jibel: go, go, go! :-) | 15:22 |
pitti | jibel: now we just need to upload something which triggers them :) | 15:23 |
jibel | pitti, I'll tail britney's logs before cjwatson pings me telling I broke it ;) | 15:23 |
elopio | vila: fgimenez: published the trusty versions. | 15:29 |
elopio | I think. I'm still a newbie with ppas. | 15:29 |
fgimenez | elopio, ok thanks lot, i'll relaunch the job | 15:30 |
vila | elopio: right, you copied the vivid versions ;) recipes are a bit easier to build for multiple releases at once (and provide clearer versions too IMO) | 15:32 |
fgimenez | elopio, perfect, it liked your ppa ;) | 15:32 |
elopio | vila: how do I make a recipe? | 15:33 |
elopio | ah, nevermind. I'll just search the launchpad docs when I have some free time. | 15:33 |
vila | elopio: from a branch you click the 'Create packaging recipe' button | 15:35 |
vila | elopio: the most painful part is to select the target PPA in the huge list | 15:35 |
tych0 | hello | 15:46 |
alesage | balloons receiving some bad news about the LXD session, tych0 realizing he has a conflict | 15:46 |
balloons | tych0, ohh.. when can we reschedule? | 15:51 |
tych0 | balloons: i could do tomorrow at the same time? | 15:52 |
balloons | alesage, you should have the power to move things around. | 15:54 |
balloons | tych0, we are full schedule but we can try and fit. if you can't do it today, you can't do it :-) | 15:54 |
tych0 | balloons: yeah, sorry | 15:54 |
balloons | meaning, we'll make it work for later | 15:54 |
alesage | balloons, will this make a conflict with an existing session? --right ok | 15:54 |
tych0 | well, or anyt ime really | 15:54 |
balloons | sorry, not to confuse. I mean, if today doesn't work, pull it off the schedule and we'll make it work later | 15:54 |
tych0 | balloons: sure, understood | 15:55 |
balloons | but it will be hard. just have a look at the schedule and see | 15:55 |
alesage | balloons, tych0 there's an empty slot Thursday 16:00 ? | 15:56 |
alesage | tych0, which I think is 3:00 PM for you? | 15:57 |
tych0 | alesage: 1600 UTC? | 15:57 |
alesage | tych0, yessir | 15:57 |
tych0 | hm, i think that's 10AM MDT unless i'm misunderstanding | 15:58 |
alesage | tych0, or sorry, 10:00 AM my mistake in CO | 15:58 |
tych0 | but yeah, that works | 15:58 |
alesage | tych0, you're right, I'm bad at math | 15:58 |
alesage | tycho ok I'll move the session if you're willing :) | 15:58 |
tych0 | alesage: sure, works for me | 15:58 |
alesage | tych0, great | 15:58 |
balloons | elopio, ready for the helpers session. | 18:49 |
elopio | balloons: almost, just recording the last demo. | 18:49 |
balloons | I'll set everything up | 18:49 |
elopio | balloons: can you send the official documentation links to the channel when we start? | 18:54 |
elopio | I have my history full of old links | 18:55 |
balloons | elopio, yes | 18:55 |
elopio | veebers: #ubuntu-uos-appdev | 18:58 |
elopio | balloons: the three unity8 branches are in a silo. After that lands, we can propose the namespace refactor + sphinx. | 19:56 |
balloons | elopio, awesomeness | 20:03 |
bip | Hello :) | 20:20 |
bip | All to work? ;-) | 20:25 |
elopio | bip: hello | 20:32 |
bip | Hello elopio :) | 20:33 |
Noskcaj | hi bip | 21:37 |
bip | Hey man! sorry for disturb! :) | 21:38 |
Noskcaj | You can test ISOs on virtual machines if you want, it sppeds up the process of testing so most people use VMs | 21:38 |
Noskcaj | *speeds | 21:38 |
bip | Noskcaj: ok. There's a standard option for a good testing? Type 1 Gb ram - 20 gb hdd etc? | 21:39 |
Noskcaj | That should be enough, as long as there is enough hdd space to install, anything should work | 21:39 |
bip | Noskcaj: you're a ISO Tester? | 21:40 |
Noskcaj | I started my ubuntu contributions with iso testing, i mostly do packaging work now | 21:41 |
bip | Noskcaj: perfect i think is a good start for me in this team :) | 21:41 |
Noskcaj | :) | 21:41 |
bip | Noskcaj: can you help me in this startup ? | 21:41 |
Noskcaj | sure. | 21:42 |
Noskcaj | If you're using a GUI, you might want to have a look at the program "testdrive" | 21:42 |
Noskcaj | It's not super well maintained, but it allows you to sync the current iso and automatically makes a VM with it | 21:42 |
bip | Noskcaj: yes on server i got KDE. This becouse i make some Organizzation Test :) | 21:43 |
bip | Donwload. | 21:45 |
bip | Noskcaj: very good idea. Thx you. Now I'm download Vivid-Desktop-amd64.iso (10 min) | 21:46 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!