[00:28] anyone around that might be able to help me with s-jenkins permissions? [02:05] === trainguards: IMAGE 221 building (started: 20140904 02:05) === [02:09] you know it's time for bed when you see that message [03:05] === trainguards: RTM IMAGE 15 building (started: 20140904 03:05) === === Ursinha is now known as Ursinha-afk [03:08] BLAM! https://code.launchpad.net/~robru/cupstream2distro/readability-cleanup/+merge/233284 got it down from 1234 pep8 violations to 825 (all of citrain/ directory is fixed but nothing outside of it, like cupstream2distro/ directory or tests/ directory). merged it like that for now (with the remaining 825 whitelisted) because I'm out of time. need to push [03:08] this to production and make sure nothing exploded. [03:16] fginther: any chance you're still around? found a bug in the autolanding job, fixed it, how can i rerun it? i reapproved the branch but it doesn't seem to be working... === Ursinha-afk is now known as Ursinha [03:17] robru, what's the MP? [03:19] robru, https://code.launchpad.net/~robru/cupstream2distro/readability-cleanup/+merge/233284 is running right now [03:19] fginther: oh ok thx, just impatient i guess [03:25] fginther: https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/1357983/+merge/232630 [03:25] that passed CI, then when I top approved it complains it failed ci? [03:26] I am confused. [03:26] hmm [03:27] popey: the autolanding job is different than the ci job, so it's probably misconfigured or something. not sure. [03:30] will look again in the morning when I am awake [03:30] ta [03:45] === trainguards: IMAGE 221 DONE (finished: 20140904 03:45) === [03:45] === changelog: http://people.canonical.com/~ogra/touch-image-stats/221.changes === [03:48] thanks, will do rtm tomorrow morning [03:50] sergiusens: you're welcome! [04:05] morning [04:07] Mirv: Heya! [04:08] robru: heya heya! [04:08] Mirv: i just did a massive pep8 overhaul on ci train. Shouldn't have any semantic change unless i made a mistake. Keep an eye out for goofy syntax errors when running Jenkins jobs, should be easy to fix [04:09] robru: pep8 and funny syntax, check. [04:09] I ran a few jobs already and it seemed sane, but there's lots of code paths that are just totally untested [04:10] yeah, I see you've touched almost everything. anyway, they should be easy to fix if something is wrong. [04:10] Mirv: yeah ;-) [04:11] Mirv: not done yet! I fixed about 400 out of 1200 pep8 violations. Will try to get the rest tomorrow [04:13] robru: ok, a jolly amount of things to fix, there [04:20] === trainguards: RTM IMAGE 15 DONE (finished: 20140904 04:20) === [04:20] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/15.changes === === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [07:20] thostr_, hello [07:20] brendand: hi [07:34] eh, need to do an emergency drive to the vet, I should be back for the meeting [07:37] :( [07:42] thostr_, i'm hoping to sign off silo 13 soon [07:43] thostr_, for the new stuff it lands, did you or charles add a test case to the test plan? [08:06] Back [08:09] Mirv: sil2100: I am done with the UITK validation. All test logs are backed up, the UITK does not cause any regression. I have pulled out the header animation because that would have caused psorblems for few tests. [08:10] Mirv: sil2100: So the UITK for Ubuntu archive in silo12 is good to go. When it lands I will start the RTM testing. [08:10] bzoltan: excellent! [08:10] Mirv: did you press the publish button on it already? ;) [08:11] Mirv: ok, let me handle the pressing [08:11] bzoltan: just a quick one - the merges need approval :) [08:14] bzoltan: re running ;) [08:14] bzoltan: publishing o/ [08:15] Thanks again for the hard work! [08:15] sil2100: cool, thanks [08:15] sil2100: it was not hard :) hard is running a marathon :) it was just long. [08:22] bzoltan: good stuff! [08:22] sil2100: thanks! [08:23] bzoltan: yeah ;) But it takes up precious time and resources anyway [08:25] bzoltan: sil2100: might not be anything dangerous, but err zoltan launched non-rtm new build 20 mins ago in landing-012? and that not-yet-built rebuild was actually what got published? [08:25] while the rtm silo build is from yesterday [08:25] Mirv: that was my testing script change [08:26] Mirv: I added the -p archive handling to make the stock image testing possible [08:26] bzoltan: aha, right. still, it wasn't finished yet in the PPA so now it got copied not completely built. a smoke-test would have been nice too, but well, indeed the change is nothing to worry about! [08:27] Mirv: I got the message that the build was successful... [08:27] Mirv: strange [08:27] * ogra_ gets meeting coffee [08:27] and there is some non-true dependency wait now in the archive build :S https://launchpad.net/ubuntu/utopic/+source/ubuntu-ui-toolkit/1.1.1227+14.10.20140904-0ubuntu1 [08:27] let's see... [08:28] sil2100: ^ bzoltan is btw right, he did get utopic "Packages built" from the bot basically right after clicking build. [08:28] that might be a regression on how the "built" status is fetched, related to the sync silo fixing [08:29] Damn [08:29] Mirv: we didn't change how the build status is fetched [08:29] anyway, we've a meeting to do so let's see after that if the archive builds have started themselves :) [08:29] sil2100: it says "building" and then Finished: SUCCESS.. eh. https://ci-train.ubuntu.com/job/ubuntu-landing-012-1-build/37/console [08:30] Mirv: this is the thing we mentioned, either something changed in LP API or something... we even made it more restrictive because of problems like this and it didn't help :| [08:31] ygh [08:31] Wait [08:31] Mirv: I was a bit surprised, but I thought that the builders are on steroid... in pbuilder the armhf takes 20minutes [08:31] THis one is just wrong [08:31] sil2100: yeah, it's not even that, it's just wrong :) [08:31] sil2100: it is indeed wrong [08:31] brendand: that was mostly bug fixes [08:32] brendand: so, test plan hasn't changed [08:32] thostr_, there was something about hardware alarm support? [08:34] brendand: but silo 13 is about power changes [08:34] thostr_, i'm looking at the changelog [08:34] brendand: that was mostly about displaying the right icons depending on the power level [08:35] thostr_, sorry - it's powerd 'hardware wakeup support' [08:35] robru: we might have some small regressions from the changes :) [08:37] I know that utopic-proposed is not the focus, but I cannot unlock a SIM card on 221 and that'll probably land in ubuntu-rtm soon. [08:38] on mako [08:53] brendand: ah right. I'd need to check whether charles has updated it [08:56] brendand: there is no specific test case for that. Actually, I think we're missing a holistic alarms test plan (which covers multiple components) [08:57] brendand: do we have other examples of such kind of integration tests? [09:02] thostr_, i'm sure there are plenty of examples :) [09:02] brendand: sure, but where? [09:03] thostr_, not written down anywhere that i know of [09:03] thostr_, there must be a test plan for alarms in one of the applications or indicators [09:03] thostr_, you should probably link to that [09:05] or we just create an alarms test plan which we then reference in indicator, powerd, clock app, PIM, ... [09:05] Mirv: great to see that I can use the rtm images just as the utopic images... so i can add PPAs and stuff :) cool [09:06] thostr_, sure - but i'm just saying that other test plans might already have those test cases, so if you look there you might get some inspiration [09:06] Mirv, oh is citrain script fixed? [09:07] bzoltan: !! nice, it was annoying [09:07] brendand: which script? [09:07] Mirv, what's bzoltan talking about? [09:07] Mirv: one thing i do not get thu .. the RTM and non RTM PPAs [09:07] sil2100: bzoltan: I found the dependency problem, we need a package promoted to main -> moving to #ubuntu-release [09:08] brendand: oh, you mean that.. yes, bzoltan did new fixes to his testing script [09:08] new krillin tarball pushed [09:08] Mirv, okay - i'm just curious to know if anyones hacked together a simple way to add silos [09:09] brendand: adding silos to what? [09:10] john-mcaleely, thanks ! [09:10] davmor2: do you have a clean phone you can test my dialer issue on? [09:10] (on that hasn't made any calls) [09:10] bzoltan, "great to see that I can use the rtm images just as the utopic images... so i can add PPAs and stuff :) cool" - what did you mean? [09:10] Mirv: wait, what? Oh man, the packaging changes didn't have any new dependencies added [09:11] Mirv: actually there was no UITK packaging diff [09:11] brendand: during tha last RTM validation the add-apt-repository did not work on RTM images [09:11] sil2100: or, maybe this happened already before and we don't catch them before manual rebuilds in archive? [09:11] oh my [09:11] popey: no but I will do when I comme back at 11 [09:11] kk [09:11] bzoltan: sil2100: qml-module-qt-labs-settings is in universe [09:11] will file bug, not done yet [09:11] but comes from a main source package [09:11] Mirv: or maybe that was that additional test change that bzoltan did? [09:12] sil2100: no, it wasn't [09:12] sil2100: no, I just fixed my shells cript what does the test plan [09:12] bzoltan: ok, so it must have been around for longer [09:12] https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.1.1214+14.10.20140826-0ubuntu1 also had the dep already [09:13] hmm, why we didn't get any MIR here... [09:13] sil2100: binary packages from approved main source packages are moved to main on request [09:13] in general [09:17] bzoltan, yes that's right - what did you do to fix that? [09:19] brendand: :) i did not do anything. It just works now :) [09:21] so apt-add-repository now works on rtm too [09:23] Mirv, hmm interesting. i haven't seen any movement on those bugs [09:23] psivaa, i have a device freshly flashed with -proposed now [09:23] psivaa, what steps does the ci loop go through? [09:29] brendand: if you haven't used the provision.sh script in lp:ubuntu-test-cases/touch then it might be more manual work. i'd rather do 'scripts/provision.sh -i touch_stable -w' from the branch [09:29] http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/README-cli.rst has information too [09:35] bzoltan, em - you better be careful. our testing shows it adds the wrong ppa [09:35] bzoltan, i.e. the utopic one [09:35] brendand: Well.. that was one question I asked ... what is the diff between the rtm and non rtm PPAs... because on the PPA page they are the same [09:36] brendand: Mirv: sil2100: RTM -> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-012 [09:36] brendand: dont forget to include your network file in provision.sh (for magners-wifi) [09:36] brendand: Mirv: sil2100: NON RTM -> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012 [09:36] bzoltan: yeah, so LP doesn't yet properly update the description :| [09:36] bzoltan, rtm binaries are built against the rtm archive ... [09:36] brendand: Mirv: sil2100: and in both cases the PPA is ppa:ci-train-ppa-service/landing-012 [09:37] bzoltan: but anyway, you need to use ppa:ci-train-ppa-service/ubuntu-rtm/landing-012 for RTM [09:37] sil2100: OK, thanks [09:37] bzoltan: although apt-add-repository won't work, so I guess brendand always adds the PPA manually [09:37] :< [09:42] Oh geez [09:43] * sil2100 just saw what happened to the citrain code [09:43] I mean, visually [09:43] It now looks terribly on my sublime editor [09:55] sil2100: brendand: should we maybe get QA signoff also for the utopic mediascanner2/thumbnailer landing, because of the past regressions? [09:57] psivaa: could you (or someone else?) trigger ci for the "update components" merges from akiva at the bottom of this list please? http://people.canonical.com/~dpm/core-apps-sponsoring/ - he's not in the teams so it didn't trigger automatically... [10:02] Mirv, technically no - since we aren't in traincon for utopic - are we? [10:02] popey: akiva is added to allowed users now in core app jenkins [10:02] thank you. will that magically autotrigger? === psivaa changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: psivaa | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ♫ I feel more awesome than an awesome possum ♫" [10:03] sil2100, add-apt-repository ppa:ci-train-ppa-service/ubuntu-rtm/landing-012 doesn't work [10:04] popey: yes, it should [10:07] popey: right wiping in progress did you file a bug in the end? [10:08] sil2100, so far the only way we know that works is adding by hand. if you know an automated way it would be really good to hear [10:08] davmor2: bug 1365400 [10:08] bug 1365400 in dialer-app (Ubuntu) ""Recent" pull-up confusing on new phone" [Undecided,New] https://launchpad.net/bugs/1365400 [10:08] psivaa: thanks [10:08] * brendand could probably whip something up with launchpadlib [10:12] brendand: yeah, so as I said [10:13] brendand: yeah. I'll just try it a bit on my own. [10:15] sil2100: right fresh Wipe I'm going to see if reboots re show the wizard [10:18] popey: no joy but there is an update to the recent page that might be stopping it now [10:18] popey: you now get all and missed [10:18] davmor2: you can't reproduce it? [10:19] on krillin ? [10:19] popey: not on current image I can't [10:19] well thats odd [10:19] you have a SIM in it? [10:20] popey: yes [10:20] ah well [10:20] brendand: how's the AP-test going? [10:20] popey: as I say there was an update to the recent page that may be stopping it now [10:21] sil2100, still in progress [10:21] popey: did you have the all missed in the gap at the top when you first saw the issue? [10:22] davmor2: right, but i dont see how you can have different dialer-app if we're on the same image [10:23] https://www.youtube.com/watch?v=ubrTjVKU6eM [10:32] psivaa, sil2100 - provision.sh ran and the wizard is still there [10:32] psivaa, sil2100 - http://paste.ubuntu.com/8232013/ [10:33] uh [10:33] brendand: ok, 'phablet-config welcome-wizard --disable' does not work then [10:33] ? [10:33] psivaa, does it need to reboot? [10:34] brendand: 1 sec [10:35] sil2100: hey, robru has reset silo 10 yesterday, but it still lists packages and seems to be confused [10:36] sil2100: all is merged (by hand) though; I'll delete the packages from the PPA or can you reset the state of the silo in a harder way? [10:36] psivaa, after i reboot the wizard is gone - but should provision.sh have done that? [10:37] brendand: no, the device reboot is part of running a particular test [10:37] psivaa, ok [10:38] lool: hey! Let me take a look [10:39] brendand: 'scripts/run-autopilot-tests.sh -a mediaplayer_app' should start the AP testing [10:39] does someone have the lp snippets for creating RTM PPAs? [10:39] lool: yeah, I have some [10:40] psivaa, where is reboot-and-unlock.sh? [10:40] lool: if you want to create an RTM PPA for a team, then use: lp.people['some-team'].createPPA(distribution=lp.distros['ubuntu-rtm'], name='thename') [10:40] thanks [10:41] lool: btw. silo 10... did you merge in all the changes by hand already? [10:41] sil2100: yes [10:41] brendand: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/files/head:/utils/host/ [10:42] lool: and all packages in the archive, right? (double confirming) [10:42] lool: if yes, then I clean the silo :) [10:44] (I assume so) [10:44] lool: ok, so I do a silo clean without processing merges [10:44] sil2100: all in the archive [10:45] psivaa, what runs phablet-config writable-image? [10:46] * sil2100 off to lunch [10:47] sil2100: so I'm on reboot number 4 no sign of the wizard on 16 [10:47] brendand: the -w flag in provison.sh: [10:47] psivaa:touch$ grep -wr "phablet-config writable-image" [10:47] scripts/provision.sh: phablet-config writable-image $CUSTOMIZE [10:48] sil2100: do you know if rsalveti and kenvandine were disabling the wizard with phablet-config? === om26er_ is now known as om26er [10:49] psivaa, ah do you guys set that normally? [10:50] psivaa: https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/1357983/+merge/232630 runs fine on my desktop but fails in jenkins.. any ideas? [10:53] psivaa, can you show me the call to provision.sh that jenkins uses? [10:54] popey: the failing ones are, touch and mako jenkins jobs. on desktop (amd64) it passes in jenkins too [10:55] brendand: in http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/64/consoleText : [10:55] touch/scripts/provision.sh -i touch_stable -w === MacSlow is now known as MacSlow|lunch [10:56] psivaa, ok i'll try that now [10:58] psivaa, now we'll see [10:59] brendand: ack. did you change the network file information in provision script? [11:00] psivaa, yep i specified -n [11:00] brendand: ack [11:01] psivaa: sorry, I don't understand [11:07] popey: the failing jenkins jobs are: https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-utopic-touch/343/? and http://jenkins.qa.ubuntu.com/job/generic-click-autopilot-runner-mako/484 which are not running on the desktop. but jenkins results for desktop arch is passing as it does to you locally [11:08] popey: so i'd think running the test on mako locally would help [11:08] psivaa: ok. [11:37] psivaa: Is there a way I can retrigger CI on https://code.launchpad.net/~mvo/click/lp1219912-build-exclude/+merge/219716 ? The rebuild link (http://s-jenkins.ubuntu-ci:8080/job/click-devel-ci/2/rebuild) has apparently expired or something and now gives me a 404 [11:37] cjwatson: let me check [11:37] (and yes, I'm on the right VPN [11:37] ) [11:45] cjwatson: because the first job ran a little while ago and somehow the old builds in this job have been cleaned, we are unable to retrigger the build. [11:45] cjwatson: i have now triggered a build with the info from MP [11:45] cjwatson: should work. but i'll keep a watch [11:47] hmm that has thrown a conflict in the merge [11:47] brendand: so, any luck with the autopilot problem ;/ ? [11:47] cjwatson: could the conflict resolved and committed to the MP? that should trigger a build automatically too [11:47] brendand: it's the wizard's fault? === ubot5` is now known as ubot5 === psivaa changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ♫ I feel more awesome than an awesome possum ♫" === om26er is now known as om26er|afk === MacSlow|lunch is now known as MacSlow [12:14] sil2100: could you see/ack landing-014 packaging changes? I tested a bit locally since it's thumbnailer again, music/video seemed fine also after reboot [12:14] Mirv: let me take a look - I wouldn't require a formal QA sign-off for that, but yeah, good that you're trying to proceed safely ;) [12:19] Mirv: packaging wise it looks ok, so a +1 [12:20] Mirv: I also see that thumbnailer does not include any new deps, so it should be fine :) [12:22] plars: hey! [12:26] brendand: ping === cjwatson_ is now known as cjwatson [12:28] psivaa: thanks for whatever you did there [12:29] cjwatson: np :), had to manually copy to the fields in 'Build' since 'Rebuild' dint work. [12:31] psivaa: if you could do the same for https://code.launchpad.net/~mvo/click/framework-info/+merge/220199, or tell me how to do it, that'd be lovely [12:31] sil2100: thanks! [12:32] brendand, did you get anywhere yet ? [12:33] looking at thw wizard upstart job i see a "stop" at the top of the pre-start script ... i wonder if thats shouldnt be "{ stop; exit 0; }" instead ... [12:35] cjwatson: it's filling 'landing_candidate', 'merge_proposal' and 'candidate_revision' with the information 'bzr+ssh://ps-jenkins@bazaar.launchpad.net/~mvo/click/framework-info', 'https://code.launchpad.net/~mvo/click/lp1360582-honor-enum-only-trusted/+merge/233001' and '507' in 'Build now' option. [12:35] cjwatson: i've done it for the above now. [12:36] and that merge has no conflicts, so it should go well [12:36] sil2100, ogra_ - i see 'scripts/run-autopilot-tests.sh: 104: scripts/run-autopilot-tests.sh: subunit2junitxml: not found' [12:37] maybe i need to install that though [12:37] brendand, well, but why would that have any influence on the wizard [12:38] ogra_, it doesn't - just it's the only issue i see so far with -proposed [12:38] ogra_, everything seems fine from here [12:38] oh, so you couldnt reproduce ? [12:38] i thought oyu could [12:40] psivaa: thanks [12:43] brendand: so you couldn't reproduce the issue we're seeing yet? [12:44] sil2100, i wonder could it have something to do with phablet-tools? [12:45] perhaps i should update that and check again [12:45] sil2100: hi, good morning [12:48] plars, we're desparately trying to find out why krillin rtm doesnt unlock [12:48] (since image 14) === charles_ is now known as charles [13:07] if i rebuild rtm silo 3 (line 11) will that grab the latest packages from utopic? [13:07] it includes fixes for the bugs that kept it from passing QA before, but it also includes much more [13:08] Mirv: still trying to figure out what is broken with the build jobs, but something is reproducibly broken - the watch-ppa script only runs once === josepht changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard josepht | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ♫ I feel more awesome than an awesome possum ♫" [13:13] Mirv: but at least I confirmed now that the refactoring is the source of the problem - reverting it fixed stuff for proposed [13:13] robru: ^ [13:14] sil2100, see my question about rtm silo 3? [13:15] kenvandine: hey! Let me take a look [13:15] sil2100, i think the bugs that made it fail QA are fixed in utopic now [13:15] can i just rebuild that silo ? [13:15] kenvandine: so, the feature of sync silos retargetting ubuntu automatically is currently not yet deployed as we have some problems there, so we probably have to retarget the silo to utopic instead [13:16] kenvandine: let me just do that :) [13:16] kenvandine: you'll get a new silo probably [13:16] ok, thx [13:16] kenvandine: you want both unity8 and u-s-s from utopic, right? [13:17] i think unity8 has to go with it... but can you keep the current unity8? [13:17] not sure what else might have landed [13:17] Ouch [13:17] Crap, ok, too late :| [13:17] no worries [13:17] probably fine :) [13:39] Saviq: we have a problem with silo 007 [13:39] davmor2, hit me [13:40] Saviq: the phone never seems to time out and suspend after running 3 alarms, So it looks like the nested code might of crashed something [13:40] Saviq: phone has been on the apps screen now for about 10minutes [13:41] apps scope even [13:41] davmor2, huuumph, that's unexpected [13:42] kenvandine: hey, were you planning a landing today for u-s-s that my merge could go in with? :) [13:42] cyphermox_, i already have your branch in a silo :) [13:42] davmor2, the code there has nothing to do with any suspend logic :| [13:42] kenvandine: cool [13:42] davmor2, as it's unity-system-compositor that deals with that now [13:42] Saviq: only crashes are mtp, trust store and location so there is no powerd being killed [13:43] Saviq: and this only happened after the 3 alarms went off, prior to that it suspended [13:43] davmor2, looks to me like something's holding the screen on cookie [13:44] davmor2, AlbertA, is there any way to query the display state (and reason)? [13:44] AlbertA, like to check what's keeping the display on? [13:47] sil2100: can you confirm that lool's silo for the location stuff made it into rtm? [13:48] asac: it did not (yet) [13:48] asac: no, it's not yet tested [13:48] exactly [13:48] asac: but the silo has some packages in it [13:49] lool: run with it please [13:49] we are unblocked once this is in [13:49] for custom [13:49] sil2100: tx [13:51] sil2100: ok. it must be something delicate, possibly in version number handling / storage or something. [13:51] Mirv: it seems to be something with the PPA package fetching, parts that weren't touched in ages o_I [13:52] Mirv: i.e. the PackageInPPA class === om26er|afk is now known as om26er [14:02] sil2100: the only thing I see there in http://pastebin.ubuntu.com/8233668/ is that it introduces a new variable 'packages', but it shouldn't probably clash with anything? maybe a bit longer name would be better anyway [14:03] Mirv: doesn't look like it, I'm trying to sniff around for the cause still [14:05] - if not packages_not_in_ppa and not packages_building and not packages_failed: [14:05] + if not (packages_not_in_ppa and packages_building and packages_failed): [14:05] that's obivously wrong [14:05] obviously* [14:06] if not (A OR B) == if not A and not B [14:06] when refactoring for pep8 is nice, people should still be careful [14:06] Damn, Robert..! [14:06] didrocks: hah, love your keen eye for those ;) [14:07] sil2100: peer review would have avoided that, I bet :) [14:07] davmor2, is it reproducible? can you give me steps to repro? [14:07] didrocks: yeah, well, I would probably moan about it if I was to review the code, as I don't like the refactoring - in my opinion it makes the code less readable [14:08] ah, de morgan [14:08] sil2100: same here… and it screws as well bzr blame [14:08] sil2100: but review the code… keep telling you that :p [14:08] and offered my help multiple times [14:08] anyway, another topic [14:08] didrocks: yeah, well, it was robru's change anyway and I wasn't asked for a review ;) [14:09] It was happening during my night too! Couldn't even notice! [14:09] sil2100: pushing the change [14:09] Saviq: I can reboot and see if I have the same issue. But basically I installed the silo set three alarms for the same time let the phone suspend the 3 alarm notifications display I dismissed all three and that was it in that state [14:09] didrocks: thanks :) [14:09] yw :) [14:09] * sil2100 gets back to rebasing his branches in progress to the recent changes [14:10] It's also another thing that such changes make much more complicated [14:10] sil2100, how come it's fine that robru (or others) commit changes to production code without review? [14:10] that seems buggy [14:12] seb128: yeah, we need to get this sorted out - normally other than bugfix changes have a test-period in preprod too, which didn't happen here [14:12] seb128: and I think especially when you didn't author the code and the author keeps proposing about reviewing the changes :) [14:14] sil2100: pushed btw [14:14] davmor2, that sounds totally unrelated to what the silo brings... I'll try out here [14:14] Saviq: the three alarms tests the nest notifications right? [14:15] nested even [14:15] Saviq: after reboot screen blanks I'll trigger the three alarms again [14:16] davmor2, no [14:17] davmor2, nested prompts are when you go to a paid app not having an U1 account [14:17] davmor2, then the pay ui displays and triggers the account prompt [14:17] davmor2, see https://wiki.ubuntu.com/Process/Merges/TestPlan/pay-service [14:18] davmor2, there's nothing like "nest notifications" [14:20] Saviq: hmm okay, in that case a found a different bug [14:21] Saviq: you know you only set unity8 as things to test though right hence the confusion nested prompt the only thing I could think of was it was a proper fix for the multiple notifications :( [14:26] sil2100: could you help me to understand what blocks the UITK here http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html ? [14:26] Mirv: ^ [14:27] bzoltan: yeah, so it's what Mirv mentioned in the morning... [14:27] bzoltan: we need qml-module-qt-labs-settings to be included in main :| [14:27] sil2100: What that `out of date` means and who will do what and when? [14:28] sil2100: and who should/could do that? [14:28] bzoltan: because of the bug in CI Train the packages got pushed to the archive as source packages, so they started building there... and there it popped up that we're missing a package in main to actually correctly build it [14:28] bzoltan: Mirv poked on -release, not sure if he got any news on that [14:28] Mirv: ^ ? [14:29] bzoltan: we need to fill in a MIR for it [14:29] Not sure if Mirv did that [14:29] Let me make sure [14:29] sil2100: I have no idea what MIR is [14:29] bzoltan: Main Inclusion Request [14:30] bzoltan: anyway, we'll have to do that if anything... it was an old issue that was not noticed since we build all packages in the silos usually, and those don't have those blockades :| [14:30] sil2100: who should/could do that? [14:33] bzoltan: ok, I see we don't need a MIR probably [14:33] Let me re-ping someone === Ursinha changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ♫ I feel more awesome than an awesome possum ♫" === Kaleo_ is now known as Kaleo [14:35] sil2100: I am happy to do whatever it takes. just ping me if I need to fill something or do something. [14:37] bzoltan: hah, ok, that was fast ;) [14:37] davmor2, I'm looking at rtm#16 without silo 7, same behavior [14:38] davmor2, whatever woke up the phone for the alarms is holding the display on [14:38] davmor2, you can see by going "powerd-cli display on", if nothing held the screen on, it'd be cookie 0 (or 1, don't remember) [14:38] charles: ^ [14:38] davmor2, it's cookie 3 for me [14:39] sil2100,bzoltan: it's done; builds should auto-retry in a bit (publisher plus half-hourly cron job) [14:39] Saviq: no worries I'll carry on testing now then, thanks for the help debugging though [14:41] pmcgowan, bfiller: is there a reason that notes is still in the image I thought it was being dropped? [14:45] davmor2, we are currently discussing, will probably drop it fro image and CI [14:47] would someone have the snippet for uploading to RTM PPAs? [14:49] [ubuntu-rtm] [14:49] fqdn = upload.ubuntu.com [14:49] method = ftp [14:49] incoming = /ubuntu-rtm [14:49] login = anonymous [14:49] lool, ^^ [14:50] ogra_: does that work with PPAs? [14:50] lool, ah, no ... that needs extra runes ... i just modified my ppa entry in dput.cf [14:50] [ppa] [14:50] fqdn = ppa.launchpad.net [14:50] method = ftp [14:50] #incoming = ~%(ppa)s/ubuntu [14:50] incoming = ~%(ppa)s [14:50] login = anonymous [14:50] .... [14:51] needs the ubuntu dropped there [14:52] cjwatson: thank you [14:52] ogra_: you know they invented this thing call paste.ubuntu.com to save flooding channels ;) [14:52] sil2100: I am in the middle of the RTM validation, so no problem yet [14:52] davmor2, thats boring and wouldnt annoy you as much :P [14:52] (sorry) [14:53] ogra_: hahaha [14:53] lool: the dput in trusty-proposed/utopic doesn't need manual changes there [14:54] I'm using dput-ng actually [14:54] since a couple of weeks [14:54] ah, somebody should probably update that, since I didn't [14:54] oh, so modern ! [14:54] I think I was subject to propaganda from planet debian prior to debconf [14:54] oh, actually, ScottK already did [14:54] it seems to have fairly trivial to convert json files [14:54] so likewise, you need either utopic or trusty-proposed of dput-ng [14:54] oddly, it didn't complain about 14.09 though [14:54] I have utopic version [14:55] dput(-ng) doesn't know how to complain about that [14:55] am I supposed to uplaod to ppa:ubuntu-rtm/owner/name ? [14:55] the lookup is up to LP [14:55] ppa:owner/ubuntu-rtm/name [14:55] ok; I'll drop my customizations then === boiko_ is now known as boiko [14:55] https://launchpadlibrarian.net/179794265/dput-ng_1.7_1.7ubuntu1.diff.gz looks right [14:55] sil2100, can you help me find the .deb for the latest version of unity8-autopilot in utopic? [14:56] cjwatson: I thought /incoming would be /ubuntu-rtm rather than /ubuntu [14:56] sil2100, it's for the AP issue [14:56] brendand: latest in utopic? apt-get download unity8-autopilot doesn't work? [14:56] well I guess that's still valid for uploads to ubuntu-rtm [14:56] sil2100, but i'm running rtm :) [14:56] sil2100, i just want to install that .deb to make sure it fixes the issue [14:56] brendand: ah ;) [14:57] sil2100, anyway my hands are free now i think i can look [14:57] sil2100, but if you know of the top of your head that would be useful [14:57] brendand: so, you can use that command on your desktop and then adb push maybe? But in case you need the link itself, I can provide it :) [14:57] sil2100, ah yeah good point [14:57] brendand: https://launchpad.net/ubuntu/+archive/primary/+files/unity8-autopilot_8.00%2B14.10.20140903.1-0ubuntu1_all.deb <- but the link just in case [14:58] Saviq, davmor2, you say the alarm wakeup isn't releasing its "display on" cookie after the alarm is dismissed? [14:58] charles, that seems to be the case, yes [14:58] brendand: so you think we need those with the latest Mir? :) [14:58] charles: after several alarms I was using 3 at the same time [15:00] * Saviq tries with 2 now, phone started suspending again after a time [15:00] Saviq, davmor2, so to reproduce this, I just need to set an alarm, let it go off, and then the screen won't timeout to black on its own? [15:00] charles, current confirmed case is 3 alarms at the same time, all dismissed [15:00] charles: 3 alarms at the same time [15:01] davmor2, Saviq, ack I'll try that [15:01] didrocks: hey! Do you know if dch can be somehow forced to increment an already released top-most version instead of appending a new entry? ;) The manual doesn't say anything about that [15:02] davmor2, Saviq, what image are you testing with? [15:02] charles, rtm#16 on krillin [15:02] Saviq, thanks [15:03] charles: ditto [15:06] brendand: sil2100: ogra_: I'm trying the https://launchpad.net/ubuntu/+source/unity8/8.00+14.10.20140828.1-0ubuntu1 based debs on top of rtm right now after successfully reproducing it at home with the older one [15:06] bzoltan: sil2100: I didn't get anyone back on the release channel [15:06] plars: ACK :) [15:06] brendand: sil2100: ogra_: I suspect we're just going to need an updated unity8-* in rtm to fix this [15:06] Mirv: no worries, cjwatson already picked it up [15:07] there were some critical fixes that were still outstanding [15:07] plars: that would be good to hear, since we have some landings ready with that [15:07] sil2100: yeah, I read, that's what I thought would happen eventually. great! [15:07] plars: brendand was checking that as well [15:07] sil2100: brendand: ogra_: ok, confirmed... I'm watching an autopilot test run right now with that combination - successfully unlocked [15:08] plars, thanks [15:08] plars: excellent [15:08] Too bad the mir deps didn't mention that it required the new unity8 [15:08] plars, brendand: thanks guys! [15:08] plars, oh, awesome ! [15:08] davmor2, charles, yeah, killing datetime service makes it suspend again [15:08] charles, 2 alarms were enough here [15:08] probably a leaked display hold [15:09] * Saviq tries 1 [15:11] Mirv: I didn't notice your earlier query because jetlag, basically [15:12] sorry about that [15:12] cjwatson: no problem, I didn't expect you to be around with that amount of jetlag anyway [15:15] davmor2, charles, if I use just one alarm it's all fine, so it seems like there's a hold per alarm set up, but only one gets cleared [15:16] Saviq: that sounds like a good possibility [15:21] Saviq, davmor2, just FYI, I'm seeing it too. Haven't tracked it down yet [15:21] davmor2, is there a ticket for this yet? [15:21] * charles remembers who he's talking to. of course there's a ticket. [15:22] davmor2, what's the bug # for this? [15:22] charles: not yet but I can trigger one in a minute [15:24] sil2100: didrocks, about the pep-8 changes... it's long due [15:24] sil2100: didrocks, I haven't contributed much with that because I just can't read that code [15:24] so better now than never [15:25] Ursinha: well, not sure if this time is good for it since we have still some RTM changes to do, and it's breaking the standard workflow [15:25] Ursinha: I would expect such changes to happen later and most probably discussed [15:25] Ursinha: when there's no haste [15:26] sil2100: but why is that breaking the workflow? the changes introduced/revealed bugs? [15:26] Ursinha: yeah, it broke one thing, but also I have a lot of branches that are work-in-progress, and such big changes require me to manually rebase to make them mergeable again ;) [15:27] Ursinha: as it completely changes the layout of the code basically [15:27] Ursinha: (not to mention my personal opinions about code-readability in this form ;D) [15:27] sil2100: maybe you should coordinate a bit better with robru as he's working with you on citrain and I assume your changes might break his as well? :) that's an honest observation [15:27] sil2100: there should be absolutely no arguing about using pep-8 when coding python, but that's my personal opinion :) [15:28] Ursinha: I always inform about features I develop on meetings, so robru is aware of anything that I implement ;) [15:28] I never push out something without telling about it first [15:28] While this, well, I didn't hear anything about it - Robert only informed me about unit-test work he'll be doing [15:28] sil2100: I dunno, on several occaisions I woke up to find NameErrors in your production code [15:28] sil2100: informing isn't coordinating :) I'm not saying you are doing it wrong, but as we have more than one person working on the same codebase that is something nice to think about [15:28] robru: that was a bugfix going wrong [15:29] robru: it's hard to inform about every hotfix I'm doing ;) [15:29] sil2100: the reality is that our timezones are so different, we're going to always be working while the other is sleeping. please don't complain about work I do while you sleep :-P [15:29] robru: just tell me you intend to do such big changes! It's not a 10-line diff, it's OVER 9000! [15:29] ;) [15:30] sil2100: today I'm going to implement a pyflakes checker [15:30] and if I have time I'm going to widen the pep8 checker to the whole tree, not just citrain/ directory [15:30] it got me thinking, sil2100, how many branches do you have in progress at once? that's crazy to do when you're not the only one modifying the code [15:30] Ursinha: well, I don't say I miss coordination, I miss being informed [15:30] charles: https://bugs.launchpad.net/indicator-datetime/+bug/1365557 [15:30] Ubuntu bug 1365557 in Indicator Date and Time "Multiple alarms set at the same time trigger the screen to nolonger blank" [Undecided,New] [15:30] Ursinha: currently there are 3 branches [15:31] Ursinha: and usually I was the only one working on CI Train code so I just got used to that ;) [15:31] sil2100: the rest of us miss coordination because you both need to change that code and if you don't coordinate things break and we all suffer :) that's my point [15:32] Ursinha: I only know about me and robru as the ones doing changes in CI Train code, with me tweaking on it for the most recently - if I'm not aware of anyone else working on something I don't coordinate because I don't know who to coordinate with :) [15:32] sil2100: something strange with silo rtm-11 it appears assigned to me in the spreadsheet and the dashboard for push-client but it seems to contain system-settings instead [15:32] Ursinha: in the past it was only didrocks doing uploads [15:33] ralsina_: ah, it might have been freed in the meantime, one moment ;/ [15:33] * sil2100 again couldn't finish his branch with improvements here [15:33] sil2100: cool, I was away for a couple of days, so I could just start another landing later, no big deal really :-) [15:34] sil2100: I know, but now there is you and robru working on it (and could be more people)... all I'm saying is that's maintained by more than one person now and needs some change in the "process", to avoid things such one breaking the other's work [15:34] specially considering you both live in such different timezones [15:36] Ursinha: I agree here indeed, that's why I actually mentioned that I would like to be informed about if any changes are to be made so I can prepare myself [15:36] Ursinha: especially big ones [15:36] sil2100: fair enough [15:36] Maybe not any changes, but big ones for sure! [15:37] sil2100: but let's not disagree on pep-8 and pyflakes :P [15:38] Ursinha: I'm not a pythonist, I will just leave it up to you and robru with the expertise here ;p I'm just saying that the style is not completely good for me eyes! [15:38] unless you have a superwide ultra high resolution monitor, having that crazy long lines is impossible to read :) [15:39] sil2100: yeah, I'm not sure what your problem is with pep8, but it is the Gold Standard for writing python code that is actually readable by other python programmers. so this change made a huge positive impact on readability for potential future maintainers of this code (including myself). Now that I can actually read what's going on in the code I might be [15:39] able to contribute more going forward. [15:39] ralsina_: you needed ubuntu-push there, right? [15:39] sil2100: yes [15:40] robru: yes yes [15:40] robru: good to know, well, I must say that for instance I like wrapping lines only when it makes sense, not like for every argument if the list is bigger [15:40] robru: since my eyes work pretty good on things that are a bit 'wider', in like one line [15:41] thostr_, 'powerd-cli test' fails one test with silo 13 [15:41] charles, ^ [15:42] sil2100: not sure how that can be -- it's clearly easier to scan down a straight line than to read things from a cloud-jumble that spans vertically and horizontally [15:42] sil2100: it's hardcoded in my brain that the only width that makes sense is less than 80 chars :P (which might be a bit outdated, I know, but this is how a pythonist learns to read code) [15:43] sil2100: also like, the absurdly long lines found in citrain would wrap on my screen and break the flow of the python indentation. you need to be able to see the indentation clearly to understand the structure of the code. are you reading the code in a maximized widescreen window? because I split my widescreen in two columns (still over 100 chars wide!) but [15:43] citrain code wrapped so badly. there were lines that wrapped *TWICE* on my screen, totally illegible [15:43] sil2100: and now for something slightly different: how do you handle external contributions to cu2d? do people need to come to you and request review, how does that work? [15:43] Ursinha: I don't think we've had an external contribution since april ;-) [15:43] Indeed ;) [15:44] let's say I want to contribute, what I have to do? [15:44] robru: well, I think citrain suffered from the editor syndrome! [15:44] ogra_: sil2100: how soon could we expect to see a rebuild with the updated unity8 bits? [15:44] *do I [15:44] sil2100: btw I'm going to try to resurrect this one at some point: https://code.launchpad.net/~mathieu-tl/cupstream2distro/cleanup-on-kill/+merge/213728 [15:44] robru: since on my sublime editor the code was perfectly readable [15:44] sil2100: send me a screenshot :-P [15:44] robru: one moment ;) [15:45] I use vim :) even on the best editor ever you still have the screen size limitation, that's why I don't understand [15:45] many parts of the code seriously exceed my widescreen monitor on its highest resolution :) [15:45] Ursinha: he must have a 30" screen so he can display the full length of the lines without wrapping ;-) [15:45] or maybe a 30' screen... [15:46] I used vim previously, but then noticed the wonders of sublime and use it for code mostly ;) [15:46] robru: add a pep8/pyflakes test for anything landing in citrain :) [15:46] Damn, I'm surrounded by pythonists! [15:46] Get away! Shoo! SHOO! [15:47] ;) [15:47] sil2100: man, that's ubuntu land, we're mostly pythonists :P [15:47] sil2100: seriously, I used to think pep8 was a waste of time many years ago until I worked with james_w and salgado on a project and they insisted it was a good idea to enforce it from day 1. I'm a convert now [15:48] * sil2100 is a C person [15:48] * sil2100 is soo oldschool [15:48] sil2100: I also code in C, but when I code in python I do that like a pythonist [15:48] I wouldn't dare to write C code like pythin [15:48] python [15:48] plars: that's what this flamewar is about! I just implemented a hard requirement on pep8 yesterday and I'm doing pyflakes today [15:48] robru: awesome! [15:49] plars: thanks, yeah I agree the code was a disaster, totally unreadable [15:49] sil2100, feel lucky that robru doesn't apply hyper-pep8 [15:49] I haven't really looked at the citrain code, but if I get some spare cycles, I'd be happy to help bring it into compliance if some of that is still needed [15:49] sil2100, where people start bringing you up on pep8 'violations' that the tool doesn't even check [15:50] sil2100, and sometimes even decide to interpret pep8 in their own special way [15:50] :) [15:50] Yeah, I might have to read up on all of this, please remember that my Python experience is limited [15:50] plars: robru will certainly love you :) [15:50] Before I only used it for advanced scripting purposes and autopilot [15:51] brendand, looking at it [15:51] robru: http://people.canonical.com/~lzemczak/subl.png [15:52] sil2100: that's okay, I wasn't born knowing perfect python (I still don't have perfect python), but thing is always try to improve your techniques :) I know change is hard, but some are for the greater good :P [15:53] Ursinha: ^ he has wrap turned off... [15:53] sil2100: ah, having a line broke with "\" usually means something is clearly wrong that even one with high tolerance to long strings is bothered [15:53] robru: to me that would be even worse [15:54] imagine having to roll the screen horizontally? [15:55] hah, I have wrapping enabled sometimes [15:55] sil2100: Ursinha http://i.imgur.com/Jm1pU4l.png before and after. [15:55] Damn imgur doesn't work for me today [15:55] Ok, but anyway, I go back to code [15:57] left image makes me feel good [15:57] sil2100: ok anyway, I have an idea that can help strike a balance here. if we move the definition of the super-long strings to the top of the file, they'll be less indented and thus require less wrapping. and then in the code we can just reference them as global variables, which will fit easily on one line. That way we get a nice win/win of less wrapping, [15:57] but still shorter lines, and better readability. [15:57] s/left/right/ [15:57] robru: yes, e.g. moving predefined messages there and use the variables [15:58] robru: well, I don't mind it being as it is now, since I guess that's the standard - just saying that it's not good for my eyes ;) [15:58] sil2100: you'll get used to that, I promise :) [15:58] robru: it might be because I sometimes work with code in 'blocks', and I got used to the blocks as they were, while now it's different - will have to get used to that [15:59] I liked to it as the author meant it [16:00] sil2100: yes, I work with the code in "blocks", and the blocks were impossible to read because all the wrapped lines made it impossible to scan the indentation and see the structure of the file ;-) [16:00] hah, yeah, I got used to it and was able to work with it :) Maybe my brain was somehow compatible with that [16:01] sil2100: I don't know how sublime works but it might have a pep-8 plugin that can help you there [16:01] sil2100: I have that enabled on my vim and I can check it easily [16:02] plars: pong! [16:02] sil2100: oh, brt [16:16] there shouldn't be hot fixes in the train code as there aren't hot fixes in the actual product [16:21] sergiusens, but it makes the whole thing so much more exciting ! [16:23] lol [16:23] sil2100: autopilot went to pep8 conversion after we started clickifying too ;-) [16:24] 80 line limit makes 3 way merges faster to read as well [16:24] just use the coding standard of the language [16:27] fginther: how much chaos would it create for you if ogra_ lands the adb changes today? [16:27] psivaa: ^ fyi - I'll handle the remaining 2 changes or so that we need for ubuntu-device-flash to pass it the --password option and use the new password in the sudoers setup script [16:29] plars: ack, thanks. let me know if i need to review anymore of those. [16:29] plars, today is as good as any [16:29] sergiusens: hah, nice, it seems I missed out all the pep8-bits in python projects ;) [16:30] fginther: I'll cc you when I have a branch so you can make sure to pick up those too, will probably be just a couple of lines [16:30] plars, thanks [16:30] sergiusens: since I was playing with autopilot while it was still as it was before [16:33] trainguards: can you please restart this build https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-019/+build/6321642 [16:33] Saviq: sure [16:34] Saviq: done [16:34] Saviq, sil2100: finally silo 007 is ready to rock [16:34] davmor2: \o/ [16:34] davmor2, good stuff [16:34] robru: I'll publish that ^ [16:34] kgunn, ↑ [16:34] plars: could you check why not all the browser tests are running? [16:34] sil2100: ok [16:34] and balloons: could you release a new reminders version to the store so it doesn't get stuck anymore. [16:34] ? [16:34] elopio: none of the autopilot tests are running due to the screen unlock problem [16:35] robru, Saviq, davmor2: published [16:36] elopio, plars reminders was released yesterday right after it merged [16:36] music app and terminal also got updates [16:37] balloons: awesome! [16:52] balloons: thanks. [16:52] Ursinha: robru: sil2100: anyway, my only point is that as you don't really know the code, you should do peer reviews. if you change the logic and not only the wrappig like here, you should double check. (on another note: don't disable tests if you make a change that don't make them passing). That's more best practice than pep8 IMHO [16:52] plars: I didn't know there was a screen lock problem. So I'll check again after that is solved. [16:56] didrocks: yes my intention is to review the disabled tests and fix them correctly. it's just that I wanted to gate MPs on the unit tests ASAP and you can't do that if you have a bunch of failing ones. [16:57] yeah, would have been better to not break them first but oh well :) [16:57] robru: but still, I'm serious, peer reviews, the code of fix that I had to do shouldn't happen if the change is being seriously reviewed [16:58] didrocks: yeah I agree, would have loved to not break it in the first place, but here we are... :-/ [16:58] didrocks: also peer reviews are nice, but will cripple our team. sil and I are in such different time zones, every small change would take 2 days to ping back and forth with reviews. [16:58] didrocks: so at least we can settle for auto-reviews from jenkins [16:58] but Ursinha canhelp, right? [16:58] can* [16:59] didrocks: Ursinha is afraid to look at the code... well maybe now that we have pep8 she can help more ;-) [16:59] didrocks: also Ursinha is in my timezone, so we have nobody to review for sil [16:59] "afraid"… ok [16:59] I did propose to help in peer reviews multiple times [17:00] didrocks: seriously the code was unreadable before pep8, and Ursinha agrees. it's the main reason I haven't contributed much yet, because i literally could not read it as it was. [17:01] robru: rather than waited then, pep8 fixes could have come way better [17:01] It's funny to see the ranting when the origin of the discussion is a stupid simple logic error which has nothing to do with pep8 when the refactoring was done here [17:02] I'm not afraid to look at that code, I just fear I'd break something because that's really hard to read and not all tests pass [17:02] didrocks: right, I made a small logic error at the same time I was doing pep8, sorry for that. [17:02] Ursinha: all tests did pass when I left, for the record [17:02] didrocks: I caught at least twice tests not passing on trunkl [17:02] Ursinha: on which revs? [17:03] I'm not pointing fingers, that wouldn't help us here, I'm only saying I didn't want to break anything as that was production [17:03] didrocks: dunno, you had some special mojo for running the tests or something. I never saw tests passing at any point. [17:03] I entirely agree on peer reviews, although I will say that large refactoring commits often receive only very cursory review, out of necessity - one reason for the religion of trying to split up commits into logical pieces as much as possible [17:03] robru: you never told me that tests never passed for you, not sure how you did tests your changes in the past then [17:03] robru: but you should have asked me, and this offer still stands [17:04] didrocks: a while ago, I pointed the problems to sil2100 and he worked on fixing one of them.. my point is that if we had tarmac or something to gate that these would have been caught earlier, and that's fine, we're improving this all as we move, right? [17:04] didrocks: that's the point. I never tested changes ever. neither did sil. we've been live-editing production since you stepped down. [17:04] Ursinha: agreed on having a bot to perform the merges [17:04] robru: hoping you will go to better practice now then [17:04] I think I commented on the tests being broken when I last had occasion to change citrain; I made sure that the tests passed in the region I was working on and that I didn't regress anything, but I wasn't in a position at the time to go and drain the swamp too [17:05] didrocks: again, I'm not pointing fingers, I'm explaining one of the reasons why I have avoided touching the code [17:05] (and I did add a test for the thing I was doing) [17:05] I was in a very similar position as cjwatson [17:05] didrocks: yes, I worked long hours yesterday to implement autolanding for lp:cupstream2distro, gated on tests passing, and with code style quality checks so that the code can actually be enforced to be readable ;-) [17:05] I fixed the test in the area I was working on but it would take me more than that to fix it all [17:06] cjwatson: yes I remember vividly you wrote some tests but complained of dozens of test failures. I was afraid to even look. [17:06] I didn't have a problem running the tests, though, and the errors I could see didn't look like test runner issues, they were just buggy tests or similar ... [17:06] cjwatson: integration tests that needs a special setup, right? [17:06] but it was a while back [17:06] cjwatson: thanks a bunch for the tests you did write [17:06] didrocks: well, I didn't do a full search, there may have been some of those, but some things were just busted with no good reason [17:07] Ran 198 tests in 17.027s [17:07] rev 590 (the last one I touched) [17:07] that was in July though [17:07] then, integration tests needs a pbuilder [17:07] robru: yesterday pretty sure ubuntu-keyboard got published to both ubuntu and ubuntu-rtm but only seeing it on ubuntu 0.99.trunk.phablet2+14.10.20140902.1-0ubuntu1 [17:07] robru: can you check on it's rtm status? [17:07] didrocks: you've been away for a while and I'm sure people did what they could to learn the codebase and keep up [17:07] cjwatson: yeah, but as the discussion were "we didn't touch the tests because they never passed", I wanted to answer to that [17:08] Ran 81 tests in 10.077s on integration tests [17:08] bfiller: speaking of which, your query about the initial RTM sync was escalated to me, but it doesn't look like you responded to https://lists.launchpad.net/ubuntu-phone/msg09627.html [17:08] bfiller: indeed rtm is behind, not sure why, hang on [17:08] however, you need to have this pbuilder setup locally [17:09] didrocks: I never knew how to setup the env to run the integration tests [17:09] cjwatson: yeah it got resolved as we released another version of the package that got synced to both [17:09] Ursinha: you never asked AFAIK :) [17:09] but I can help you tomorrow if you need [17:09] didrocks: I did, a long ago :) [17:09] didrocks: are there instructions on how to set up the pbuilder anywhere? can you perhaps write a script that automates the creation of that pbuilder environment so people other than you can run those scripts? [17:09] cjwatson: sorry didn't response [17:09] robru: I'm happy to guide you to do it [17:09] didrocks: again, I'm not complaining, just saying I couldn't find docs or anything to learn how to do that [17:09] bfiller: ok, so it was just that package and not others? [17:10] didrocks: and that would help people to be able to fix tests if they could run them [17:10] cjwatson: that package was the only one that I knew about [17:10] ok [17:10] Ursinha: they could ask as well, not like IRC was a wall :) [17:10] and then, that help building the doc which wasn't there [17:10] didrocks: man, do you understand my point? [17:10] cjwatson: oh, are you syncing it? or should I set up a silo to sync it? [17:10] I'm saying that is one of the reasons, and that's about it [17:10] that only means we should fix that [17:10] *we* [17:10] robru: no, just following up on an older thread [17:11] bfiller: what are the source package names that are missing? just ubuntu-keyboard? [17:11] Ursinha: I do, do you understand that telling "I didn't do anything because there was no doc and I was afraid to look at and never asked for this" is kind of a weak argument as well? [17:11] Ursinha: hence the "if you need help, I can help you guiding" [17:11] and what I always told since I left here [17:11] robru: actually ubuntu-keyboard-* there are like 20 of them. I can get the exact names if you'd like [17:11] didrocks: I asked for this, but as the other people here we have plenty of things to do, so I'm kindly suggesting "let's write docs" [17:11] didrocks: ok, please when you get some time (tomorrow) I'll appreciate an email with step by step instructions of what commands to run to create the pbuilder necessary to run the integration tests. [17:12] robru: sure, if you remind me in any way, I'll do it [17:12] bfiller: no no those are the binary package names. they all come from ubuntu-keyboard I think. [17:12] hmm, it'd be useful if I set up some way to get rmadison output for rtm, wouldn't it? [17:12] robru: http://pastebin.ubuntu.com/8242325/ [17:12] didrocks: well you should write a note for yourself, I won't wake up until your shift is over and you'll be out of time again... [17:13] bfiller: we always want source package names for this kind of stuff really [17:13] robru: I have a note for now, but ping me in case you don't receive anything [17:13] didrocks: ok thanks [17:13] cjwatson, robru: yup, ubuntu-keyboard is the source pkg [17:13] yw [17:14] sil2100: what's the syntax for syncing from utopic rather than a silo? 'sync:utopic,something-something source_package_name'? [17:14] ok, rmadison shows ubuntu-rtm/14.09 now [17:14] cjwatson: thanks [17:14] robru: it's 'sync:distro,series package package' [17:15] robru: so sync:ubuntu,utopic foo bar [17:15] didrocks: you can check your pvt logs, we discussed integration tests on 2014-05-02 as I couldn't find instructions on how to do that... so don't say I never asked, please :) [17:16] sil2100: thanks [17:16] bfiller: ok, new ubuntu-keyboard building in rtm 16: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/2/console [17:16] Ursinha: right, and I answered you [17:16] finishing up with "do not hesitate if you have any question!" after you saying you are looking to it :) [17:16] so, I assumed you set it up :) [17:17] robru: thanks [17:17] bfiller: you're welcome! [17:17] didrocks: you had no obligation of checking back if I got there or not, I'm only saying I did ask due to lack of docs, that was my point the entire time :) [17:17] so let's write docs now and we'll all be happy and fine [17:18] Ursinha: agreed [17:19] robru: actually, I gave the command to create the setup environment [17:19] chroot-tools/.pbuilderrc [17:19] robru: # Just use it to create the cowbuilder with: sudo HOME=. DIST= cowbuilder --create --debootstrapopts --variant=buildd [17:19] and that should be enough (with pwd=chroot-tools) [17:20] robru: let me just find which dist I used for those tests (that will maybe need to be adapated, to be more generic will be better) [17:20] didrocks: I guess raring, I saw that a lot in the tests [17:20] robru: yeah, I would say so, let me confirm, one sec [17:21] * robru needs some breakfast [17:21] robru: right raring, I have in ubuntu-developer-tools-center a better way for having a "fake" distro, you can maybe get some inspiration from there [17:21] robru: enjoy your breakfast! [17:26] are we using the train to land train changes? [17:26] that would be fun [17:27] fun for me to watch, of course :-) [17:27] rsalveti: thankfully it's not self aware [17:27] rsalveti: but we are at least now gating MPs against citrain so that they don't regress citrain's own tests. [17:27] robru: right [17:28] yeah, the pep8 discussion was a bit surprising, we got a bug, sure, but just fix it, no big deal [17:28] It wasn't a discussion, no worries, since no one was discussing if the pep8 switch is necessary or not [17:29] It was more like about communication (that we will now communicate better) and about taste ;) [17:29] rsalveti, trainspotting ? [17:29] right [17:29] ogra_: :-) [17:30] * ogra_ thinks we need to re-define the line length for pep8 anyway so code fits in the terminal app [17:31] ogra_: I think that was under discussion a while ago [17:31] As pep8 is the right way to go from what I see and I can understand that, as I was a great zealot of writing C code complying to ANSI C in my old days ;) [17:31] turning it to 20chars ? [17:31] :) [17:31] ogra_: ;p [17:31] ogra_: what terminal size are you using man ;p [17:31] sil2100, whatever fits on my phone screen :P [17:33] 80 columns is fine unless you're doing c++ [17:33] for c++ you need like 280 [17:33] or more [17:33] 480 [17:35] sil2100: thanks for understanding :) [17:35] * Ursinha hugs sil2100 [17:36] * sil2100 just needs to adjust his eyes to a new coding style [17:36] * sil2100 hugs Ursinha [17:36] ;) [17:36] :) [17:36] sil2100: the other benefit of 80 char lines is that you can have two windows side by side on the same screen... or one editor window and one terminal window... or two terminal windows. both unity and gnome-shell have great half-maximization features for getting windows perfectly side-by-side tiled ;-) [17:36] robru, get a modern laptop/monitor :P [17:37] * ogra_ can fit 4 terms with 80 chars in a row on his lappie [17:37] ogra_: 27", two terminals side by side are about 110 characters wide each. citrain code had lines so long they wrapped twice. that's like 300 char lines in python. [17:37] (well 3.8 ) [17:37] haha [17:37] ok, thats quite long [17:38] ogra_: I guess you didn't see this earlier ;-) http://i.imgur.com/Jm1pU4l.png [17:39] wow 1 [17:39] ! [17:42] trainguards, https://ci-train.ubuntu.com/job/ubuntu-landing-019-1-build/23/console says SUCCESS, but spreadsheet says some packages failed ¿? [17:42] robru, oh, all the wasted space on your right terminal ;P [17:43] Saviq: not wasted, it's called a margin, help readability. there's a reason books don't print words right to the very edge of the page :-P [17:43] robru, but not half of the page ;) [17:44] robru, don't get me wrong, I'm all for wrapping, but 80 columns is just so 1990 [17:44] even with two terminals as you have them, 100, even 120 would be good enough [17:44] Saviq: I admit 100 could be ok, but I just wanted to follow a standard [17:44] grr ^W [17:45] Saviq: I admit 100 could be ok, but I just wanted to follow a standard [17:45] robru, yeah yeah, I know [17:45] davmor2: you around [17:45] 80 is just too limiting IMO, leads to very artificial wrapping [17:46] Saviq: you are a C++ programmer, I presume? :P [17:46] fginther: any idea what's going on here? https://code.launchpad.net/~rpadovani/reminders-app/bottomEdge/+merge/231118 - see last comment [17:46] * kgunn wants to put Saviq and duflu in cage match fight over 80 col use [17:47] Saviq: hmm, where do you see packages failed in the spreadsheet? it's line 45, right? [17:47] popey, looking [17:48] Ursinha, hmm it must've updated now [17:48] Ursinha, it was weird 'cause it said "Packages built\nSome packages failed to build" in the dashboard, but yeah, good now, sorry for the noise [17:49] Saviq: no problem, that's a weird error if all packages built, thanks for letting us know anyway [17:49] Ursinha, I tend to think of myself as a pragmatic programmer :P [17:50] :P [17:50] I agree 80 might be outdated, but as robru I like standards :P [17:50] better than no standards :) [17:51] Ursinha, and having to wrap like what you see at the end of https://code.launchpad.net/~saviq/unity8/dash-geometry/+merge/233354 is IMO not pragmatic [17:51] nor does it help readability [17:52] Saviq: I'd wrap that differently :) [17:52] it's indeed confusing [17:52] Ursinha, wrapping after = \ is not that much better either [17:52] and sure, I could use shorter names, but that doesn't help readability either [17:53] Saviq: I'd start the line with a ( and put the rest in the next line, identing format parameters below that [17:53] Ursinha, standards, you said? :D [17:53] there are no definitive rules on how to do that, I just try to make it more readable, not only break the line when it reaches 80 for the sake of it [17:54] yeah, but it varies from project to project :) [17:54] there are the main standards and the project ones, Launchpad has a very nice styling guide for example [17:55] aaanyway... on another topic... [17:56] we seem to have an issue with changelogs in synced packages... we skipped one release into rtm (because they were close to one another) [17:57] and now the changelog is kinda weird because it doesn't include the previous release... [17:57] https://launchpad.net/ubuntu-rtm/+source/unity8/8.00+14.10.20140903.1~rtm-0ubuntu1 [17:57] wonder if the changelog rewrite should rewrite the changelog to include all the changed bits since last ubuntu-rtm release... [17:57] changelog rewrite rewrite the changelog, yeah, that's not confusing at all [17:58] that sentence could need another "rewrite" sprinkled in [17:58] or two .. or three [18:00] Saviq: oh yeah, when you see two different statuses like that in the dashboard, the smaller one underneath is just a stale one from the spreadsheet, which is slower to update. the larger, top one is considered canonical. [18:01] considered authoritative [18:01] robru, ktx [18:01] Saviq: you're welcome [18:02] kgunn: I am now] [18:03] sil2100: why did we land ubuntu-ui-toolkit without the -gles version? [18:06] rsalveti: we landed the -gles as well, at least it was published along with UITK [18:07] sil2100: hm, not in ubuntu [18:07] rsalveti: maybe it got somehow lost? Let me check [18:07] https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit-gles [18:07] hmmm [18:07] ubuntu-ui-toolkit-gles (1.1.1227+14.10.20140904-0ubuntu1) is in no known space (and time) [18:08] rsalveti: so, I see the rsync file had the -gles, so it either had to be rejected from the archive or something happened on snakefruit [18:08] https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/25/artifact/packagelist_rsync_landing-012-utopic/*view*/ [18:08] hmmm [18:09] Too bad we don't get e-mails if things get rejected [18:13] slangasek: hey! Do you remember if snakefruit had any logs of all the copy2distro runs it was doing? [18:16] sil2100: this wouldn't be something I would have known, but I could look [18:16] slangasek: I remember something like that, maybe it was didrocks that mentioned it one time in the past, hmm === om26er_ is now known as om26er [18:20] sil2100: well, the most recent log is always written to public_html, but http://snakefruit.canonical.com/~ubuntu-archive/cicopy.log is a 403 [18:21] sil2100: and I'm not finding any other logs here [18:22] slangasek: thanks [18:22] mterry: in the welcome wizard there seems to be a really noticeable delay in the in the number pad rising for the pin is this something you've seen? [18:22] I wonder what could be the problem, let me dig in further [18:23] slangasek: hm, could I ask you to put one file in snakefruit in a moment? I guess it might have been rejected because the -gles packages have some hacks in them, and in that case we were doing source copies [18:24] ok [18:29] slangasek: could you put this http://people.canonical.com/~lzemczak/packagelist_rsync_landing-012-utopic into the incoming/ directory? Don't remember where exactly it was on snakefruit, but I would guess somewhere in cu2d or something [18:29] slangasek: I once asked you for some rsync file uploads there so you'll probably know where that is ;) [18:30] sil2100: done [18:31] slangasek: thanks! [18:31] rsalveti: ok, let's see if it publishes it now [18:31] rsalveti: what I suspect happened is that it got somehow rejected as because of a small bug we published the source packages instead of the built binaries [18:32] davmor2, I bet that's because we restart maliit between those pages, so that it knows in which language to display the OSK [18:32] rsalveti: and as we know the -gles counterparts have some neat things inside to make the -gles sync easier [18:32] davmor2, probably something we could do to make that nicer [18:32] rsalveti: I can't tell for sure if that was it, but if it gets published now we'll know that something similar could have happened [18:32] (no logs of what happened) [18:45] rsalveti: ubuntu-ui-toolkit-gles (1.1.1227+14.10.20140904-0ubuntu1) is in the proposed pocket <- \o/ [18:47] sil2100: awesome, thanks! [18:49] rsalveti: yw! Thanks for noticing, didn't expect it to get rejected [19:01] sil2100: np [19:01] Saviq: The changelogs on Launchpad's distrosourcepackage pages have long been broken in that kind of way. I wouldn't advise putting any effort into working around it. If you look at the debian/changelog in the package, it appears to have the "skipped" release [19:02] slangasek: the URL is http://people.canonical.com/~ubuntu-archive/cicopy.log not snakefruit.c.c, but it only has the most recent attempt; I don't know of a historical log OTTOMH [19:03] Saviq: I might try making this better btw. as I can generate the package with a -v, but it might be a bit tricky due to some specific things we're doing for rtm [19:03] Saviq: but I'll keep that in mind [19:04] oh, it's true that -v might help [19:05] it's still an LP bug IMO, it could perfectly well work this out [19:06] (he says handwaving furiously; no doubt there are performance implications and I don't immediately know whether it would be the sort of thing that could only be fixed for future uploads) [19:06] kenvandine, silo 17 can publish [19:07] cjwatson: ack [19:09] sil2100, cjwatson, got it, thanks [19:12] pmcgowan: sorry I'm a little behind on the publishings, I'll get to that. [19:14] pmcgowan: eh, that branch has a Needs Fixing from seb and no further commits to fix seb's concerns. [19:15] pmcgowan, the MP still isn't approved [19:17] pmcgowan, a few hours ago seb128 gave it another needs fixing... [19:17] not sure if the issue he found was addressed [19:17] oh [19:18] pmcgowan, it was the same complaint seb had last week [19:20] sergiusens: you got utopic1 [19:21] ty [19:21] yw ;-) [19:24] bfiller: camera-app building in rtm8 https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/11/console [19:24] robru: cheers [19:25] bfiller: you're welcome! [19:26] pmcgowan, also... it looks like that silo needs to be rebuilt anyway [19:27] pmcgowan, the previous landing was merged into trunk an hour ago [19:27] kenvandine: ugh, can you pocket copy silo rtm16 into 14.09-proposed? citrain is too stupid to publish it: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-016 [19:27] but the ppa was rebuilt 4 hours ago [19:28] robru, are you sure it needs a copy? [19:28] and if so... how do i do that? [19:28] copy-package or something? [19:28] yeah [19:28] kenvandine: yeah, same way you'd ever upload anything to -proposed ;-) [19:28] oh... a dput? [19:28] kenvandine: I'm sure I could spend my entire shift debugging why citrain refuses to publish it since it's clearly built in the PPA. [19:28] i thought there was a fancy tool for it :) [19:29] kenvandine: I guess copy-package. i'm not a core dev, you should know this stuff ;-) [19:29] i've never done copies :) [19:29] kenvandine: yeah, it's just like... configged a silo for that one project, built that project, PPA clearly has that project built, bfiller tested it. go to publish "can't publish this! It didn't build!" yes citrain, I TOTALLY BELIEVE YOU. [19:29] a dput should work though [19:30] kenvandine: dput would work but you'd have to dget the package first. copy-package should be able to do it in one step [19:31] dput would also require a rebuild. [19:32] copy-package --from=~ci-train-ppa-service/ubuntu-rtm/landing-016 --suite=utopic --to=ubuntu-rtm --to-suite=14.09-proposed -b [19:32] make sure your lp:ubuntu-archive-tools checkout is reasonably up to date [19:33] ok [19:33] cjwatson, can i do copy-package as core dev? or is that archive admin? [19:33] anyone who can upload something can also specify it as a copy target [19:33] cool [19:34] (hence, self-service syncs from Debian - it's the same system) [19:34] yeah, i do those [19:35] in that case there's a special syncpackage tool for it, but it winds up as the same API calls. copy-package does less handholding but is more powerful [19:35] robru, done! [19:35] including the -b option which you need here to avoid rebuilding [19:35] cjwatson, thanks [19:36] np [19:37] huh, I said --suite=utopic which was wrong, should have been --suite=14.09. did that somehow magically work or did you correct my typo? [19:37] i did it right :) [19:37] i saw what you did there [19:37] oh good, reality is aligned with expectations [19:37] always nice when that happens [19:37] indeed [19:40] kenvandine: cjwatson: thanks [19:42] no! [19:45] ;D [19:46] Ok, I think it's time to EOD already, see you tomorrow o/ [19:58] Do we have a bug for the dash occasionally getting stuck in a permanent "still starting" loop? [20:15] robru, Can I get a silo for line 48 please? [20:20] tedg: ok you got 2 [20:20] no wait [20:20] crap [20:20] tedg: conflicts with silo 8 [20:21] Oh, uhg. [20:21] charles, ^ [20:22] I guess I'll mark that one as not ready until rsalveti's silo lands then. [20:22] tedg: poke rsalveti to test that ;-) [20:23] tedg: also one URL is a branch not an MP, please fix that. [20:24] robru, Oops, fixed. [20:26] pmcgowan, i kicked a rebuild of silo 17, since we know it's outdated anyway [20:26] kenvandine, why? [20:26] it hasn't been rebuild since the last settings landing [20:26] so it doesn't included everything that's in trunk [20:26] but we still need an mr fix right? [20:26] yeah [20:27] or at least some understanding of the problem [20:27] pmcgowan, did you test it? [20:27] kenvandine, no [20:27] ok [20:27] seb was seeing blank rows and such [20:27] dbarth, chatting about your mr, didnt work for seb [20:28] oh I did test it a while ago and saw similar, figured it was early days [20:28] dbarth, it was the same problem seb commented about on friday [20:32] pmcgowan: i saw [20:32] but i wonder if he tested the right packages [20:33] i re-tested with the packages from silo 17, and the 2 broken entries i had are now properly filtered [20:33] I can try it again once it builds [20:33] pmcgowan: the packages in the ppa should already work [20:33] dbarth, ok, it didn't look like the commits since his comment fixed that [20:34] the build was finished around 6pm CET this afternoon [20:34] yeah, just out dated [20:34] i imagine [20:34] dbarth, it finished 3 hours past the last merge to trunk [20:34] ? [20:35] theer was no merge, was it? [20:35] dbarth, kenvandine his comment is before jenkins made new packages [20:36] * pmcgowan gets the debs [20:36] i can confirm with him tomoow, but if we want to clear this silo, it's quick to check [20:36] ok [20:37] dbarth, we still need the rebuild, to get in sync with trunk [20:37] ah [20:39] oh so I should wait for the silo [20:41] dbarth, sorry, we kept on trucking with landings since your branch wasn't approved yet [20:51] kenvandine: ok, if it rebuilds, we can test soon anyway [20:52] dbarth, ok... i need to get a quick landing in front of you again... sorry [20:52] dep issue for rtm landings [20:54] kenvandine: it's a consipracy or what? ;) [20:55] dbarth, haha... sorry :) [20:55] ah hey folks [20:55] sorry I should have discussed this here [20:56] hey [20:57] kenvandine: do we need permission to go with this? [20:57] kenvandine: dbarth said it's ok to land this first [20:57] kenvandine: if you dont mind, would you land it? [20:57] lool, so to quickly handle this dep, i'll change the dep to add the ~ [20:57] yeah [20:57] lool, will do [20:57] just suffix the current one with a ~, that should work [20:58] and it's good practice all the time BTW, including in bdeps etc. [20:58] kenvandine: thanks! [20:59] lool, can you give me an approval on the MP? [20:59] lool, indeed [20:59] kenvandine: sure thing [20:59] Tweak the depends for accountsservice-ubuntu-schemas to handle a "~" version [21:00] whoops [21:00] https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/dep_tweak/+merge/233426 [21:00] copy/paste bug :) [21:00] lool, i'll jockey this through quickly [21:00] kenvandine: approved [21:02] lool, silo 11 [21:03] wow... right as 11 freed up :) [21:04] dbarth, after this lands and merges, i'll make sure your silo gets a rebuild [21:04] so it's ready for testing when you get up tomorrow :) [21:08] robru: It seems I no longer have write access to the spreadsheet. Could you add access for me, or mark row 39 as QA approved? [21:09] ToyKeeper: one sec [21:10] ToyKeeper: hm, it says it was shared with you already, are you perhaps not logged in? [21:10] Yes, it's possible. I was out for long enough I've had a bunch of sessions expire. [21:10] ToyKeeper: anyway i marked it as approved for you, if you still can't access after signing in, file that with RT or something, because that's just weird. [21:11] robru: Thanks. :) [21:11] ToyKeeper: you're welcome [21:12] kenvandine: cool [21:12] fginther: any progress? [21:12] kenvandine: thanks [21:12] dbarth, np... sorry for needing to jump in front :) [21:12] dbarth, you have a good night [21:12] ogra_: you gonna need RTM for that as well? [21:12] Huh, weird. SSO just responded in both english and in a language I don't recognize. [21:12] robru, yep [21:13] ogra_: ok you got utopic14 [21:13] thanks ! [21:13] popey, looks healthy again [21:13] popey, go for ti [21:13] it [21:15] ogra_: you're welcome [21:15] alright I gotta run some errands, back in an hour or so, cyphermox can cover landings if anybody needs anything urgently ;-) [21:16] o/ [21:18] fginther: kk [21:26] fginther, it seems the prints don't appear for the failures for python3; https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/fix-1359167/+merge/233387/comments/569665 [21:26] fginther: failed http://91.189.93.70:8080/job/generic-mediumtests-utopic-weather-app/90/console [21:27] does that need a merge from trunk? [21:36] tedg: robru: charles: should be done with my silo in a few [21:37] robru: will trigger another image, ok? [21:37] ubuntu touch [21:38] rsalveti, Did you see my comments on the MR? [21:38] rsalveti: robru is out for a bit [21:38] tedg: not yet [21:38] rsalveti: feel free to trigger a new image, I don't think there'd be any blockers [21:39] tedg: I'm not checking for audio-sink because at that point there's no way to not have an audio-sink [21:39] tedg: but can add a check if you prefer [21:40] popey, yes, that just needs a merge to trunk and someone to resolve the conflict in that MP [21:40] tedg: and the manual test needs to be part of pulseaudio, not the indicator [21:40] rsalveti, I think because you're dereferencing it (thus would crash) in the next line, it's important. [21:40] already covering that [21:41] tedg: sure, it's just that if that fails, you have way bigger problems :-) [21:41] but no worries, will update [21:41] balloons, I fixed the missing test results and reran that MP [21:41] * fginther swears at jenkins [21:41] :-) [21:45] fginther: do we have a jenkins replacement already? [21:46] :-D [21:52] fginther, anyways on the py3 thing, it looks like we'll just need to coordinate mp's with you switching the jobs over.. the debian packaging and cmake just need to be told to go to python3. That's why the massive failures. At least I get it now [21:57] balloons, ack [21:58] balloons, is elopio's MP ready to land soon? [21:59] kenvandine, I tested the debs from the silo, not sure if its working correctly or not [22:00] tedg: mind checking the mr again? [22:00] I dont get blank lines, but I granted webbrowser access and it doesn show in the list [22:00] tedg: https://code.launchpad.net/~rsalveti/indicator-datetime/adding-media-role/+merge/233299 [22:00] kenvandine, but camera does [22:00] * tedg clicks [22:01] fginther, we have to land my https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/fix-1359167/+merge/233387 first, which has the py3 conversion in it [22:02] rsalveti, Cool, thanks, looks good. [22:02] tedg: thanks [22:10] === trainguards: IMAGE 222 building (started: 20140904 22:10) === [22:15] rsalveti: you wanna help with mtp so I'm not the only one to have tested the fixes? [22:15] (it's silo 10) [22:15] sergiusens: how did your testing go for mtp? [22:15] cyphermox_: approved the mp, didn't you see? [22:16] I did [22:16] but you didn't test the silo [22:16] cyphermox_: oh, you didn't ask me to ;-) [22:16] cyphermox_: I can though, utopic or rtm? [22:17] utopic silo 10 [22:17] sergiusens: it's jsut a formality since you already built it and everything [22:17] it seems sergiusens will test it :-) [22:17] ack [22:17] cyphermox_: I didn't actually ;-) [22:17] cyphermox_: I grabbed the jenkins build [22:17] as long as I'm not the only one to test my own code... [22:18] rsalveti: well you can help with krillin and utopic [22:18] I've just flashed that again [22:18] what is the fix? [22:18] rsalveti: copy to sdcard [22:18] cool [22:19] rsalveti: and switch lang to french, music will be translated [22:19] and so on [22:21] really ? [22:21] ogra_: yes? [22:21] * ogra_ always wanted to hear his songs in french [22:21] i have to try that ! [22:22] I made sure you could only translate to french though, that's to help with the master plan of making Ubuntu Touch french-only, and finally establish our language as the one true Ubuntu language :) [22:22] does the artist need to be able to speak french to have the lyrics translated ? [22:23] or does it just work on the fly with all music ? [22:23] :) [22:25] cyphermox_: ogra_ x-use-langpacks makes the langpacks not be in the deb though, right? [22:26] the mo's that is [22:26] the .mo/.po files [22:26] right [22:26] so I can't test the lang until we get one of those released [22:26] but jenkins ignores that flag and it worked there [22:26] ogra_: it's highly experimental on-the-fly translation ;D [22:26] so it's all good [22:26] cyphermox_, lol [22:27] no need to know how to speak french, it will work [22:27] you'll magically understand everything too, because it will appear as though it's the original language [22:27] babelfrench ! [22:35] *twiddle* [22:55] * ogra_ vomits over the broken changelog that came out of the silo [22:56] so annoying [22:56] (was kind of pointlless that i used -v when generating it ... the silos always cut off the end :( ) [23:07] hi trainguards. A click-scope silo landed about three hours ago in rtm via sync:xxx. Do you guys know why it does not show up when trying to apt-get upgrade it in a clean rtm image? [23:20] plars, if i dont manage to land the adbd change in rtm tonight, will you get along ? [23:21] robru: ^ can I get the rtm instance setup now? [23:21] (it is still migrating to utopic and til i get the rtm silo ready i'll have been fallen asleep) [23:21] also, if I click build, is there auto logic for it to do the copy for me? [23:21] or is sync:X not meant for us? [23:29] sergiusens: i setup your rtm instance nao [23:30] thanks [23:30] is it already in the spreadsheet? [23:30] there i get my answer [23:30] cyphermox_: did rsalveti get a change to test mtp as well; or is it all on me? [23:31] all you I think [23:31] well, I did too [23:31] cyphermox_: but I'm drinking a 9% beer at this hour :-P [23:31] not yet [23:31] sergiusens: 9%. wimp [23:31] I'm finishing up a very very tiny amount of port :/ [23:31] well it has my ack [23:32] ChickenCutlass: we should have team dinner at a good brewery ;-) [23:32] sergiusens: trust me — I will work it out [23:32] \o/ [23:32] sergiusens: all the other teams will be jealous [23:32] or just do a beer tour [23:32] hop into brewery, drink, hop out [23:32] I don't care about dinner [23:32] :) [23:33] sergiusens: right — just a prezel here and there [23:33] phew [23:33] works for me [23:33] how painful that was [23:33] ogra_: is it done [23:33] doneded [23:33] 3h silo munching vs a 30sec upload [23:33] ChickenCutlass, i know :) [23:34] ChickenCutlass, but only the utopic part [23:34] ugh [23:34] rtm is another cycle like this [23:34] sergiusens: nitpicking, but your DH_GOLANG_INSTALL_ALL change isn't in changelog [23:34] plus QA [23:34] ogra_: maybe after the crunch, we should migrate adb (the parts we care about) to go [23:34] which is why i'll give up now ... i wont survive another 3h tonight [23:34] sergiusens, god forbid ! [23:35] clean C [23:35] :) [23:35] cyphermox_: argh, I could add it [23:35] ogra three hour of what? [23:35] sergiusens: don't bother [23:35] probably some checker would do some good at the jenkins level [23:35] * sergiusens ping fginther for MORE work :-) [23:35] checker for this stuff? [23:36] it's not really something you can work out programmatically [23:36] cyphermox_, getting a silo ... uploading ... building ... testing on two devices ... finding an issue ... spending 10min on a fix ... start over .... [23:36] cyphermox_: well the packaging ack check at the jenkins level might help me notice I need to update it [23:36] overall i started 3h ago [23:36] sergiusens: I guess [23:36] ogra_: you are finally enjoying the train! [23:36] and the silo stuff stole half my changelog :( [23:36] ogra_: again... welcome to the train ;-) [23:37] ogra_: if you set changelog in your changes it shouldn't touch it [23:37] sergiusens, well, usually i dont need to land in both distros at the same time [23:37] ogra_: heh :-) [23:37] sergiusens, its absolutely fine if you can do it as a side job and leave it do its stuff while you do something else [23:38] it only gets painful if you have to watch it all the time [23:38] ogra_: oh, I can't do that; stuff rots that way [23:38] rsalveti: did you plan to test mtp or should I set it to testing pass now? [23:38] cyphermox_: still doing some other stuff, so feel free to give +1 [23:38] cyphermox_: I'm +1 on that [23:38] ack, marking as done [23:38] fixes one of those blockers in the email, so good [23:39] cyphermox_, i did two revisions ... created the .changes file with -v to have them both in .... only the one liner of the second change ends up in the final package ... the 20 page novel for the former revision is gone [23:39] ogra_: that may be part of the "hot fix" to prevent changelogs from version 0 to present :-P [23:41] rsalveti: want to ack packaging changes? https://ci-train.ubuntu.com/job/ubuntu-landing-010-2-publish/lastSuccessfulBuild/artifact/packaging_changes_mtp_0.0.4+14.10.20140904-0ubuntu1.diff [23:41] or sergiusens [23:41] cyphermox_: I'm not core [23:41] just ppu [23:41] cyphermox_: looks fine [23:41] you aren't? [23:41] cyphermox_: no, not sure if I have rsalveti's blessing still :-P [23:41] dude. [23:42] dum de dum.. [23:42] i know :-) [23:43] sergiusens: you always had my +1 :P [23:43] rsalveti: you said I should wait ;-) [23:43] rsalveti: I did a thread Join and waiting for that to finish [23:43] ahah, just said what people would tell you anyway [23:44] * sergiusens checks who's on the board these days [23:46] robru: I don't want to touch things you may have already been working on, not sure if I just push the buttons for dbarth's silo 17 [23:48] cyphermox_, don't publish silo 17 [23:48] kenvandine: ah, thanks for letting me know :) [23:49] I don't think the MP is approved yet [23:49] and seb had problems with it [23:49] and i just published settings in silo 11 [23:50] === trainguards: IMAGE 222 DONE (finished: 20140904 23:50) === [23:50] === changelog: http://people.canonical.com/~ogra/touch-image-stats/222.changes === [23:50] look, an image [23:50] cyphermox_, i'm not sure why the spreadsheet listed the MP as ready, since it had never been approved [23:50] 2am here ... i guess the rtm side has to wait til tomorrow morning [23:51] * ogra_ gies to bed ... [23:51] *goes [23:51] * kenvandine toggled that back to no :) [23:51] ogra_: or *dies ? [23:51] ack [23:51] sergiusens, hah [23:51] close :) [23:51] lool, i just published silo 11