[04:45] <rsalveti> Mirv: robru: slangasek: do we know who disable the import-images job from cron?
[04:53] <robru> rsalveti: i know nothing.
[05:54] <Mirv> rsalveti: same here, I've only seen ogra_ discussing import-images at times
[05:54] <rsalveti> which sucks, as we don't have a new image now
[05:54] <rsalveti> maybe ogra_ can get it fixed in a few
[05:55] <Mirv> handling the images is maybe slightly bottle-neck:ish, ie when there is trouble there are few that can help.
[05:55] <Mirv> in 2-3h, yes
[05:55] <rsalveti> problem is that cronjob gets disabled without a single comment explaining why
[05:55] <rsalveti> so impossible to know the reason
[05:56] <rsalveti> and this happens quite often
[05:56] <Mirv> right, that has happened before
[05:56] <Mirv> it'd really use some small process that includes documentation
[05:56] <rsalveti> yeah
[07:46] <oSoMoN> good morning trainguards, can I please have a silo for line 74 ?
[07:46] <Mirv> oSoMoN: ok
[07:48] <oSoMoN> thanks Mirv!
[09:03] <ogra_> mvo, do you know if the image importer was disabled due to snappy images ?
[09:04] <ogra_> err s/images/issues/
[09:05] <ogra_> Mirv, rsalveti, i'm doing a manual run now
[09:06] <ogra_> hmm, runnin it with -v and i get no output ... strange
[09:06] <ogra_> bah ... my crappy keyboard turned that into -vv :(
[09:08] <mvo> ogra_: no, I was not aware of this, what happend? do you have details?
[09:09] <mvo> ogra_: I only see a ftbfs on arm64
[09:09] <ogra_> mvo, not beyond "someone disabled the cron job ... likely on friday"
[09:30] <sil2100> Shouldn't disabling of the importer be annouonced on -release first?
[09:30] <sil2100> Was there no rationale for that?
[09:31] <ogra_> well, we usually announce it on -release ...
[09:31] <ogra_> obviously the person that disabled it didnt announce it though
[09:32] <ogra_> i cant really tell if it is broken, seems the -v switch that usually gives you the log doesnt work anymore
[09:32] <ogra_> i see it moving in top though
[09:33] <sil2100> huh
[09:33] <sil2100> jibel: *pokes*
[09:55] <imgbot> [09:55] <imgbot> [09:55] <Mirv> \o/
[09:55] <ogra_> ha !
[09:56] <sil2100> ogra_: maybe let's re-kick an image then? :)
[09:57] <ogra_> yep, doing
[09:58] <Mirv> QtWebKit removal progresses http://people.canonical.com/~ogra/touch-image-stats/20150321.changes
[09:58] <ogra_> whee !
[09:58] <Mirv> just two updates would be needed (webbrowser-app, ubuntu-html5-theme) and it should drop
[09:59] <ogra_> cool, i'm eager to see what it drags with it
[10:00] <imgbot> [10:19] <ogra_> sil2100, there is a new tzdata package we might want to pull into rtm
[10:24] <sil2100> ogra_: on iiiit!
[10:24] <ogra_> :)
[10:24] <sil2100> (in case we do an OTA3 from RTM)
[10:33] <ogra_> yeah, that was the idea
[11:25] <imgbot> [11:25] <imgbot> [11:25] <sil2100> That seemed fast
[11:25] <sil2100> hm
[11:26] <davmor2> ogra_, sil2100: do my eye deceive me or is there no libc there either
[11:28] <sil2100> Interesting
[11:30] <sil2100> ogra_, davmor2: from what I see in the image manifest, the latest glibc is in there
[11:30] <sil2100> ogra_, davmor2: actually, the previous image had it as well
[11:30] <ogra_> oh, then it landed in 143
[11:31] <ogra_> hmm, not there either
[11:32] <sil2100> ogra_, davmor2: I see it got introduced first in 20150322
[11:32] <sil2100> (from the manifests)
[11:33] <sil2100> I wonder why I don't see it in changes
[11:34] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20150322.changes
[11:34] <ogra_> it is there
[11:35] <ogra_> seems not mapped to an iname number :/
[11:35] <ogra_> *image
[11:36] <sil2100> hm, but I checked consecutive image numbers
[11:36] <sil2100> Has this rootfs not been used in any image?
[11:36] <sil2100> Ah, maybe due to the importer being off?
[11:37] <ogra_> http://system-image.ubuntu.com/ubuntu-touch/devel-proposed/mako/index.json has no trace of 20150322
[11:37] <ogra_> yeah, i guess that confused everything
[11:37] <ogra_> so it was in image 143 + 1/2
[11:37] <ogra_> :)
[11:38] <ogra_> 143 is 20150320 ... 144 is 20150323
[11:38] <ogra_> so the importer skipped it ... let me cat the content to 144
[11:39] <ogra_> done
[11:40] <ogra_> oh, wait, 0321 is missing too
[11:41] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/144.changes
[11:41] <ogra_> that is the full changeset for the weekend
[11:47] <davmor2> ogra_: oh so it's listed there then
[11:48] <sil2100> ;)
[11:49] <ogra_> davmor2, now it is ... i had to merge three changeloags
[11:50] <davmor2> ogra_: I see what the issue is, before you were only checking the changelogs now you are looking at the changeloags it is showing up ;)
[12:23] <sil2100> ogra_: can you tell me which changelog files have changed?
[12:25] <ogra_> 20150321 and 20150322
[12:44] <sil2100> ogra_: thanks :)
[12:57]  * sil2100 lunch
[13:10] <popey> sil2100: what's happening with the i-d crash fix?
[13:10] <popey> I see yet another customer with a crashed i-d... https://twitter.com/CGaenzler/status/579067770765086721
[13:54] <pmcgowan> Mirv, three days lots of use with silo 3 and no crashes
[13:57] <popey> pmcgowan: did we get a yay or nay for the indicator-datetime to be fixed in rtm? and thus are we going to have another rtm release to make it worthwhile?
[13:57] <popey> I keep hearing conflicting comments about whether the next OTA will be rtm or vivid based.
[13:57] <popey> hard to know current stats
[13:57] <popey> *state
[13:57] <pmcgowan> popey, the next ota is rtm based
[13:57] <pmcgowan> and the indicator fix is tagged to land
[13:58] <Mirv> pmcgowan: sounds good. I finished with my AP + exploratory testing so I'll put the silo towards QA then
[13:58] <popey> brilliant \o/
[13:58] <pmcgowan> Mirv, my only hesitation is its a complete qt update for the one patch I suppose
[13:58] <popey> pmcgowan: how about the eds fix bfiller landed in vivid?
[13:58] <pmcgowan> and krillin not crashing
[13:58] <pmcgowan> popey, which is that?
[13:58] <popey> (would make calendar 10x better experience)
[13:59] <popey> pmcgowan: https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1423185/+merge/252184
[13:59] <Mirv> pmcgowan: qtdeclarative module rebuild, not others. but yes, it's one of the bigger modules. no reason why build result on rtm should differ though from the previous build other than this patch affecting pixmap handling.
[14:01] <pmcgowan> Mirv, ack, my thinking was if it were to occur on krillin it would be REALY bad
[14:01] <pmcgowan> popey, that seems worthy of a fix
[14:06] <popey> pmcgowan: anything I need to do, or just poke bfiller nicely? :)
[14:07] <pmcgowan> popey, I just poked him for his view, depends on frquency, does that happen all the time-ish?
[14:07] <pmcgowan> considering calendar not quite prime time yet
[14:07] <popey> pmcgowan: very easily reproducible, and with that fix it's night and day
[14:07] <Mirv> pmcgowan: it seems it's luck if the crash doesn't happen on krillin so far. I added some details for QA to evaluate it now, including the debdiff (http://paste.ubuntu.com/10660930/)
[14:07] <pmcgowan> Mirv, ack thanks
[14:08] <pmcgowan> popey, then I am ok to land it, just a few lines
[14:08] <popey> thank you
[14:24] <pmcgowan> popey, that indicator fix is in silo 4 a long time, need qa to test
[14:24] <popey> ah, okay. jibel ^^
[14:25] <pmcgowan> popey, oh trello says it passed
[14:26] <pmcgowan> popey, scratch that, that was not rtm
[14:26] <pmcgowan> it needs to get in the queue
[14:27] <popey> yeah it was passed in vivid
[14:38] <rvr> didrocks: If you think that booting fine is enough, I'll sign off your silo right away ;)
[14:39] <didrocks> rvr: it is for this change :)
[14:39] <didrocks> just some binaries changing between packages
[14:39] <didrocks> moving*
[14:40] <rvr> didrocks: Done!
[14:40] <didrocks> rvr: thanks :)
[14:44] <jibel> popey, the card was missing from our board. I added it manually and will find someone to test it asap
[14:45] <popey> thanks jibel !
[14:46] <davmor2> didrocks: jibel: http://paste.ubuntu.com/10661235/ and root         1  2.4  0.2   3764  2288 ?        Ss   14:19   0:03 /sbin/init as a confirmation to rvr :)
[14:47] <didrocks> thanks guys :)
[15:30] <balloons> cihelp, I need an app added to core apps jenkins. I'd like jenkins to run on lp:help-app now.
[15:32] <psivaa_> balloons: ack, will handle that and get back to you
[15:34] <balloons> psivaa_, thanks, let me know if you need help. You should be able to clone something like all the clock app jobs for it. I added jenkins bot to the developers of the app, so it should be all ready to go
[15:36] <psivaa_> balloons: ack, thanks
[16:03] <psivaa_> balloons: do you need 'D09add_ppa~ubuntu-touch-coreapps-drivers~daily' hook too for this?
[16:03] <balloons> psivaa_, yes
[16:03] <psivaa_> i'm not sure what that hook does
[16:03] <psivaa_> balloons: ack
[16:03] <balloons> psivaa_, it adds the core apps ppa, which is needed in this case
[16:23] <psivaa_> balloons: I could not see any tests directory, does this have a test-suite name?
[16:26] <balloons> psivaa_, ohh right. It's not going to have the tests/autopilot structure of before. It does have tests, let me find the direcotyr
[16:26] <psivaa_> some are in internals/
[16:26] <balloons> psivaa_, though to be fair, you shouldn't have to care I suppose at first
[16:27] <balloons> they will run as part of the build
[16:27] <psivaa_> balloons: ack
[16:27] <balloons> if we add something to tests/autopilot later it should all just work still right?
[16:28] <psivaa_> i guess that should
[16:28] <balloons> ok, so sounds like we are fine then?
[16:28] <psivaa_> fginther: ^ in this case with no tests dir, what would be the testsuite-name in the cupstream2distro-config?
[16:29] <psivaa_> fginther: 'test_suite:' in the config
[16:29] <psivaa_> balloons: let me confirm
[17:41] <elopio> ping cihelp: do you have an ETA for this bug? https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1389729
[17:41] <elopio> or maybe a workaround?
[17:41] <elopio> it's affecting this execution: http://91.189.93.70:8080/job/reminders-app-vivid-amd64-ci/151/console
[17:42] <psivaa_> elopio: we all are in a meeting, will come back to you once that's over
[17:42] <elopio> thanks psivaa_.
[17:44] <elopio> mzanetti: ^
[17:45]  * mzanetti reading
[17:45] <mzanetti> ack. thanks elopio
[17:56] <cyphermox> barry: I'll take care of it ^
[18:01] <barry> cyphermox: thanks
[18:08] <cwayne> davmor2, ello, think you'll have time for a custom test this week?
[18:08] <davmor2> cwayne: add it to the spreadsheet
[18:08] <davmor2> cwayne: oh wait for vivid or rtm
[18:09] <cwayne> davmor2, rtm
[19:36] <balloons> psivaa_, so what's the verdict on the help app?
[19:36] <sil2100> cyphermox, barry: I leave the train in your hands now :)
[19:39] <psivaa_> balloons: help-app is now in the core app jenkins. could you check please
[19:40] <balloons> psivaa_, awesome, checking
[19:40] <sil2100> THanks guys o/
[19:49] <balloons> psivaa_, the bot definitely picked things up and ran, and I just triggered a build too
[19:50] <balloons> So build issues, but presumably nothing wrong with jenkins. I'll assume it's all good and work on the build. Thanks!
[19:50] <psivaa_> balloons: ack, thanks
[21:35] <psivaa_> elopio: regarding your ping about https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1389729, we dont have any workaround at the moment, and finding a fixer for the bug is proving difficult. reminders app CI is impacted by this and need to be handled mannually i suppose
[22:59] <rsalveti> robru: next image might be busted
[22:59] <rsalveti> robru: dist-upgrade and my phone fails to boot
[22:59] <robru> rsalveti: oh hey. I'm off this week ;-)
[23:00] <rsalveti> alright :-)
[23:23] <cyphermox> duly noted.