/srv/irclogs.ubuntu.com/2014/02/28/#ubuntu-quality.txt

=== veebers_ is now known as veebers
=== yofel_ is now known as yofel
=== _salem is now known as salem_
=== salem_ is now known as _salem
pittiGood morning05:22
DanChapmangood morning07:05
pittihey DanChapman07:07
DanChapmanhey pitti :-)07:08
elfymorning DanChapman pitti07:09
pittihey elfy07:09
jibelGood morning07:47
pittijibel: I'm currently working on comparing before/after upgrade upstart jobs07:52
jibelpitti, I'd need latest autopkgtest on stable releases, what do you think is the best option: push the deb to auto-pkg-testing, download it from the archive or publish to backport?07:52
pittijibel: http://paste.ubuntu.com/7009176/ is my current diff (I didn't write the post-upgrade test yet)07:52
pittijibel: either download and install the deb, or debcheckout autopkgtest and autopkgtest/run-from-checkout07:53
pittijibel: we do the latter on the armhf/ppc64el boxes07:53
pittijibel: a-u-t> it's a bit unelegant to do the initial recording in bin/auto-upgrade-tester and the post-upgrade recording in UpgradeTestBackendSSH.py, but I didn't see how else it should work07:54
pittias in between .upgrade() and .test() the backend is not running, so I can't do the post-upgrade recording in bin/auto-upgrade-tester07:54
pittiand I can't do it in the post-upgrade test as that doesn't have a reference to the backend07:55
pittijibel: does that look acceptable, structurally?07:55
pittiugh, wazn is heavily loaded again08:07
pittiah, dkms fun08:07
jibelpitti, why cannot you do the pre-upgrade recording in UpgradeTestBackendSSH.py by adding an upgrade() method and do a super().upgrade() in each backend? would that work too?08:07
jibelpitti, yeah, it's running the qrt08:08
jibelpitti, I changed the schedule this morning, there is no need to run it every day08:08
pittijibel: ah, I can do that08:08
jibelthere is lot of duplicated code between LXC and Qemu which should be moved to SSH too08:09
pittijibel: so more like that? http://paste.ubuntu.com/7009233/08:12
jibelpitti, yes, I think it's structurally better08:13
pittijibel: added to EC2 as well08:13
pitti(the super())08:13
pittijibel: thanks08:14
* pitti will run that on aldebaran, wazn is too busy08:14
pittijibel: hm, I see the before/after services in http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-saucy-trusty-desktop-i386_vm/41/consoleText now, but I think I'll re-structure this again08:56
pittijibel: I'll copy the "before" list into the test bed after upgrade, and do the comparison in a post-upgrade test, so that a failure is yellow, not red08:56
pittijibel: otherwise I'd have to fail the test in the backend itself, which is ugly08:57
pittijibel: or can I raise a test failure (but not an upgrade failure) in the backend, too?08:57
jibelpitti, it's better to keep before and after in the testbed and run the test there than raising a test failure in the backend09:18
pittijibel: *nod*09:18
pittijibel: running with that now: http://paste.ubuntu.com/7009420/09:19
pittijibel: meh, now aldebaran has a load of 22; every machine I want to touch today goes crazy :)09:21
jibelpitti, sounds good. Just a small detail if a service contains 'running' in its name the test might be wrong.09:25
pittijibel: right, should check for /running09:26
pittior perhaps /running($|,)09:26
pittifixed to /running09:27
jibelmeh, I cannot just install autopkgtest from trusty on precise, it depends on debhelper which in turn depends on a whole bunch of packages :(09:33
pittijibel: you can't run it from git in your scenario?09:41
pittijibel: if you need a package, I can do a precise-compatible backport for you09:42
jibelpitti, I'd rather use a package that a checkout so we control the version we use09:45
pittijibel: the versions are tagged, so you can check out a particular version; but sure, let me build a package09:45
davmor2Morning all10:01
pittijibel: I think I'm ready to receive adt spam for ppc64el now; do you want these as well?11:00
pittijibel: i. e. I'd revert r298 for ppc64el11:01
jibelpitti, I do want spam11:05
pittijibel: oh, that'll re-enable notifications for everybody, not just us, right?11:07
pittijodh: but I guess that's fine11:07
pittijibel: committed to r31411:08
jibelpitti, or replace {{ email_recipients }} by our emails addresses11:09
jibelin the templates11:09
pittijibel: well, can't hurt if uploaders have a look if they break a test which has worked until now11:09
jibelsure, they'll feel the pain too11:09
pittijibel: http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-saucy-trusty-desktop-i386_vm/lastSuccessfulBuild/artifact/results/bootstrap.log :)11:14
pittiservices success11:15
pittijibel: that's http://paste.ubuntu.com/7009807/11:16
pittijibel: ok to commit and see how it behaves in the other tests?11:16
jibelpitti, nice. I can't say I succeeded11:17
jibel+ git clone http://anonscm.debian.org/git/autopkgtest/autopkgtest.git /tmp/adt/autopkgtest.checkout11:17
jibelCloning into '/tmp/adt/autopkgtest.checkout'...11:17
jibelerror: unable to open object pack directory: /tmp/adt/autopkgtest.checkout/.git/objects/pack: Too many open files11:17
jibelfatal: failed to read object 198b14448c0dafe33000867fb04bd57d9561fdab: Too many open files11:17
pittijibel: ah, I got the same one; weird with a proxy11:17
pittijibel: a git pull after you have a checkout generally succeeds, but I've seen this on the initial clonse11:17
pittijibel: workaround: clone locally, scp -r11:18
jibelmore and more interesting fatal: unable to access 'http://anonscm.debian.org/git/autopkgtest/autopkgtest.git/': Failed to connect to anonscm.debian.org port 80: Connection refused11:26
elfyballoons: https://code.launchpad.net/~elfy/ubuntu-manual-tests/1229511/+merge/20878012:01
knomeballoons, was your update-tracker-from-branch-script public and something others could use as well?12:04
=== _salem is now known as salem_
elopiorhuddie: you can put your MP as ready for review.13:23
rhuddieelopio, will do13:24
rhuddieelopio, I can't find the option for that, do I need to propose for merge again?13:28
elopiorhuddie: no, you only need to propose the merge again when you change prerequirements.13:28
elopiorhuddie: https://code.launchpad.net/~rhuddie/address-book-app/test_go_to_add_contact/+merge/20682813:29
elopioon top, it says status: Work in progress13:29
elopioyou should have a yellow button next to it.13:29
rhuddieelopio, ah thanks. easy when you know how :)13:30
elopiorhuddie: that's launchpad's motto.13:30
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== alex_abreu is now known as alex-abreu
elopiorvr, jcollado, rhuddie: want to hangout today?15:11
rhuddieelopio, sounds good to me15:12
rvrelopio: Yeah15:12
jcolladoelopio: Ok15:13
knometeenagers... ;)15:13
elopiorhuddie, rvr, jcollado: ok, same place https://plus.google.com/hangouts/_/canonical.com/new-features15:13
knomegoing to hang out in the mall?15:13
* knome hides15:13
elopioand random time, as always :)15:14
knome(for the record, i was just kidding)15:14
elopioknome: the cool kids hangout without getting up from the couch.15:30
knomeyou mean the fat kids?15:31
* knome hides15:31
knomeow, i can't fit under the table!15:31
knome;)15:31
elfylol15:44
* elopio goes to make some excercise :'(16:06
rvrelopio: These are the failures in webapps-demo on the phone with a clean install http://paste.ubuntu.com/7011100/16:06
rvrAre they similar to yours?16:06
elopiorvr: yes, that's what I'm getting.16:07
elopio"returned multiple results"16:07
rvrI will take a look16:07
rvrThat's supposed to be fixed by veebers16:08
elopiorvr: on his branch, alex changed the way we launch the apps:16:08
elopio7+ self.app_proxy = self.launch_click_package(16:08
elopio218+ package_name,16:08
elopio219+ app_name)16:08
senanDanChapman, balloons, hi :)16:08
elopiothat might do the trick.16:08
elopiothanks for looking into it rvr. Let me know if you find something.16:09
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== bfiller is now known as bfiller_afk
=== bfiller_afk is now known as bfiller
letozafballoons, elopio hi21:24
=== salem_ is now known as _salem

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!