[01:46] <rsalveti> robru: just a heads up that the next image might be broken
[01:46] <rsalveti> rtm one
[01:46] <rsalveti> flashed latest + dist-upgrade and now unity8 doesn't even start
[01:46] <rsalveti> unity8: tpp.c:62: __pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)' failed.
[01:46] <rsalveti> let me reflash
[01:47] <robru> rsalveti: oh, is there any way to pull that before it goes live?
[01:48] <rsalveti> we might just not create the next image
[01:48] <rsalveti> I'm reflashing and will try to reproduce my problem
[01:56] <rsalveti> robru: worked fine after a reflash, so we should be good
[01:56] <rsalveti> will try to reproduce a few more times
[01:56] <rsalveti> might be just a broken env here
[01:58] <robru> rsalveti: heh, ok. well you can disable the cron job if you find a problem right? I can't and I'm expecting company in a few minutes.
[01:58] <rsalveti> yeah, will start one in a few
[01:58] <rsalveti> will wait and see :-)
[01:59] <rsalveti> yeah, it's a combination with the media-hub I had in my landing
[01:59] <rsalveti> really weird
[01:59] <rsalveti> so all is good :-)
[02:01] <robru> rsalveti: cool, thanks for figuring that out ;-)
[02:01] <rsalveti> sorry for the noise :-)
[02:05] <imgbot> === IMAGE 60 building (started: 20150109-02:05) ===
[03:05] <imgbot> === IMAGE RTM 188 building (started: 20150109-03:05) ===
[03:25] <imgbot> === IMAGE 60 DONE (finished: 20150109-03:25) ===
[03:25] <imgbot> === changelog: http://people.canonical.com/~ogra/touch-image-stats/60.changes ===
[04:15] <imgbot> === IMAGE RTM 188 DONE (finished: 20150109-04:15) ===
[04:15] <imgbot> === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/188.changes ===
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
[08:06] <satoris> ping trainguards. Line 55 has been "ready to build" for almost a full day now. Is there something holding it up or are things just busy?
[08:17] <Mirv> satoris: the lander clicks the build button also in case of sync silos...
[08:19] <satoris> Mirv: huh, I've never clicked the build button before and yet my packages have built automatically.
[08:21] <satoris> And jenkins tells me I don't have build permission.
[08:24] <Saviq> satoris, sometimes the trainguard who assigned a silo just kicks a build, too
[08:24] <bzoltan> Mirv:  who is the QA sherif around this time?
[08:25] <satoris> Saviq: yes, that seems reasonable. If you have a silo ready to build, why would you _not_ want it built immediately when possible.
[08:26] <Mirv> satoris: huh? have you just recently started your own landings? robert added some autobuild functionality for some cases. anyway, it's building now but you should have access too.
[08:26] <Saviq> satoris, sometimes I preempt to get a silo early while MPs are being prepped and such
[08:27] <satoris> Mirv: no, I have done my own landings for ages. Never had a problem before.
[08:27] <Mirv> satoris: for example if sync target is not ready yet. but yes that's why there's the auto function now.
[08:27] <Mirv> bzoltan: soon brendand or davmor
[08:29] <satoris> Mirv: so if I in the future need building (as I don't seem to have rights to start them myself) should I just ask someone here to do it or what is the correct procedure?
[08:34] <vila> mardy, Mirv : http://s-jenkins.ubuntu-ci:8080/job/ubuntu-system-settings-online-accounts-ci/186/console \o/
[08:37] <mardy> vila: looks like I cannot open the link, not even with the VPN on
[08:37] <mardy> vila: anyway, I guess that you did it :-)
[08:37] <mardy> vila: what was it?
[08:38] <Mirv> satoris: yes you can just ask trainguards, but next week we can ask sil2100 what needs to be done for permissions
[08:38] <vila> mardy: remove the hook that was running the coverage part, it's not needed anymore.
[08:38] <satoris> Mirv: check, thanks.
[08:39] <vila> mardy: it's annoying that you can't access with a working vpn :-/
[08:39] <vila> mardy: do you have a way to validate your VPN to access something else ?
[08:41] <vila> mardy: better explanation: https://pastebin.canonical.com/123071/
[08:46] <satoris> ping trainguards, please start build of line 58 (landing-001). Thanks.
[08:47] <Saviq> satoris, done
[08:47] <satoris> ty
[08:48] <Saviq> satoris, in any case, you should get build permissions if you've been landing already
[08:48] <Saviq> not sure who has the power...
[09:15] <popey> Mirv: morning. could you please upload http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/generic-click-builder-utopic-armhf/output/com.ubuntu.calendar_0.4.565_all.click when you get a chance. Thanks.
[09:26] <Mirv> popey: morning.
[09:28] <Mirv> popey: done, this time without any hassle too
=== chihchun_afk is now known as chihchun
[09:41] <popey> Mirv: thanks
[09:52] <popey> davmor2: bug i mentioned, could you reproduce if you get a moment please? https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1408958
[09:52] <ubot5> Launchpad bug 1408958 in indicator-datetime (Ubuntu) "Calendar alarm notifications have no buttons, on screen for short while" [Undecided,New]
[09:54] <davmor2> popey: man now I got to install the calendar app and sign into to google and everything
[09:55] <popey> new calendar app in store!
[09:55] <popey> :D
[10:00] <davmor2> popey: yeah I thought that was the new behaviour.   Maybe I was wrong.
[10:02] <davmor2> popey: there was meant to be a difference between calendar and alarm notifications maybe I read the bug wrong though
[10:03] <popey> that may be the case, but this is a calendar event
[10:03] <davmor2> popey: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1320880
[10:03] <ubot5> Launchpad bug 1320880 in Ubuntu Calendar App "Calendar notifications are treated the same as an alarm notification" [High,In progress]
[10:05] <davmor2> popey: does that give you some feedback
=== karni is now known as karni-away
[10:13] <popey> davmor2: hmmm
[10:13] <popey> 2 seconds still isn't long enough to pull phone out of pocket and actually read the notification
[10:13] <ev> how are we doing with all things CI? Any issues to report?
=== karni-away is now known as karni
[10:38] <Saviq> trainguards, can someone please delete unity8 20150109 from rtm landing 003 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-003/+packages
[10:39] <Saviq> I must've inadvertently pressed the build button on the wrong silo :/
[10:39] <Saviq> and 20150108.1 is what I tested
[10:42] <Mirv> Saviq: sure
[10:42] <Mirv> saamight be too late if you want to keep the old..
[10:42] <Mirv> saamight.. :)
[10:43] <Saviq> saamight, let's see
[10:43] <Mirv> Saviq: so the 08.1 already disappeared from sight, do you want to try what happens if I delete the 09?
[10:43] <Mirv> the package is of course there, but I don't know how the archive data is set up
[10:43] <Saviq> Mirv, let's see, worst case I need to retest anyway :/
[10:44] <Mirv> indeed
[10:44] <Mirv> so now 09 is Deleted and 08.1 is Superseded...
[10:44] <Mirv> and if not going to the Copy/Delete packages page, the PPA looks like it'd be empty
[10:45] <Saviq> I wonder if I can copy
[10:45] <davmor2> popey: sorry didn't mean to ignore you didn't see your reply, I agree but that isn't my call, it fit the criteria of behaving differently personally for calendar events I would have it only ring for a second or 2 and then just leave the osd displayed until it accepted with a button press maybe
[10:46] <davmor2> popey: I don't know though if the alert is tied into the osd which might be the issue
[10:46] <Saviq> Mirv, think you could bin-copy to the same (or a different?) silo?
[10:47] <Mirv> Saviq: yeah! I've done that before, and it seems to work.
[10:47] <Mirv> Saviq: so, copied a superseded 08.1 to the same PPA now
[10:47] <Saviq> Mirv, awesome, thank you
[10:47] <Saviq> now a watch_only and we're back in business
[10:58] <Saviq> Mirv, is it expected that watch_only takes so long https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-1-build/113/console ?
[10:58] <Saviq> it's been going for 10 mins now
[10:59] <ev> elopio, cihelp: http://s-jenkins.ubuntu-ci:8080/job/ubuntu-system-settings-ci/1889/console looks like a job is broken. My shift is about to end, but if we can get confirmation, the next vanguard can pick it up.
[11:05] <cjwatson> mardy: Perhaps you're using the old batuan-based VPN.  https://wiki.canonical.com/InformationInfrastructure/IS/HowTo/CompanyOpenVPN is the way forward, if so
[11:06] <Mirv> Saviq: I think it's a bug, I've noticed it too, but only 5 mins
[11:06] <Saviq> Mirv, 18 mins and counting :/
[11:06] <Mirv> Saviq: oh right I think I noticed this new behavior too. it waits at that "Checking" until the indexes it expects are there
[11:06] <Mirv> I don't know how it feels about that deleted newer version..
[11:06] <Saviq> wonder if they will show up...
[11:07] <Saviq> yeah, that's what I was afraid of, too
[11:07] <mardy> cjwatson: yes, I'm still on the old one; I'll read that page and update, thanks!
[11:07] <Saviq> Mirv, let's see what happens, we can always move to a different silo
[11:07] <Mirv> yes
[11:08] <cjwatson> mardy: I think some of the network rearrangements towards the end of last year basically broke the batuan VPN (although I hadn't been using it for several months before that, so I'm inferring this from other reports)
[11:09] <cjwatson> mardy: Fortunately the new company-wide VPN AFAIK gives you access to a strict superset of what the batuan VPN did
=== chihchun is now known as chihchun_afk
[11:14] <mardy> cjwatson: yep, now it works, thanks a lot! :-)
[11:14] <Saviq> Mirv, yeah, so... it did expect the new version, the job failed, now whether that's a bug in citrain or not - you tell me
[11:14] <Saviq> Mirv, but, can we please bincopy to a different silo then
[11:20] <cjwatson> mardy: Great
[11:25] <Mirv> Saviq: it does not seem the http://ppa.launchpad.net/ci-train-ppa-service/landing-003/ubuntu-rtm/dists/14.09/main/ information is going to get right either, so doing the silo dance
[11:26] <Saviq> Mirv, thank you, and sorry for the pain
[11:28] <Mirv> Saviq: no problem. it seems build watch_only still doesn't work immediately so let's wait again.
[11:53] <Saviq> Mirv, doesn't wanna work :/
[11:53]  * Saviq back in a bit
=== MacSlow is now known as MacSlow|lunch
[12:12] <Mirv> Saviq: I wonder how that's possible. not even a reconfigure + build watch_only seems to help. I wonder if we need robru's help to debug it (https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-007-1-build/90/console)
[12:12] <Mirv> the package is there and intact, QA could test it manually of course and it could be copied manually.
[12:17] <satoris> ping trainguards. Line 55 is tested and working but not marked done yet because it turned out that an updated version of qtubuntu-camera needs to land first. That is not on the sheet yet but should happen soon. What should I write on the sheet to make sure it lands ASAP after qtubuntu-camera but not before?
[12:19] <Mirv> satoris: it looks like the another landing is in silo 000 / line 70? just mark yours as tested and that comment it should land after silo 000's qtubuntu-camera.
[12:31] <Mirv> Saviq: I've done everything I can possibly think of... created a new line in the spreadsheet, copied the package first before assigning a silo and assigned silo only after the previous one was purged
[12:31] <satoris> Ack.
[12:39] <Mirv> Saviq: I just became Evil and resolved the issue!
[12:39] <Mirv> muahahaha
[12:40] <Mirv> so in the meta field in column P, I wrote "Packages built" and the rest of the spreadsheet took it from there :)
=== MacSlow|lunch is now known as MacSlow
[13:26] <Saviq> Mirv, yeah, only question is if publishing will work ;)
[13:26] <Saviq> Mirv, thanks in any case
[13:30] <Mirv> Saviq: copy-package will, regardless :)
[14:41]  * Mirv switches to furniture building mode
[14:42] <Mirv> ...after assigning a silo to jgdx
[14:42] <jgdx> :)):)
[14:42] <jgdx> IKEA?
[14:43] <Mirv> no, but a bit similar just with worse instructions ;)
[14:44] <josepht> I was envisioning saws and planes and such :)
[14:50] <cwayne> davmor2: heya, think I can get a custom tar through on monday?
[14:51] <davmor2> cwayne: possibly :)
[14:51] <cwayne> davmor2: would it help my chances if i said please :)
[14:52] <davmor2> cwayne: no as in I don't know what else is going to happen Monday but it shouldn't be an issue unless hell is released :)
[14:53] <davmor2> cwayne: pencilled in :)
[14:55] <cwayne> davmor2: thanks :) and happy new year!
[14:55] <davmor2> cwayne: happy new year dude :)
[15:59] <elopio> ev: ok, thanks for looking at it. cihelp: is somebody looking at http://s-jenkins.ubuntu-ci:8080/job/ubuntu-system-settings-ci/1889/console ?
[16:17] <retoaded> elopio, in a meeting atm but looking ....
[16:20] <elopio> retoaded: thanks!
[17:05] <kgunn> trainguards just need a vivid silo, line 83
[17:06] <robru> kgunn: vivid 1
[17:06] <robru> Mirv: I guess you figured out rtm 7 without me?
[17:18] <popey> davmor2: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1409069
[17:18] <ubot5> Launchpad bug 1409069 in ubuntu-system-settings (Ubuntu) "System Settings doesn't show updates until you visit updates screen" [Undecided,New]
[17:36] <Saviq> trainguards, reconfigure of vivid silo 001 please, added qtmir-gles there
[17:44] <robru> Saviq: what's the deal with the ongoing build? do you need that? it shouldn't be running during a reconfigure
[17:45] <Saviq> robru, it builds qtmir
[17:45] <Saviq> robru, now we're adding qtmir-gles
[17:45] <Saviq> which is the "twin" package
[17:47] <robru> Saviq: well the thing is, that ongoing build job holds the silo config in memory, so if I reconfigure while it's building, when the build finishes, it'll save it's state which will effectively undo the reconfigure.
[17:48] <Saviq> robru, we can abort the build then, it's still gonna build in the PPA and then another build will see that?
[17:48] <robru> Saviq: so we'd need to kill the build job (which won't actually kill the build in the PPA) and then reconfigure. yeah should work.
[17:50] <robru> Saviq: ok it's reconfigured, just make sure you specify 'qtmir-gles' in the new build job otherwise it'll upload a new qtmir
[17:51] <Saviq> robru, I know the drill, thanks :)
[17:52] <robru> Saviq: you're welcome!
[18:01] <bzoltan> robru: do you know when the next RTM image is going to be created?
[18:05] <robru> bzoltan: in about 10 hours as far as I know
=== alan_g is now known as alan_g|EOW
[19:15] <elopio> fginther: ps-jenkins is now a member of canonical-platform-qa
[19:15] <elopio> sorry for the delay
[19:45] <elopio> fginther: plars: I got a run in ubuntu-sanity-tests \o/
[19:45] <elopio> thanks.
[19:45] <plars> elopio: great!
[19:46] <elopio> these is for the self tests. Now we need to find a way to run the actual sanity tests in an actual device. But that will be in a future iteration.
[20:57] <robru> sergiusens: "The landing is small enough to not need testing and has been in vivid for a while." uhhhhh huhhhhhhh... ? do you have a bug reference with rtm approval for that?
[21:26] <sergiusens> robru: yeah, it's in the MP
[21:26] <sergiusens> robru: oh, last debian/changelog
[21:26] <sergiusens> and no, I don't have it handy ;)
[21:26] <sergiusens> rsalveti: ^
[21:28] <robru> sergiusens: I don't see any bug reference at https://launchpadlibrarian.net/194113685/ciborium_0.2.12%2B14.10.20141008-0ubuntu1_0.2.12%2B15.04.20141201~rtm-0ubuntu1.diff.gz ?
[21:28] <rsalveti> sergiusens: everything needs Q
[21:28] <rsalveti> QA
[21:29] <rsalveti> if you test it on RTM, then just mark it as need QA
[21:29] <rsalveti> just changed QA sign off to required
[21:29] <rsalveti> QA should be able to validate this soon
[21:30] <rsalveti> sergiusens: can you update the testplan for it?
[21:30] <rsalveti> to include what is covered by this MR
[21:33] <sergiusens> rsalveti: robru I thought I wasn't supposed to do that
[21:33] <sergiusens> as in, someone else tags it
[21:33] <rsalveti> sergiusens: wasn't supposed to do what exactly?
[21:34] <robru> sergiusens: well yeah, somebody like pmcgowan needs to approve it for rtm. but he marks his approval by adding a task on your bug, and I just don't see any bug number listed anywhere. not in the spreadsheet, not in the changelog, etc.
[21:34] <rsalveti> just because the landing is under your name, we can take care of it if needed
[21:34] <rsalveti> but it would still be good if you could add the test case description in the wiki page
[21:34] <sergiusens> rsalveti: mark the QA field
[21:34] <rsalveti> so the QA team can validate by following what is available in there
[21:35] <rsalveti> sergiusens: oh, right, now everything RTM needs QA sign off
[21:35] <sergiusens> I missed the memo and that's not in the FAQ :-)
[21:36] <rsalveti> not sure if we indeed had one, just know because I did many landings over the past few days
[21:36] <rsalveti> or trying to at least
[21:37] <sergiusens> rsalveti: testplan updated
[21:38] <rsalveti> sergiusens: great, thanks!
[21:40] <sergiusens> rsalveti: this is the bug https://bugs.launchpad.net/camera-app/+bug/1392368
[21:40] <ubot5> Launchpad bug 1392368 in gallery-app (Ubuntu RTM) "Support storing and viewing photos on an SD card" [High,In progress]
[21:41] <rsalveti> cool, thanks
[21:50] <pmcgowan> sergiusens, rsalveti all set?
[21:50] <rsalveti> pmcgowan: yup