/srv/irclogs.ubuntu.com/2014/07/29/#ubuntu-ci-eng.txt

ogra_sine which file to select is a completely image specific thing00:00
slangasekwell, it's a hardware thing00:00
ogra_neither arch nor seed matter for this00:00
ogra_right, thats what i mean00:01
slangasekwhich in the future might mean we need runtime detection of the correct stack for a generic image00:01
ogra_yup00:01
slangasekso even livecd-rootfs is only an approximation, but it's certainly better than the mess we have now00:01
cjwatsonAgreed00:01
ogra_(at the cost of shipping bloat)00:01
cjwatsonConvergence => bloat ;-)00:01
slangasekogra_: do you want to push the fix into livecd-rootfs?  (after the current bodged image finishes building, at least)00:01
ogra_heh00:01
cjwatsonI mean, if that's how you define bloat, the implication is accurate00:01
ogra_not tonight anymore ... i just dropped by because i saw the mails on the ML (on my ubuntu phone btw, yay) ...00:02
xnoxslangasek: i think, we need a package witch force configures the alternate to one or the other, and conflicts/removes the other-one. Kind of like qt4-default & qt5-default00:02
xnox(as much as i hate the qt*-default packages)00:02
ogra_slangasek, but if it can wait til EU business day i'm happy to take that00:02
cjwatsonxnox: hm, that might work but I'd be worried about it entrenching the problem for upgrades and the like00:03
ogra_xnox, sneaking around the debian policy ?00:03
slangasekogra_: I think it can wait, everyone's EOD by the time this image gets built00:03
cjwatsonand hitting alternatives with a hammer always makes me scared00:03
xnoxor in the postinst of the both stacks we can do use ubuntu-drivers magic to inspect modaliases and not configure the wrong package on a given hardware.... but that would work in apt world, but not in the system-image mode.00:03
ogra_slangasek, ok, then i'll take care tomorrow00:03
slangasekogra_: great, thanks00:03
cjwatsonxnox: Nor in any live filesystem build00:04
xnoxyeap. =(00:04
ogra_xnox, i doubt modaliases even works00:04
xnoxogra_: well, they sure do install the right nvidia drivers.00:04
ogra_(never tried though)00:04
ogra_oh, i mean on the phone image indeed :)00:04
xnoxogra_: everything i say, usually comes from the prism of ubiquity installer =)00:05
ogra_:)00:05
cjwatsonOh, and ubuntu-touch-meta is waiting for a unity-scope-click autopkgtest which is in a huge queue, albeit quite close to the top of it01:02
cjwatsonBut the queue might be listed backwards ...01:02
cjwatsonLike watching paint dry01:03
cjwatsonhttp://d-jenkins.ubuntu-ci:8080/label/adt/load-statistics01:09
cjwatsonoh hai gcc01:09
slangasekthere we are, u-t-m into utopic01:34
pmcgowanslangasek, was just looking for the mr,01:34
cjwatsonNot published yet01:34
* slangasek nods01:34
ToyKeeperHmm, given the ETA on a new build, I think I'll head off for dinner...  unlikely it'll be ready until after I get back.01:35
cjwatsonThough publishing now01:36
cjwatson(It's in the "oh dear my new database servers haven't been plugged in yet" stage)01:36
pmcgowanslangasek, I missed the resolution, but I dont see any changes to u-t-m in lp01:40
cjwatsonhttps://launchpad.net/ubuntu/+source/ubuntu-touch-meta/+publishinghistory01:41
cjwatsonThe main package view is unhelpful when a change is mid-publication01:41
cjwatsonActually even more clearly, https://launchpad.net/ubuntu/+source/ubuntu-touch-meta/+changelog01:41
pmcgowanthanks01:42
pmcgowanso what exactly broke?01:43
slangasekpmcgowan: the builds had an unintended reliance on some undefined behavior (ordering of package configuration), and because two packages were being configured in the opposite order from before, the mir client library config was pointing to a shouldn't-have-been-there-but-was mesa build instead of the android build01:50
slangasek(which comes back around to us having better auditing of new packages winding up on the image - I don't know when the mesa packages landed there, but it was probably several weeks ago and went unnoticed)01:51
pmcgowan+1 on better auditing of new packages --- sore point01:51
pmcgowanthanks guys01:53
rsalvetiI think we always had the mesa packages in there01:54
rsalvetisince mir decided to split the backends01:54
cjwatsonYup01:56
cjwatsonFirst livefs build log matching /libmirclient.*mesa/ is 2014031101:56
rsalvetiright01:56
rsalvetilong long ago01:56
pmcgowanhow do we prevent this type of thing from screwing us again01:57
cjwatsonProbably corresponds to https://launchpad.net/ubuntu/+source/mir/0.1.6+14.04.20140310-0ubuntu101:57
cjwatsonWe keep on plugging away at undefined behaviour in builds wherever we see it, and each time we find one that makes things more robust01:58
pmcgowanI still dont understand why this hit us today01:59
pmcgowansomething deep in the tools?02:00
cjwatsonI don't think it's worth tracking down02:04
cjwatsonNondeterministic behaviour is nondeterministic02:04
imgbot=== trainguard: IMAGE 156 building (started: 20140729 02:05) ===02:04
pmcgowancomputers are determinstic yes ?02:04
cjwatsonThere's probably something that tweaked things, but I don't see it as a useful exercise02:04
pmcgowanwhat happened here02:05
cjwatsonNondeterministic as in the behaviour is not specified02:05
pmcgowanhmmm02:05
slangasekpmcgowan: the ordering of package configuration by apt is undefined, so some small unrelated tweak in the system probably tripped it off02:05
cjwatsonOr rather it's undefined when not constrained by dependencies02:05
slangasekthe same update introduced three new packages and dropped one, which were legitimate changes that could have permuted apt02:05
cjwatsonTrying to track this down will likely just lead to some entirely reasonable change02:06
slangasekah, and looks like cjwatson beat me to triggering the rebuild02:06
cjwatsonAnd won't tell us anything interesting02:06
cjwatsonslangasek: Not I02:06
* slangasek nods02:06
slangasekoh02:06
cjwatsoncron? :)02:06
slangasekwell, someone did, hopefully they made sure it was in the archive first :)02:06
pmcgowanjust looking for a way to not get burned again02:06
slangasekheh, dunno02:06
pmcgowanyou guys can tell me what that is02:06
slangasekpmcgowan: in this case, removing packages that don't belong on the image in the first place would have saved us02:07
cjwatsonWhatever failure happened here happened months ago02:07
pmcgowanslangasek, omg _1 again02:07
pmcgowan+102:07
cjwatsonIMO the fundamental problem here is abusing selective package installation when runtime detection is the right answer02:07
cjwatsonRemoving packages that don't belong on the image is yet another fragile workaround for poor design02:07
cjwatsonIt's all too easy for that sort of thing to creep back in for one reason or another02:08
rsalvetiyeah02:08
pmcgowanI buy that02:08
rsalvetibest thing here would indeed mir to do the right thing during runtime02:08
cjwatsonBut if mir weren't relying on package-installation-dependent alternatives to behave appropriately for the hardware, we wouldn't have had this problem in the first place02:08
cjwatsonConvergence will force sanity on this :)02:08
pmcgowanexactly02:09
pmcgowanlets go 15602:09
pmcgowanthanks guys02:09
rsalvetiguess this build was started by cron02:10
rsalvetiwill be around to see if it's indeed a good one02:10
cjwatsonYeah02:10
cjwatsonIt started after the relevant publisher run finished02:11
rsalvetilive build logs should tell us (and the x86 one gets done way before the armhf one)02:11
cjwatsonLast one didn't, but usually yes :)02:11
rsalvetihaha, indeed02:11
pmcgowancjwatson, btw why are you awake?02:12
pmcgowan;)02:12
cjwatsoninsomnia combined with too freaking much to do02:12
cjwatsoncombined with ooh-shiny about scalingstack02:12
rsalvetilol02:13
pmcgowanman02:13
cjwatsonbut I don't usually sleep that well anyway02:13
rsalvetiupdate-alternatives: using /usr/lib/i386-linux-gnu/mir/platformgraphics/android/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_mirplatformgraphics.conf (i386-linux-gnu_mirplatformgraphics_conf) in auto mode02:30
rsalvetiupdate-alternatives: using /usr/lib/i386-linux-gnu/mir/clientplatform/mesa/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_mirclientplatform.conf (i386-linux-gnu_mirclientplatform_conf) in auto mode02:30
rsalvetistill same issue02:30
rsalvetihttps://launchpadlibrarian.net/180947443/buildlog_ubuntu_utopic_i386_ubuntu-touch_UPLOADING.txt.gz02:30
rsalvetislangasek: ^02:31
slangasekrsalveti: hmm03:00
slangasekrsalveti, cjwatson: right, even the direct seeding of libmirclientplatform-android doesn't fix it because something else in the ubuntu-touch dependencies alpha-sorts earlier and triggers pulling in -mesa <sigh>03:13
slangasekrsalveti, cjwatson: so I'm going to proceed with implementing ogra_'s livefs fix03:13
slangaseklivecd-rootfs, I mean03:13
bzoltan1rsalveti: slangasek: may I get a manual ack to the QtCreator plugin in the silo5? I have ,moved the qlick-reviewers-tools to the Recommends form the Suggests section. Yes, it is a desktop only package and a super minor change.03:30
bzoltan1rsalveti: slangasek:  the qlick-reviewers-tools  is available in Utopic and Trusty of course03:30
imgbot=== trainguard: IMAGE 156 DONE (finished: 20140729 03:35) ===03:34
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/156.changes ===03:34
* ToyKeeper waits for 156 to finish flashing03:46
veebersslangasek: if I build the packages in my silo, will that impact or hold up other builders that people might want access to to get out of traincon0?04:03
bzoltanveebers: ToyKeeper: do you know anybody who could ack that ^^^ package?04:05
bfillerslangasek: what team do I need to be on set importance and assignee on ubuntu source package bugs (like this one: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1346502)04:05
ubot5Launchpad bug 1346502 in messaging-app "It can be very slow to load a conversation" [Critical,Confirmed]04:05
veebersbzoltan: ack as in QA approve? If so I only know of ToyKeeper. Otherwise robru perhaps?04:05
bzoltanveebers: no,  QA approve is not what I need, the package changed a dependency.04:06
ToyKeeperSo... bad news.  Image 156 is broken in exactly the same way as 155.04:06
ToyKeepercjwatson, slangasek: ^^^04:07
veebersbzoltan: ah right, not sure then sorry04:07
ToyKeeperbzoltan: Honestly, it's hard to move forward in the landing process at this time of day, since none of the right people are around.04:08
ToyKeeper... and image 156 didn't fix the critical bug it was supposed to fix, so we're kind of stalled.04:09
ToyKeeperLate-NZ hours are sparsely populated.04:10
veebersToyKeeper: Would you have any idea on when traincon-0 might be lifted (just out of interest)? i.e. if a new fixing image was spun up right now would it take, hours or 10's of minutes?04:12
ToyKeeperveebers: If the new image started now and had the correct fix in it, I think traincon could be lifted as soon as the .eu release manager logs on and checks the test results.04:21
ToyKeeperveebers: Yup, the crit that 155 was supposed to fix seems to be fixed...  so now we just need to fix the crit introduced in 155.04:25
ToyKeeperIf that's fixable before 157 builds, I'd assume 157 will get promoted and end traincon 0 sometime in the next ~10 hours or so.04:27
slangasekbfiller: importance/assignee> Ubuntu bug control; https://wiki.ubuntu.com/UbuntuBugControl04:30
slangasekveebers: building in a silo is fine wrt TRAINCON-0, unless the silos are so committed that we don't have a place for critical builds04:30
slangasekToyKeeper: yes, sorry, should've said - rsalveti IDed 156 as broken the same way as 155 during the build, I'm spinning 157 now which should fix it04:31
slangasekbzoltan: I've queued up https://ci-train.ubuntu.com/job/landing-005-2-publish/79/ to look at, but I need to run out to the store so it'll be a bit04:32
bzoltanslangasek: thank you04:32
bfillerslangasek: thanks04:33
slangasekbzoltan: alternatively, I may find myself with a few minutes to spare while waiting on livecd-rootfs to fully publish, and just get it done04:38
bzoltanslangasek:  that would be cool.. the whole release is two lines change :)04:38
slangasekyeah - change looks fine, now I need to find the button04:39
slangasek(which is basically "log in to jenkins")04:39
slangasekbzoltan: approved04:39
imgbot=== trainguard: IMAGE 157 building (started: 20140729 04:40) ===04:39
bzoltanslangasek:  you rock. thanks04:39
ToyKeeperslangasek: Awesome, didn't know you were still around.  :)04:40
slangasekToyKeeper: to my growing chagrin04:40
ToyKeeperPeople will be quite pleased to have the landing process unblocked though.  :)04:41
olliToyKeeper, that's an understatement ;)04:43
elopiocihelp: something is wrong with the unity unlock script05:30
elopio  File "/usr/lib/python3/dist-packages/unity8/process_helpers.py", line 178, in _get_unity_pid05:30
elopio    return int(status.split()[-1])05:30
elopioValueError: invalid literal for int() with base 10: 'start/running'05:30
elopioI guess that it's no longer printing the process id when it's run.05:31
elopioSaviq ^05:31
elopioThis comes from the latest dash results: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/576/consoleFull05:31
plarselopio: 155 and 156 look like they are in bad shape, from the mailing list, I know 155 has a broken UI. I suspect 156 has the same problem but I haven't tried it yet locally05:40
plarselopio: yeah, see the scroll back, but never fear - 157 will save us all!05:41
plars:)05:41
slangasekwell, I can't imagine why that would yield a 'start/running' result though05:43
veebersslangasek: sweet thanks, I just didn't want to tie up resources that were going to sorting out the crit issues.06:04
veebersToyKeeper: I see, thanks :-)06:04
slangasekimage 157 built successfully, not waiting for delta generation06:58
imgbot=== trainguard: IMAGE 157 DONE (finished: 20140729 07:05) ===07:04
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/157.changes ===07:04
slangasekToyKeeper, davmor2, sil2100: ^^ there; image 157 built without -mesa bits07:07
ogra_and does it boot ?07:09
ogra_:)07:09
ToyKeeperAwesome.  Flashing again...07:11
slangasekogra_: that's for someone east of me to figure out ;P07:11
ogra_heh07:11
ogra_do we have any explanation why this happened at all ?07:11
ToyKeeperogra_: Side effect of a long-standing build issue, and we simply saw more symptoms today.07:12
ToyKeeperThe build pulls in both desktop and phone packages, and the result depends on which one gets configured first.07:12
ogra_hmm07:12
ToyKeeperIt shouldn't be pulling in the desktop packages at all though.07:12
ogra_still interesting that it came just out of the blue07:12
slangasekno, that's really not interesting07:12
ogra_(i know about the alternatives issue, we have it since years in different variations)07:13
slangasekbecause the configure ordering of the packages is *arbitrary* and it was an accident that it worked at all before07:13
ToyKeeperNot sure what exactly changed to trigger new symptoms, but the fix is pretty much the same either way.  We need to get rid of the desktop packages anyway, to save space.07:13
slangasekthis was a build that changed the set of packages installed (some packages added, some packages removed) - that's enough to trigger it07:13
ogra_that were many of the 150 builds before too07:14
ToyKeeperIn some ways, it's kind of nice that this was brought up, since it provides an obvious way to reduce the image size right when we need to make it smaller.07:14
jibel157 boots, there is a display but binder_2 uses 100% CPU07:26
ToyKeeperRight, duh.  First boot never sees media.07:31
jibelback to normal after another reboot.07:31
ToyKeeperSix crash dumps so far...  seems like we don't really put a high priority on that though.07:38
* sil2100 has his fingers crossed for #15707:38
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
sil2100uh07:38
ToyKeeperThe thumbnailer crashing is new, though.07:38
ToyKeeperNot sure when the next tester will be around, but I need to be up in a few hours and I'm not sure I should start a 2-hour testing session.07:44
ogra_ToyKeeper, davmor2 and popey should be around soon ... dont bother, get some sleep07:44
sil2100ToyKeeper: davmor2 should be up in around 30 minutes07:44
sil2100ToyKeeper: thanks for working on this and have have a nice night ;)07:45
ogra_++07:45
ogra_and slangasek too !!!07:45
sil2100Indeed! I already said goodnights to slangasek though!07:45
ToyKeeper#157 definitely looks like a huge improvement so far, but that's without going into a lot of detail.07:45
sil2100ToyKeeper: that... that's one of the nicest things I heard recently!07:46
sil2100;p07:46
ogra_yeah, compared to two unbootable images the one eyed image is king ;)07:46
ToyKeeper(in other words, nothing user-visible exploded yet)07:47
ToyKeeper'night, and good luck.  :)07:47
jibeli've a gallry-app crash when I delete a picture with 157, https://errors.ubuntu.com/oops/50a2cd30-16f4-11e4-8cfb-fa163e4aaad407:48
sil2100jibel: does it happen every time?07:52
popeyis #157 okay to flash to?07:52
jibelsil2100, not every time.07:52
jibelpopey, 157 is okay.07:53
mhr3sil2100, could you (or get someone to) help pete with silo 008? unity-scopes-shell now deps on location-service, which isn't buildable on arm64 etc, so scopes-shell is no longer buildable there either07:53
sil2100mhr3: uh, hmm...07:54
tvosssil2100, mhr3 let me see if I can fix arm64 for location-service07:54
mhr3tvoss, it's also ppc and ppc6407:54
tvossmhr3, ack, on my list07:55
sil2100mhr3: I'll try, but this basically means that we'll have to remove -shell for those 3 archs - can't we somehow work around it?07:55
sil2100Ah ok, that would be best07:55
mhr3pete-woods, fyi ^^07:55
popeythanks jibel07:57
tvosssil2100, we would have to conditionally include build dependencies for location service to compile on arm64 and ppc08:02
sil2100tvoss: what build dependencies would that have to be?08:02
tvosssil2100, I think libubuntu-platform-hardware-api-headers and libubuntu-platform-hardware-api-dev,08:02
sil2100tvoss: ok08:04
Saviqsil2100, hey, can you please upload http://people.canonical.com/~msawicz/ubuntu-touch.tar.xz to silo 6?08:14
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: sil2100, trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. TRAINCON-0. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
robruSaviq, ah sorry about that, I uploaded it but I guess it was rejected08:17
tvosssil2100, back ... did you reply to the list of build dependencies?08:18
robruSaviq, so I guess if I can't upload it with your signature, I'll need to upload it with my signature, which will require me to build the source package myself.08:19
Saviqrobru, you should be able to just resign it with debsign08:19
davmor2boo!08:19
SaviqI *think*08:19
davmor2ogra_, sil2100: I'm guessing that 157 fixes the world if the spam I'm getting from irssi is right08:20
davmor2are we looking at this image for promotion then if it works?08:20
robruSaviq, debsign failed because I don't have your secret ey08:20
Saviqrobru, oh interesting... just go for it, rebuild it08:21
robruSaviq, ok uploaded, should be good for real this time08:23
seb128you don't need to rebuild the source to sign a .changes/dsc08:23
Saviqrobru, thanks08:23
robruSaviq, you're welcome08:23
seb128just design -k<key> .changes08:23
seb128debsign08:23
robruhmm08:24
sil2100tvoss: yeah, I said that it makes sense...08:24
robruseb128, thanks, too late ;-)08:24
seb128yw08:24
popeyupdated to #157 took 17 minutes at the google logo08:24
sil2100tvoss: but will location-service compile without libubuntu-platform-hardware-api-headers etc.?08:24
tvosssil2100, yup, the build setup checks for the header files separately08:24
robruSaviq, yep, just got the email, looks accepted08:25
sil2100tvoss: ok, and it will still *work* for those platforms?08:25
Saviqrobru, \o/08:25
Saviqrobru, and shouldn't you sleep?08:25
sil2100robru is still in Europe or has a jetlag ;)08:25
robruSaviq, I'm in Strasbourg for GUADEC, it's 10AM here ;-)08:26
Saviqrobru, ah good :)08:26
sil2100tvoss: if you have a branch for that, just push it to mhr3 or pete-woods so they can add it to their landing :)08:26
pete-woodstvoss: FYI I already have this MR for some packaging issues with location-service: https://code.launchpad.net/~pete-woods/location-service/dev-packaging/+merge/22845708:27
tvosssil2100, *work* yes, but not using an android chipset :) which is somewhat expected I would say08:28
sil2100Indeed ;)08:28
robrusil2100, how's it going? is image 157 ok08:33
robru?08:33
=== vrruiz_ is now known as rvr
sil2100Ok, firefox crashing on closing hangouts is really annoying08:48
sil2100robru: davmor2 is dogfooding it now, but it boots on all supported platforms!08:49
sil2100(SHIP IT)08:49
* davmor2 slaps sil2100 repeatedly08:49
sil2100Ouch08:49
davmor2sil2100: I has Music and video so that is mediascanner fixed now to ensure they work in the players :D08:52
robrusil2100, ah great08:54
tvosssil2100, pete-woods https://code.launchpad.net/~thomas-voss/location-service/fix-1349746/+merge/22862809:06
tvosspete-woods, could you add that mp to your silo?09:06
pete-woodstvoss: will do09:06
tvosspete-woods, thank you09:06
pete-woodstvoss: actually I already added a change that does exactly the same thing (after what you said earlier in the channel)09:07
pete-woodswas just checking whether it would build09:07
pete-woodstvoss: https://launchpadlibrarian.net/180965111/buildlog_ubuntu-utopic-ppc64el.location-service_2.0.1%2B14.10.20140729-0ubuntu1_FAILEDTOBUILD.txt.gz09:07
tvosspete-woods, ah, let me fix that09:09
pete-woodstvoss: https://code.launchpad.net/~thomas-voss/location-service/fix-1349746/+merge/22862809:14
pete-woodsis that the change you're making?09:14
pete-woodswhoops09:14
pete-woodsI meant that: https://code.launchpad.net/~pete-woods/location-service/dev-packaging/+merge/22845709:14
tvosspete-woods, yup09:14
pete-woodstvoss: ^09:15
tvosspete-woods, yup09:15
tvosspete-woods, let's take your branch then, I will abandon mine09:15
pete-woodstvoss: okay, just check it actually builds first, though :)09:16
pete-woodswoot! ppc64el build succeeded!09:28
pete-woodstvoss: we still seem to have a depwait on ppc for libnet-cpp-dev09:31
tvosspete-woods, okay, let me take a look09:31
tvosssil2100, could you help here: https://launchpadlibrarian.net/180475523/buildlog_ubuntu-utopic-powerpc.net-cpp_1.0.0%2B14.10.20140718-0ubuntu1_MANUALDEPWAIT.txt.gz09:34
tvoss?09:34
cjwatsontvoss: hm, how did that build anywhere?  net-cpp is in main, those packages are in universe09:45
thostr_can I get a silo for line 3309:45
cjwatsontvoss: I suspect there was actually a different failure in the PPA09:45
tvosscjwatson, hmmm ...09:45
cjwatsonbut it may not be accessible any more09:45
tvosscjwatson, so the build-dependencies are only used in testing09:46
tvosscjwatson, I guess that's why09:46
cjwatsontvoss: ah, here's the real failure.  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-008/+build/619426009:46
cjwatsontvoss: That might have passed if only somebody had hammered retry on it a few times at the time09:46
tvosscjwatson, yup, agreed ... the test is testing timeout behavior -> recipe for flakyness09:47
cjwatsontvoss: but still, the main -> universe build-deps are a violation, they either need somebody to follow the MIR chain or we need to drop them09:47
cjwatsontvoss: that said, for the purposes of this change, you could just do a no-change rebuild of net-cpp in that silo, and we could make sure all its builds complete09:48
tvosscjwatson, so it's only jsoncpp, correct?09:48
cjwatsontvoss: we don't actually need to address this right now09:48
cjwatsontvoss: and python-flask-script09:48
tvossah, looked up python-flask09:48
cjwatsonhttp://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html says there are no MIRs filed for these as yet09:48
tvosscjwatson, ack, putting it on my list to drop them09:49
cjwatsonbut anyway, just do a no-change rebuild in a silo for now and we should be able to get it built09:49
tvosscjwatson, just asked pete-woods to do so09:49
tvosscjwatson, I'm trying to add an mp to line 35 in the spreadsheet but I cannot edit that line anymore. Is it locked somehow?09:49
cjwatsonhow's dogfooding looking?  I think the libav megatransition might be about to land09:49
cjwatsonsil2100: ^- can you check tvoss's spreadsheet problem?09:50
tvosssil2100, I would like to have https://code.launchpad.net/~thomas-voss/location-service/fix-1349704/+merge/228632 added to the silo as it is waiting on silo6 anyways09:52
tvosssil2100, if there are conflicts, I'm happy to handle them09:52
tvosssil2100, and while you are at it: https://code.launchpad.net/~thomas-voss/location-service/fix-1347887/+merge/228561 should be fine, too09:53
pete-woodscjwatson: hi, could you reconfigure silo 8? (with the stuff tvoss was talking about in it)09:55
pete-woodsI've just added a no-change MR for net-cpp09:55
cjwatsonsure, one moment, although please note that normally you should ask the person listed under "CI Train support" in the topic09:55
pete-woodscjwatson: okay, good to know :) (this is really my first ci-train experience, so learning everything here)09:56
cjwatsonpete-woods: done09:57
pete-woodsthanks!09:57
cjwatsonpete-woods: heh, I think it might need more force09:59
cjwatson"No new useful revision published compared to dest, no need to upload this component"09:59
cjwatsonpete-woods: want me to sort it out?10:00
cjwatsonneeds PACKAGES_TO_REBUILD: net-cpp, FORCE_REBUILD: yes, I think10:00
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): psivaa | CI Train support: sil2100, trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. TRAINCON-0. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
sil2100tvoss, cjwatson: yeah, let me take a look, I've been having breakfast10:00
pete-woodscjwatson: okay, thanks, I'd like to learn the rules myself, so I can sort things out in a pinch :)10:00
tvosssil2100, sure :)10:01
cjwatsonpete-woods: ok, I suggest aborting the current build and rerunning with the parameters above10:01
cjwatsonthere's a little red x in the top right of the jenkins console view if you haven't seen it10:01
pete-woodsyep, that's my favourite jenkins button so far :)10:01
* sil2100 checks the permissions10:02
sil2100tvoss: could you try editing the spreadsheet now?10:04
tvosssil2100, ack10:04
sil2100pete-woods: just so you know, use the red abort button with caution with build jobs ;)10:05
pete-woodssil2100: okay, I just use it when it goes into the waiting on buildwaits forever state usually10:05
sil2100pete-woods: it can lead to CI Train staying in an unknown state, if the build job gets aborted before the .config files are generated10:05
sil2100pete-woods: and that's the right way to go :)10:05
pete-woodsokay, will watch out for that10:05
sil2100tvoss: give me a sign if it works, since maybe some permissions got lost during the spreadsheet modifications10:06
tvosssil2100, nope10:07
tvosssil2100, not working, let me restart chrome10:07
sil2100tvoss: hmm, ok, back to the drawing board then10:07
tvosssil2100, nope, still not working10:08
sil2100tvoss: are you logged into the google account on the spreadsheet?10:09
sil2100tvoss: as I don't see you on the list of logged people10:09
tvosssil2100, of course not ... face -> desk10:09
sil2100;)10:09
Saviqtvoss, google is quite nasty recently when it comes to logging you out10:10
Saviqsil2100, could we have a silo for line 37?10:10
cjwatson final: abiword,acoustid-fingerprinter,alsa-plugins-extra,amide,aria2,aubio,audacious,audacious-plugins,audacity,avbin,avifile,bino,blender,bombono-dvd,cairo-dock-plug-ins,calligra,cantata,charybdis,chromaprint,claws-mail,cmus,criu,crtools,cups,curl,darktable,dff,digikam,dvbcut,dvdstyler,dvswitch,dwb,dynalogin,echoping,emacs24,empathy,eog-plugins,event-dance,evolution,evolution-data-server,exim4,exiv2,ffdiaporama,ffmpeg2theora,ffmpegt ...10:10
ogra_psivaa, the dashboard looks like we only have one device running tests ...10:10
cjwatson... humbnailer,ffmpegthumbs,ffms2,filezilla,forked-daapd,freetds,fuse-emulator-utils,gallery-app,geeqie,gexiv2,gimplensfun,glib-networking,gmerlin-avdecoder,gmerlin-encoders,gnash,gnome-color-manager,gnome-commander,gnome-documents,gnome-online-miners,gnunet,gnutls28,goldendict,gpac,gpscorrelate,grilo-plugins,gst-libav1.0,gthumb,guvcview,gwenview,handbrake,harvid,hedgewars,hugin,idjc,imms,inspircd,ircd-ratbox,jd,jitsi,jugglemaster,kde ...10:11
cjwatson... -runtime,kdeplasma-addons,kfilemetadata,kid3,kino,kphotoalbum,kradio4,krename,lebiniou,lftp,libabw,libam7xxx,libaudclient,libav,libavg,libcdr,libdlna,libe-book,libetonyek,libetpan,libextractor,libfreehand,libgadu,libgdata,libgroove,libinfinity,libkexiv2,libmicrohttpd,libmspub,libmwaw,libodfgen,libphash,libquicktime,librelp,libvisio,libwpd,libwpg,libwps,liggghts,lightspark,linphone,lives,loudmouth,luminance-hdr,lynkeos.app,marble,m ...10:11
sil2100Saviq: o/10:11
cjwatson... ediatomb,merkaartor,minbif,minidlna,miro,mlt,moc,motion,mpd,mplayer2,mpop,mpv,mrpt,msmtp,mythexport,neon27,nepomuk-core,network-manager-openconnect,ngircd,nifti2dicom,ola,opal,openconnect,opencv,openscenegraph,osm2pgsql,ovito,pan,paraview,pcp,performous,pinot,plasma-nm,protobuf-c,pyexiv2,qemu,qmmp,qutecom,rawstudio,renpy,riemann-c-client,rtmpdump,shotdetect,silan,spek,squeezelite,strigi,subsurface,survex,transcode,tupi,ubuntustudi ...10:11
cjwatson... o-meta,ucommon,ufraw,vdr-plugin-xineliboutput,viewnior,visp,vlc,vtk,vtk6,webfs,weechat,wireshark,writerperfect,wxsvg,x264,xbmc,xine-lib-1.2,xjadeo,xmlsec1,xmms2,xpra,yade,yaz,yorick-av,zoneminder10:11
cjwatsonfinally!10:11
cjwatson(sorry, slightly larger paste than I expected)10:11
tvosssil2100, mind reconfiguring?10:11
ogra_crazy10:11
sil2100Saviq: with override conflicts?10:11
sil2100tvoss: sure10:11
Saviqsil2100, yup, thanks10:11
psivaaogra_: let me take a look at it.. loading of dashboard takes ages for me10:12
ogra_psivaa, yeah, and it might be a dashboard issue after all ... but i only see what looks like only one device10:13
cjwatsonso that's a 206-package migration, took weeks to organise and just had to go for it, please don't ask me to back it out ... :-)  I hope the phone won't be affected significantly, but if it is let's try to move forward rather than back10:13
cjwatsonproposed-migration should be *much* faster after this10:13
ogra_we should make a policy that forbids more than 50 reverse build deps if you are not libc :P10:13
cjwatsonbecause code reuse is for other people? :P10:14
ogra_heh10:14
ogra_because it makes transitions easier :)10:14
psivaaogra_: only one mako has finished running the tests. the other two are still running10:15
psivaaso you're right :)10:15
ogra_heh10:15
Saviqsil2100, actually, recon on silo 5 please10:17
Saviqsil2100, had to add scopes...10:17
sil2100Saviq: ok ;)10:17
sil2100davmor2: soooo... how's it going so far?10:17
davmor2sil2100: so far so good10:18
sil2100ogra_, psivaa: but so far that one device that finished looks relatively ok... 3 additional failures in calendar though10:21
ogra_yeah10:21
ogra_well, lets see how the other two come out10:21
cjwatsonpete-woods: uh10:23
cjwatsonpete-woods: please don't reupload like that10:23
sil2100Oh, whole silo rebuild?10:24
pete-woodscjwatson: what did I do wrong?10:24
cjwatsonpete-woods: we can retry individual failed builds; hammering the build button in citrain does an entire new upload to the PPA, which triggers a rebuild on all architectures, which is wasteful10:24
cjwatsonin fact I'd already retried the failed build10:24
cjwatsonpete-woods: just hands off the build button for the moment please :)10:24
sil2100;)10:24
pete-woodscjwatson: it's an actual change — we disabled the flaky test for the moment10:25
cjwatsoncitrain's "Build" operation really needs to be called "Upload"10:25
cjwatsonah!10:25
cjwatsonok, my bad, I didn't think to check that the "null-commit" branch was still null10:25
pete-woodsyeah, it's not, needs a new name10:25
cjwatsonshame you didn't change the commit message10:25
pete-woodsforgot to do that!10:26
cjwatsontoo late now unless we do yet another upload10:26
sil2100hm, this gives me an idea... maybe I could add a 'rebuild uploaded packages' button in CI Train?10:26
pete-woodsthat would be really useful!10:26
cjwatsondo you mean "retry failures"?10:26
sil2100That would try rebuilding the failed builds in the silo PPA - but I wonder if I have API access to that10:26
cjwatsonyou do10:26
cjwatsonbuild.retry()10:27
sil2100Then awesome10:27
sil2100Let me add that later10:27
cjwatsonwell, anything in ~ci-train-ppa-service does10:27
cjwatsondon't just say "rebuild uploaded packages" though, because that implies that you can rebuild something that succeeded that way10:27
sil2100Yeah, righto, I meant rebuilding failed uploaded packages10:27
sil2100;)10:27
cjwatsonright, "retry" is the terminology for that in Launchpad so it should match10:28
pete-woodswould this "retry" button nudge the buildwait failures, like are in silo 8?10:49
sil2100Dep-wait failures you mean?10:49
pete-woodsyes, that's what I meant10:50
sil2100Not sure yet, but those actually get resolved by themselves once the dependency appears10:50
pete-woodssure, but you have to wait like an hour sometimes10:50
cjwatsonretry generally ought to prod those explicitly10:51
cjwatsonseeing as you need the watch-only machinery anyway10:51
cjwatsonmaybe you should be able to limit by arch10:51
cjwatsonor something10:51
sil2100I guess I might add various filtering, like per-arch and per-project10:52
cjwatsonpete-woods: FWIW it's a cron job that runs at :25 and :5510:52
pete-woodsoh, so max 30 minutes then :)10:52
cjwatsonshould be yes10:52
pete-woods3 mins to go :)10:52
pete-woodsI take it it'd be a ton of work to make the depwait retrigger happen in an event-based manner, rather than cron based?10:53
cjwatsonyep10:53
pete-woodsfair enough10:53
cjwatsonlet me introduce you to the Launchpad team with one full-time developer10:53
pete-woodswowsers10:54
cjwatsonactually I think two now - but anyway, seriously understaffed10:54
cjwatsongotta prioritise10:54
pete-woodsthis is the only company I have ever worked at where there are more projects than people10:54
cjwatsonthe other problem with making the dep-wait retry job be event-based is that IIRC it's much cheaper to compute this way round, so there's some tradeoff involved10:56
pete-woodsI believe in making the computers work harder, so I don't have to :)10:57
pete-woodsbut seriously, if you're the only guy making this whole thing work, then I totally understand10:58
pete-woodsso the build still hasn't kicked off 10 minutes after :55. is there usually a big queue of stuff that you have to wait for?11:05
sil2100davmor2: how far are you from finishing? :)11:07
davmor2another 30 minutes or so11:07
cjwatsonpete-woods: Not me, I only chip in from time to time11:11
cjwatsonpete-woods: seems to be running now11:11
pete-woodscool :)11:11
cjwatsonthere may have been a short queue, yeah11:11
cjwatsonpete-woods: cheaper to compute - can make a practical difference, especially if you overflow a time slot or end up massively slowing something else down that something else relies on being quick11:12
cjwatsonanyway, I'm handwaving11:12
cjwatsonpete-woods: (Launchpad is mainly William, under CI)11:13
pete-woodsokay, that's good to know11:13
psivaaogra_: sil2100: some app tests failed miserably... failing to launch the app it seems. i'd rerun the tests if there is no objection11:15
sil2100ugh11:16
psivaai.e. if dogfooding showed any similar behaviour11:16
sil2100psivaa: is that problems with launching the app or screen unlock?11:16
psivaadavmor2: ^ did you notice anything similar.. sorry i dint read the backlog if you've already said anything to that effect11:16
sil2100psivaa: did all those happen on one device?11:17
psivaasil2100: in two devices11:17
psivaasil2100: it's in launch app step afaics11:17
sil2100Grrr11:18
sil2100psivaa: ok, try re-launching, let's see how it goes11:18
davmor2psivaa: seems to be fine here which apps I've only tried a few11:18
=== pete-woods is now known as pete-woods|lunch
psivaadavmor2: sil2100: ack, thanks11:20
=== MacSlow is now known as MacSlow|lunch
sil2100davmor2: it fails launching for instance notes, gallery, clock, camera etc.11:25
sil2100davmor2: on smoketesting that is11:25
davmor2sil2100, psivaa: they all open but take about 7-10 seconds11:27
ogra_oh, look, only 101 failures :P11:27
sil2100oh?11:27
sil2100I don't see anything specific in 15511:28
ogra_tvoss, send some diplomats, quick !11:29
sil2100There was only upstart and lightdm11:29
=== tvoss is now known as tvoss|lunch
psivaasil2100: ogra_: davmor2: rerun of the gallery app test is not looking great. see similar failures as the original run ones on the first look11:30
ogra_sil2100, and android11:32
sil2100:|11:32
sil2100Why did we have a new android on 156?11:32
sil2100I mean, 15511:32
sil2100ARGH11:33
ogra_sd card support for the emulator it seems11:33
ogra_*shouldn't* have any impact11:33
sil2100We need moar eyeballs11:33
sil2100olli, pmcgowan: we seem to be having some problems with our latest images, we would need some people helping out in identifying which component broke11:34
ogra_i wonder if building gallery with exiv2 statically doesnt give us all the shared lib gives11:34
pmcgowansil2100, different issues than the ones in 156?11:35
sil2100ogra_: yeah, but that would just be gallery, while we had many other apps having the problem11:35
sil2100pmcgowan: yeah, so it seems now that some applications have problems starting during tests in smoketesting - and as what davmor2 mentioned, those apps seem to launch very slow11:36
ogra_there are a lot weird qmlscene errors in the notes-app log11:36
sil2100It seems to have started with 155 (most probably), as 154 had good test results11:36
ogra_sil2100, and apparmor denies the world ...11:37
ogra_https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/580/artifact/clientlogs/notes_app/syslog/*view*/11:37
ogra_i guess we have our issue there ...11:37
pmcgowanogra_, the new apparmor then?11:38
ogra_well, that only had a minor change in a totally different area11:38
ogra_not sure how it could cause this11:38
pmcgowandid ap change?11:38
ogra_nope11:38
ogra_and the apparmor change should only allow additional access to the files in /var/lib/extrausers ...11:39
ogra_(which it apparently does fine, else mediascanner would crash again)11:39
sil2100Crap11:40
ogra_jdstrand, any idea about that one ? https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/580/artifact/clientlogs/notes_app/syslog/*view*/11:41
sil2100But looking at the apparmor upload, it really shouldn't have any negative effect11:41
ogra_(once you are around)11:41
pmcgowanwhat was in the upstart changes11:41
ogra_upstart (1.13.1-0ubuntu2) utopic; urgency=medium11:41
ogra_  * Cherry-pick cgmanager text fix from upstream.11:41
ogra_nothing11:41
ogra_i mean ... well,if cgmanager would have issues our problems would be bigger (devices wouldnt finish booting)11:42
pmcgowanok11:42
olliinteresting11:50
pmcgowanmdeslaur, can you double check the apparmor changes for us11:50
pmcgowanor check that log above11:50
mdeslaursure, one sec11:50
pmcgowanthanks11:51
ogra_well, i tested the apparmor changes for jamie ... but only on a running device ... not with AP tests11:51
ogra_(to verify the bug was gone)11:51
ogra_now someone explain to me why this is specific to only one of the test devices11:52
pmcgowanoh?11:52
ogra_i mean all app tests run that introspection stuff11:52
pmcgowanright11:52
ogra_http://ci.ubuntu.com/smokeng/utopic/touch/mako/157:20140729.2:20140728.1/9355/11:52
ogra_all tests that ran on the first mako passed fine11:52
ogra_all that ran on the second one didnt11:53
mdeslaurogra_: is there a special apparmor rule for the autopilot stuff?11:53
* mdeslaur has no idea how this works11:53
ogra_mdeslaur, heh, no clue :)11:53
davmor2pmcgowan, ogra, sil2100: every apps is taking between 7-10 seconds to open I've opened them all now, worse ones seem to be "web apps, shorts, browser, calendar and Music app" everything else then opens around 7 seconds11:53
sil2100ogra_: psivaa said it was on 2 devices11:53
pmcgowandavmor2, whats top say11:53
ogra_sil2100, well, i'm only talking about the two we see on the dashboard yet11:53
ogra_once the third one shows up it will likkely get even worse :)11:53
ogra_davmor2, i cant confirm that on my flo11:54
mdeslaurogra_: so, one of the autopilot and/or jenkins scripts is supposed to tell apparmor that this is running in test mode I believe, and that doesn't seem to be happening11:58
ogra_right, but apparmor was the only bit that got changed here12:00
mdeslaurah, I think it's the autopilot-touch package that does it12:00
* mdeslaur pokes more12:00
* ogra_ still doesnt get why we have one device properly passing 12:01
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: sil2100, trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. TRAINCON-0. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
pmcgowanevery thing seems normal to me here12:03
=== pete-woods|lunch is now known as pete-woods
davmor2pmcgowan: so cpu usage goes off the chart and then it slows right down again once the app is open, Exapmles, open music app 89-96% for qmlscene, upto 67.8% for unity8, mediascanner hit 10-20%, thumbnailer hits 27%12:03
mdeslaurogra_: is there a way to see which packages are in the image?12:04
ogra_mdeslaur, http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/utopic-preinstalled-touch-armhf.manifest12:04
pmcgowandavmor2, that may be expected12:04
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cprov | CI Train support: sil2100, trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. TRAINCON-0. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
=== alan_g is now known as alan_g|lunch
ogra_mdeslaur, and changes are at http://people.canonical.com/~ogra/touch-image-stats/ ... you want to look at 155-15712:05
pmcgowanstartup times seem normally slow to me, not worse12:05
davmor2pmcgowan: nothing stays high though and I don't seen anything unexpected in the top 10 list12:05
pmcgowanright12:05
ogra_dropping letter starts in under 4sec for me here12:05
pmcgowanogra_, I assume we got new sdk libs to fix the original issue?12:06
ogra_filemanager between 4 and 512:06
ogra_pmcgowan, which original issue ?12:06
pmcgowanwell I dont know, why dd we get a new sdk libs ;)12:06
ogra_pmcgowan, because the seeds were updated for udisks2 ... no change in the libs, its is just rebuilt alongside12:07
pmcgowanogra_, cool thats what I meant12:07
ogra_(happends when you rebuild meta to add something to -touch)12:07
pmcgowanogra_, so what about the fact tests ran fine in some cases, thats a race, or some diff in the environments12:09
ogra_rather the latter12:10
ogra_we got a new initrd in 154 .. i wonder if the kernel partition possibly didnt get updated properly on some devices12:11
mdeslaurogra_: what is "phablet-config"?12:11
ogra_mdeslaur, a tool to adjust certain bits on an image (skip the welvcome wizard ... skip the intro tutorial, make sure the screen stays unlocked)12:12
ogra_comes from phablet-tools12:12
mdeslaurogra_: ok, that's what adds the autopilot rules to apparmor...can we tell if it ran or not?12:12
ogra_https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/583/consoleFull has the full console output of the server that ran the test on the phone12:13
ogra_mdeslaur, which phablet-config command  would do that ?12:14
* ogra_ sees "+ phablet-config autopilot --dbus-probe enable"12:14
=== MacSlow|lunch is now known as MacSlow
pmcgowanogra_, did the dashboard results change? I see 69 fails now12:19
ogra_pmcgowan, yes, as psivaa re-runs tests and they pass it gets updated12:19
pmcgowansun spots12:20
ogra_UITK tests completely failed though12:20
psivaaogra_: yeam UITK, was in an infinite look of dragging a coordinate. so it would have hung forever. i had to abort it and rerunning again12:21
psivaaogra_: also, we've seen the devices wait here forever in a couple of different devices:12:25
psivaa014/07/29 08:22:26 Rebooting into recovery to flash12:25
psivaa+ adb wait-for-device12:25
psivaaogra_: in fact 3 devices12:25
mdeslaurogra_: where does click_image_tests come from?12:25
davmor2sil2100: so on the whole I'm happy but those test results look awful12:27
davmor2lunch brb12:27
ogra_mdeslaur, looks like from the test server, no idea12:32
ogra_mdeslaur, for that side better ask psivaa or plars12:32
ogra_well, click_image_tests seems to be a commmand of jenkins.sh12:33
psivaamdeslaur: ogra_: click image tests is to run this script basically to check if the downloaded click packages match that in the archive:12:36
psivaahttp://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/tests/click_image_tests/check_preinstalled_list/check_preinstalled_list.py12:36
ogra_sil2100, so looking at flo we seem to have a few unity8 crashers we didnt have before12:41
ogra_mako has one in sudoku-app12:42
=== alan_g|lunch is now known as alan_g
ogra_and webbrowser seems to crash too during its test12:42
* jdstrand is here12:45
pmcgowanjdstrand, many dashboard tests were failing with an apparmor denial on introspection12:47
jdstrandwhat is the denial12:47
jdstrand?12:47
pmcgowanhttp://ci.ubuntu.com/smokeng/utopic/touch/mako/157:20140729.2:20140728.1/9355/notes_app/1448978/12:48
pmcgowans an example12:48
jdstranddid the test tool change?12:49
pmcgowanjdstrand, mdeslaur was checking that things got set up properly12:49
pmcgowanI dont know, I am told not12:49
mdeslaura test was added12:49
ogra_jdstrand, seemingly nothing relevant changed ... as usual :P12:49
jdstrandright. looking at the denial, it seems like aa-clickhook didn't get run to add the autopilot rule12:49
mdeslaurand that test makes adb-shell 'aa-clickhook -f --include=/usr/share/autopilot-touch/apparmor/click.rules' get run12:50
jdstrandthe apparmor upload should not have caused this12:50
ogra_yeah, very unlikely12:50
mdeslaurnah, it's not caused by the apparmor upload12:50
mdeslaurjdstrand: I was comparing https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/583/consoleFull with https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/572/consoleFull12:51
mdeslaurbut didn't see anything relevant beside the fact that there's a new test that makes aa-clickhook get called earlier12:51
jdstrandinteresting12:52
jdstrandis the click getting installed after the aa-clickhook call?12:53
mdeslaurbut I couldn't find where it was called in 572, or what calls it12:53
jdstrandthis seems like a test tool issue12:53
jdstrand572 doesn't have aa-clickhook at all, but 583 does13:01
jdstrandsomething is different with the test runner. whoever made that change needs to look at this13:01
jdstrandpmcgowan: ^13:02
jdstrandpmcgowan: is 583 the first to fail?13:02
pmcgowanjdstrand, who owns that?13:02
pmcgowanjdstrand, the last two builds couldnt be tested, so yes, 157 is first since 15413:02
jdstrandlet me diff the consoleText between the two13:05
jdstrandmdeslaur: how did you pick 572?13:07
mdeslaurjdstrand: it looked like the previous one that passed13:08
jdstrand572 is 300K and 583 is almost 10M13:08
* jdstrand keeps looking13:08
pmcgowando you know which build corresponds to 572?13:08
mdeslaur(I looked here: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/)13:09
mdeslaurjdstrand: perhaps 582 would be sufficient, since the aa failures aren't in that one13:10
jdstrandhow do I map http://ci.ubuntu.com/smokeng/utopic/touch/mako/154:20140728:20140725.1/9323/ to a consoleFull?13:10
jdstrandnm13:11
jdstrandhttps://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/568/consoleFull13:11
jdstrand582 was started by hand13:16
jdstrand568 has: Started by build flow utopic-touch-mako-smoke-master#16413:16
jdstrand582 has: Started by user Parameswaran Sivatharman13:16
jdstrandwell, it looks like it was started by hand13:17
pmcgowanpsivaa, ^^13:17
pmcgowanjdstrand, you think thats relevant?13:17
sil2100Sorry, just back from lunch13:17
jdstrand568s log is 1.5M, 582 is almost 1013:17
jdstrandI'm trying to compare apples to apples in my consoleText diff13:18
psivaajdstrand: curious how it'd impact13:18
jdstrandpmcgowan: is http://ci.ubuntu.com/smokeng/utopic/touch/mako/157:20140729.2:20140728.1/9355/ what people are worried about?13:18
psivaathe -master job purely does the trigger which i did manually13:19
pmcgowanjdstrand, yes13:19
jdstrandpsivaa: I don't know. did a new infrastructure, tool, runner, something get pushed out recently?13:19
psivaajdstrand: not that i know of. probably plars knows?13:20
jdstrand(fyi, I referenced 582, but I actually meant 583 the whole time, which corresponds with http://ci.ubuntu.com/smokeng/utopic/touch/mako/157:20140729.2:20140728.1/9355/)13:21
psivaajdstrand: the above link contains results from 579 to 584 jenkins jobs.13:23
balloonsfginther, any luck with https://code.launchpad.net/~fginther/ubuntu-test-cases/add-reminders/+merge/226281?13:23
psivaajdstrand: you'd need to click each app results and follow the links to see the actual jenkins job corresponding to a particular app test13:24
fgintherballoons, yes. I was able to get 14 passing autopilot tests13:26
balloonsfginther, awesome :-) So it's ready for the dash then?13:27
fgintherballoons, yes, the tests should be ready with your MP (I even tested with a .click based on your MP). I need to do a little more cleanup of my branch and get it reviewed13:28
fgintherhopefully will have that ready by EOD13:28
pmcgowanpsivaa, who else can assist in debugging this?13:29
psivaapmcgowan: what information do you want to know specifically13:30
plarspsivaa: what's the issue?13:31
psivaaplars: jdstrand was asking 'did a new infrastructure, tool, runner, something get pushed out recently?'13:32
plarspsivaa: but what's the problem you are seeing?13:32
psivaaplars: look at the dashboard13:32
plarspsivaa: we made a change to the channel being tested, from utopic-proposed to devel-proposed, which is an alias. That happened last Friday13:33
plarspsivaa: I looked last night and 155/156 were clearly broken13:33
pmcgowanyes those builds were doa13:33
pmcgowanbut 157 is "good" but not passing13:34
plarspsivaa: 157 seems to have had a device die during uitk tests, and lots of failures on notes and gallery which appear to be new13:34
psivaaplars: right, thats the issue. i aborted the uitk one first time since it had an infinitely repetitive step13:35
pmcgowanpsivaa, have we rerun the notes or gallery tests? is that a kosher part of the process?13:35
davmor2plars: 155 was a broken image didn't boot as such13:37
psivaapmcgowan: yes, the results showing in the dashboard for gallery and notes are from the second run. the first run also had the same filures13:37
pmcgowaninteresting13:37
psivaapmcgowan: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/580/#showFailuresLink is the first set13:38
psivaahttps://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/583/#showFailuresLink is the second set13:38
plarspmcgowan: absolutely, but we should keep an eye on it even if it starts to pass again. It might be good for someone from QA with deeper autopilot knowledge to take a look and see what autopilot thinks went wrong there.13:38
plarspsivaa: ah, so it already failed twice?13:38
psivaaplars: yes13:38
plars:(13:39
plarsprobably a legitimate failure then13:39
plarslet me see if I can reproduce locally13:39
psivaafirst one on mako-14 and the second one on mako-0613:39
plarspsivaa: oh, btw, did you see that I added those 3 extra instrumented makos last night? :)13:40
ogra_plars, we have two devices out of three misbehave in 15713:40
plarsogra_: I saw one of them during the uitk tests, but I haven't had time to look seriously at the other results yet. Where was the other?13:40
ogra_and the two that fail have weird AA denials13:41
plarsI assume it was before one of the reruns that psivaa did already?13:41
plarsogra_: hmm, did something change with aa that we need to account for in the device provisioning?13:41
psivaaplars: yes, i've had a few reruns. and the issue appeared afterwords too.13:42
jdstrandplars: no13:42
ogra_plars, right and the dashboard only showed the successfull one for quite a while ... i think mako-06 is definitely borked13:42
psivaaplars: the instrumented ones are now then 12,13,14 & 15?13:42
pmcgowan<ogra_> we got a new initrd in 154 .. i wonder if the kernel partition possibly didnt get updated properly on some devices13:42
ogra_oh, right13:42
jdstrandplars: the autopilot apparmor rules are either not being applied or being unapplied13:42
ogra_but all devices get installed with --bootstrap13:42
plarsogra_: mako-06 has been problematic, I'll pull it for now so we don't get reruns on it13:42
ogra_theoretically they *should* get updated13:43
plarsI've not seen it fail like that before13:43
ogra_yeah13:43
plarsjdstrand: any idea how on earth that could happen? Could a bad device really have such an effect?13:43
jdstrandplars: there was an apparmor update, but it had no code changes and was extremely minimal13:43
plarsI'd expect it to just die/crash rather than strange things like that13:43
jdstrandplars: well, I am comparing the test output from 568 and 583-- 568 is 1.5M and 583 is nearly 10M13:44
jdstrandplars: (consoleText)13:44
plarsjdstrand: well I think psivaa said one of them was caught in a loop and he killed the job after a while13:45
jdstrandthat is why I asked about test infrastructure13:45
plarsjdstrand: only change on our side happened over the weekend, and it was the announcement I made to the ML. We added a new channel, and changed one of the channels to point at the devel-proposed alias rather than the utopic-proposed channel13:45
plars(which is the same image)13:45
jdstrandI need to be able to compare 568 with something that is a comparable but failing run if I am going to be able to help diagnose13:46
plarsthere's still some reporting stuff we need to clean up there, but that's trivial. Runs have happened successfully since those changes, and nothing clearly would have had an impact on this13:46
psivaajdstrand: if you see the console in 583, we see those quite a lot of errors/ failures. that could add to the log size?13:46
=== tvoss|lunch is now known as tvoss
jdstrandI don't know-- I got dragged in to this cause there were apparmor denials. there are apparmor denials because the autopilot apparmor rules aren't being applied correctly13:47
psivaajdstrand: and 568 has only 2 failiures and that too is with image 154. not sure if you could compare those two tbh :)13:47
bfillersil2100: can I have a silo for line 33 please?13:47
jdstrandthat is the extent of what I can say about this atm (sorry I'm not more familiar with the test infrastructure)13:47
bfillersil2100: I mean line 32 :)13:48
sil2100bfiller: sadly, we're critically low on silos right now, we need to have 1 free one in case of a blocker fix ;)13:48
pmcgowansil2100, we can give up 18 for now13:48
bfillerit's fine, I can wait until one frees up13:49
jdstrandpsivaa: if I had two test runs that were more alike, I might be able to help more13:49
psivaajdstrand: more alike but one with the latest image?13:50
psivaaif that's the case, not sure how we match that13:51
psivaaplars: ^ any idea?13:51
jdstrandpsivaa: I was told that 583 had some sort of looping issue with it. 568 did not. that seems to indicate that there is something wrong with 583 results and the looping issue should be fixed first13:51
jdstrandpsivaa: once that is fixed, we should have results that we can compare13:52
plarspsivaa: I'm trying gallery_app by itself locally right now13:53
psivaajdstrand: 583 did not have the looping issue13:53
jdstrandpsivaa: ok. why is its consoleText almost 10M and 568s is 1.5M?13:53
jdstrandI need to understand that change13:54
jdstrand(if I am supposed to help)13:54
psivaajdstrand: that's because the number of failures is higher in that13:54
jdstrandI'll keep looking at it then. but it is clear that the autopilot apparmor rules are not being applied or are being unapplied at some point13:55
jdstrandyou are *sure* nothing changed in the tools to change the ordering of when clicks are installed, etc?13:56
psivaajdstrand: we dint deliberately change that. let me double check if the are installed in the same order with 56813:57
jdstrandpsivaa: are these things using the new click autopkgtest support?13:57
psivaajdstrand: i dont know what 'the new click autopkgtest support' means.. sorry. plars do you know?13:59
* jdstrand wonders if this is related to the discussion in bug #133725313:59
ubot5bug 1337253 in click-apparmor (Ubuntu) "Doesn't apply --include to newly installed clicks" [Undecided,Won't fix] https://launchpad.net/bugs/133725313:59
plarspsivaa: I think that's the stuff fginther was working on so that reminders could work, and no it's not landed yet. I was going to try to take a look soon, but the mp is on hold14:00
sil2100pmcgowan: ok, let's do that then, let me free up silo 1814:00
psivaajdstrand: i just diff'ed the initial setup bits of the phones on 583 and 568. dont see any difference14:10
jdstrandpsivaa: I see a difference in the output: http://paste.ubuntu.com/7895341/14:11
jdstrandpsivaa: '<' is 568 and '>' is 58314:12
jdstrandpsivaa: seems the provisioning code changed?14:12
* jdstrand checks when 'reprovisioning device with' string happens14:13
psivaajdstrand: that's the part of the stuff used to see if the device already has that image. i dont think it's relevant here14:13
psivaaright, reprovisioning happens when a job is rerun14:13
jdstrandthat is all before aa-clickhook14:13
* jdstrand keeps looking14:13
psivaajdstrand: the bits after '+ log 'FLASHING DEVICE'14:15
psivaa' id not that different14:15
psivaa*is not that different14:15
popeycprov: can someone help me with http://s-jenkins.ubuntu-ci:8080/job/weather-app-click/lastBuild/console ?14:17
popeyweather app is repeatedly failing to build14:17
popeyballoons: can you pelase push the core apps clicks to the store?14:18
balloonspopey, all of them?14:18
cprovpopey: in a minute and can gather fginther too.14:18
popeyyup, although skip weather for now as it's failing to build14:19
popeythanks14:19
fginthercprov, popey looking14:21
popeyta14:21
pmcgowanplars, any luck?14:25
jdstrandpsivaa: fyi, it would be nice if the 'Search for [<list of clicks>]' was sorted14:25
fgintherpopey, cprov, I found the problem, applied a quick fix and rebuilt the job. I'll also start work on a more permanent fix. There is difference in the jenkins user account on the failing machine that wasn't taken into account in the job14:26
jdstrandpsivaa: pull: /var/crash/.lock -> /var/lib/jenkins/slaves/mako-NN/workspace/utopic-touch-mako-smoke-daily/clientlogs/click_image_tests/.lock is missing in 583. what is that about?14:26
jdstrandoh I see14:27
jdstrandhrmm14:27
jdstrandthat is after the tests are run14:27
psivaayes, during results archiving14:27
jdstrandpsivaa: the only thing I can think of is the provisioning is different14:28
psivaajdstrand: curious as to how?14:29
plarspmcgowan: psivaa: the gallery_app run locally just finished (needed to provision)14:29
plars45 passes, 0 failures14:29
psivaagrrrrr14:29
pmcgowanyeah of course14:29
jdstrandpsivaa: I know that there were changes made to precompile apparmor policy. aa-clickhook should be getting run way after that, so I'm not sure it is relevant14:29
plarsit could be something odd caused by something before it14:29
sil2100:|14:29
plarsbut it's nothing in the scripts, I went through the same provisioning process locally that we do in the lab14:29
plarspmcgowan: I'm still digging14:29
jdstrandok, so plars just provisioned the same way psivaa did, presumably14:29
plarsI'm also trying notes_app right now, so at least we'll have results on those two14:30
plarsjdstrand: exactly14:30
fgintherpopey, http://s-jenkins.ubuntu-ci:8080/job/weather-app-click/236/ passed14:34
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): fginther | CI Train support: sil2100, trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. TRAINCON-0. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
jdstrandthis should be the differences between 568 and 583 before aa-clickhook is run: http://paste.ubuntu.com/7895519/14:36
jdstrandplars: do you know if the code in comment #8 of bug #1337253 is being used now?14:39
ubot5bug 1337253 in click-apparmor (Ubuntu) "Doesn't apply --include to newly installed clicks" [Undecided,Won't fix] https://launchpad.net/bugs/133725314:39
thostr_sil2100: can I get a silo for line 33?14:40
plarsjdstrand: probably not, we don't use autopkgtest, but let me look into it14:41
jdstrandI don't see any adt strings in the log14:41
jdstrandplars: ^14:41
sil2100thostr_: sadly, we're currently low on silos, with only one silo free right now... we hope to have more free if we resolve the traincon situation14:42
jdstrandplars: could be there isn't enough information to know why the autopilot rules aren't in place14:42
thostr_sil2100: ci sheet says we have two silos :)14:43
sil2100thostr_: bah, it's not updated yet ;p14:43
sil2100thostr_: in reality it should be 114:43
thostr_sil2100: ack14:43
=== alan_g is now known as alan_g|tea
* ogra_ considers if getting a vendor tray and sell silos on teh grey market is a good business model :) 14:44
sil2100;p14:45
rsalvetilet me validate the emulator now14:46
sil2100I guess that if we at least confirm that both notes and gallery pass when ran locally and davmor2 gives a final +1 on dogfooding, let's maybe consider promoting the image anyway14:47
sil2100(if emulator boots as well)14:47
ogra_sil2100, well, UITK doesnt run either14:48
rsalvetiemulator first boot doesn't get us to unity814:48
rsalveti=\14:48
plarsjdstrand: it does look like we do "aa-clickhook -f --include=/usr/share/autopilot-touch/apparmor/click.rules" This is also done by phablet-config autopilot14:48
sil2100Aw come on14:48
ogra_we are missing about 300 tests14:48
plarsjdstrand: It could be that it's run more than once though, would that cause any problem?14:48
plarsogra_, sil2100: please standby, I'm rerunning a lot of stuff right now both locally and in the lab14:49
ogra_yeah14:49
ogra_just telling sil2100 where we stand14:49
sil2100Ok14:49
ogra_didnt mean to complain or moan :)14:49
sil2100ogra_: ah, right, I didn't notice that it only had 5 tests ran ;p14:49
ogra_I#m doing that enough in other channels14:49
sil2100But it was yellow!14:49
sil210080%!14:50
ogra_shipit !14:50
plarsogra_: I didn't take it that way, I just want to make sure you know I'm aware and working on it. :) It's my focus right now14:50
ogra_:)14:50
ogra_thanks14:50
jdstrandplars: if it run more than once with the proper --include: no, it shouldn't matter. (though, if you think it is run multiple times at the same time, there could be a problem)14:50
plarsjdstrand: it wouldn't happen in parallel or anything, no14:50
rsalvetisil2100: ogra_: I get the wizard at least on the emulator, but not unity8 =\14:51
rsalvetinot even after a reboot14:51
plarsjdstrand: the only parallelization is across devices14:51
jdstrandplars: if aa-clickhook is run without the --include, then that would undo the rule. aa-clickhook is run on click install, so if a click gets installed later, that could undo the changes14:51
sil2100rsalveti: hmm... then maybe the UITK -gles bits weren't enough?14:51
ogra_rsalveti, bah14:51
rsalvetiyeah, not sure, still investigating14:52
sil2100Thanks14:52
* sil2100 is sad14:52
jdstrandplars: put more simply-- aa-clickhook must always be run after click packages are installed (unless you are going to modify your code to do what newer autopkgtest is doing)14:52
jdstrandplars: aa-clickhook -f --include=... that is14:53
=== alan_g|tea is now known as alan_g
rsalvetiogra_: sil2100: worked fine after destroying and creating it again O_o14:56
rsalvetinot a single crash this time14:56
ogra_what did you do the first time, upgrade from an older one ?14:56
rsalvetino, clean image14:56
rsalvetisame one14:56
ogra_weird14:56
rsalvetibut I had a bunch of things crashing after the wizard crashed14:56
sil2100uh14:57
rsalvetiswipe is working, can open apps14:57
rsalvetiseems ok14:57
pmcgowanbzoltan had validated it prior to the image build fwiw14:57
rsalvetilet me try to recreate the broken image14:57
rsalvetiright14:58
rsalvetiI think bad things happen when the wizard crashes14:58
rsalvetiwill test it more14:58
davmor2sil2100: oh yeah what it is with the wizard always crashing?  I'm assuming it is safe to ignore and it's just because it got closed14:59
brendandsil2100, eventful start to the week, huh?15:05
sil2100brendand: yeah... hey! You're not on holidays? ;)15:08
brendandsil2100, i am15:08
brendandsil2100, on holidays until tomorrow15:09
sil2100davmor2: well, not sure about that, but with the TRAINCON-0 overextending so much, I don't feel like blocking on smaller things ;)15:09
brendandsil2100, what happened to the dashboard :/15:09
sil2100brendand: then don't look at our image situation! It will only stress you out ;)15:09
brendandsil2100, what did you DO!15:09
sil2100I don't knooow!15:10
sil2100It was popey !15:10
sil2100#blamepopey15:10
davmor2brendand: blame popey tm15:10
popey\o/15:11
brendandsil2100, but seriously - is something fundamental causing all those failures, or do all of those applications have different issues?15:17
ogra_something fundamental15:18
ogra_it mnifests as apparmor denial of autopilot introspection15:18
ogra_but there were no changes in either ... which makes tracking it super hard15:19
ogra_s/tracking/tracing/15:19
plarsogra_: sil2100: psivaa: brendand: ok, we have fewer failures on this rerun of gallery/notes, uitk tests in progress now15:27
ogra_cool ?15:28
* ogra_ wonders what to say about "fewer failures" ... means there are still some i guess15:28
sil21004 for notes and 1 for gallery, hmmm15:30
=== gatox is now known as gatox_lunch
psivaaplars: could be weird issues in the devices then?15:30
ogra_out of the blue ?15:31
psivaai still see ' 173.094185] type=1400 audit(1406646860.290:123): apparmor="DENIED" operation="mkdir"' message in notes app failed ones15:31
ogra_i wonder if we can somehow find out if kernel and initrd are up to date in the boot partition15:31
plarspsivaa: well, we're still getting that kind of stuff, yeah15:31
plarspsivaa: before that, we ran phablet-config autopilot --dbus-probe enable15:32
plarswhich in turn, runs 'aa-clickhook -f --include=/usr/share/autopilot-touch/apparmor/click.rules'15:32
plarsit also ran before the gallery_app test15:33
ogra_plars, can you check if all devices run "3.4.0-5-mako #32-Ubuntu" ? (uname -a should suffice)15:33
ogra_that should be the latest kernel15:34
plarsogra_: the one that ran this test is for sure15:34
ogra_ok15:34
plarsjdstrand: does http://paste.ubuntu.com/7895931/ provide anything useful to you?15:34
=== charles_ is now known as charles
ogra_jdstrand, oh, one thing i noticed, we dont have /lib/modules filled anymore ... shouldnt there be some firewalling ?15:37
jdstrandogra_: the ufw tests should fail if there is an issue15:37
jdstrandogra_: I'm guessing they are compiled in if they aren't failing?15:37
jdstrandplars: that looks all normal. what is happening is that /var/lib/apparmor/profiles/click_com.ubuntu.notes_notes_1.4.275 doesn't have the autopilot rules in it in 58315:39
* jdstrand is assuming15:40
ogra_jdstrand, hmm, i thought they were supposed to be modules15:40
ogra_rsalveti, do you know ? seems /lib/modules is empty15:40
plarsjdstrand: what about 585?15:40
rsalvetiit should be a link afaik15:40
plarsjdstrand: from that device, I don't see anything under /var/lib/apparmor/profiles/ - should I?15:41
rsalvetiogra_: /lib/modules/3.4.0-5-mako for mako at least15:42
ogra_with content ?15:42
plarsjdstrand: oh wait, sorry, wrong console15:42
plarsI do have stuff there15:42
plarsphew15:42
rsalvetiogra_: mako, yes15:42
ogra_ok15:42
ogra_(i only have aan old image around here)15:42
rsalvetiwell, should always be the case15:43
rsalvetiactually, this is not a link15:43
rsalvetiit's bind-mounted15:43
ogra_well, i expected that lsmod shows some modules loaded15:43
plarsjdstrand: http://paste.ubuntu.com/7895991/ is what I have in it after run 58515:43
ogra_yeah, i remember the code15:43
rsalvetiogra_: right, we might not necessarily be using any module15:44
rsalvetibut that's sort of expected15:44
ogra_well, i was expecting some UFW lockdown15:44
rsalvetiogra_: probably nobody requiring them15:46
rsalvetiwas able to load modules here just fine15:46
rsalvetimodprobe lttng-tracer15:46
rsalvetigot a bunch of modules after that15:46
ogra_ah, yeah, works here too15:46
pete-woodsfginther: hi, could you direct me to any documentation / explain how I to integrate click building a LP package with jenkins?15:52
fgintherpete-woods, one moment please15:53
jdstrandplars: yep, it has the correct line: #include "/usr/share/autopilot-touch/apparmor/click.rules"15:53
jdstrandplars: did that run pass or fail?15:53
plarsjdstrand: it didn't fail completely, but it had some aa related failures on notes app15:54
plarsjdstrand: http://q-jenkins.ubuntu-ci:8080/job/utopic-touch-mako-smoke-daily/585/consoleFull15:54
plarsogra_, sil2100, psivaa: ok, we have passing uitk tests15:56
sil2100\o/15:56
ogra_yay15:56
ogra_at the third attempt though15:56
* ogra_ hopes that persists :)15:56
plarshttp://ci.ubuntu.com/smokeng/utopic/touch/mako/157:20140729.2:20140728.1/9355/ looks much improved now, and I've disabled a couple of devices to see if they are causing problems15:56
bzoltan1sil2100: rsalveti: We need to update the QtCreator package (not the plugins I am releasing often, but the big one) from the packaging trunk -> https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtcreator  Mirv is not around, so I will need a hand to push it.15:57
sil2100plars, jdstrand: ok, since I got a bit out-of-date on the state, but do we have any clues on what's going on the dashboard side with the apparmor denials during ap tests?15:57
plarsand jdstrand and I still need to work through what's going on with this aa-clickhook stuff15:57
plarssil2100: not yet, we're working on that now15:57
bzoltan1sil2100: rsalveti: I do not remember if the QtC package is on the CI Train or not15:57
* ogra_ thinks this is just fallout of something else we havent identified yet 15:58
sil2100bzoltan1: you want to do it through the train, yes?15:58
sil2100bzoltan1: let's check the version then ;)15:58
bzoltan1sil2100: sure, that is the real thing, right?15:58
bzoltan1sil2100:  the trunk is up to date and we have bumped the version too15:59
plarsone thing interesting... I can reproduce the messages like Jul 29 15:44:28 ubuntu-phablet kernel: [  289.352388] type=1400 audit(1406648668.834:84): apparmor="DENIED" operation="mkdir" profile="com.ubuntu.notes_notes_1.4.275" name="/home/phablet/.local/share/notes-app/" pid=5394 comm="qmlscene" requested_mask="c" denied_mask="c" fsuid=32011 ouid=3201115:59
plarsat home15:59
plarsbut I don't see the tests fail when it happens15:59
sil2100bzoltan1: ok, so it seems Timo didn't use the train for it it seems, I'm double checking one thing though15:59
sil2100I think he was releasing directly to the archive16:00
jdstrandplars: that is a different issue16:01
bzoltan1sil2100:  not impossible16:02
jdstrandplars: in that case, it seems like the applicationName in the notes-app qml is wrong. /home/phablet/.local/share/notes-app/ is wrong. it should be /home/phablet/.local/share/com.ubuntu.notes16:02
=== john-mca` is now known as john-mcaleely
rsalvetibzoltan1: is mirv on vacation again?16:02
bzoltan1sil2100: I do not think that our CI train can merge to that project16:02
jdstrandplars: if it isn't the QML, it is something else in the app16:02
bzoltan1rsalveti:  yes16:02
sil2100rsalveti: yes, one more week16:03
rsalvetilol, wonder how many weeks he got16:03
rsalvetimaybe he's special because he's finnish16:03
rsalvetisummer and so on16:03
rsalvetibzoltan1: please create the mr and ping with with the address16:04
rsalvetiI can take a look16:04
psivaaplars: wow, it's a great news. hope this stays as it is :)16:04
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): Ursinha | CI Train support: sil2100, trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. TRAINCON-0. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
bzoltan1rsalveti:  Is it possible to land a totally empty MR? I mean even without touching the changelog.16:05
plarspsivaa: there's still more to sort out, but we have better results.. still not what they should be though16:05
rsalvetisil2100: ogra_: so, I tried the emulator a bunch more times, and it's getting in a broken state from time to time16:05
bzoltan1rsalveti: in Finland everybody has about 25 days holiday, but Finns  like to to take them in big blocks :)16:05
rsalvetistill to be investigated, but it's better than the last promoted one16:06
ogra_rsalveti, promotable with a note in the landing mail  ?16:06
rsalvetiso I'd say this shouldn't be blocking trainco anymore16:06
ogra_ah, you were faster16:06
ogra_yeah16:06
pmcgowan+116:06
ogra_we now just need the smoke tests to work16:06
jdstrandplars: in other words-- that is a bona-fide bug with notes-app16:07
jdstrandpsivaa: I would be curious what the results would be if you did a test run now in the same manner you did before16:08
jdstrandplars: oh, you said you disabled a device-- is it possible that the device had problems with either the filesystem or the hardware such that it couldn't write out files? think is that maybe the files didn't get updated even though aa-clickhook --include was run16:09
plarsjdstrand: that wasn't on this device16:10
jdstrands/think is/thinking/16:10
psivaajdstrand: i guess plars ran the same way as i did, except on the devices that failed me :)16:10
plarsjdstrand: if that's the case, then the problem is on a lot of devices16:10
jdstrandplars: I know. this one passed. the other didn't. didn't you disable the device that didn't pass?16:10
popeyballoons: any problem uploading the clicks?16:10
plarsjdstrand: this one didn't pass completely though16:10
plarsjdstrand: we still got 5 notes failures which we didn't expect to see16:10
plarsjdstrand: and a whole lot of these apparmor denied messages16:11
plarsjdstrand: I also see that at home16:11
jdstrandplars: right, but the reason I am involved is cause of the autopilot apparmor rules. that wasn't an issue on this run (at least not for notes-app)16:11
plarsjdstrand: except it passes16:11
jdstrandplars: you are talking about the mkdir denial?16:11
plarsjdstrand: on 585?16:11
plarsjdstrand: yes16:11
jdstrandplars: right, I addressed that. the mkdir denial is a bug in notes-app16:11
fgintherpete-woods, sorry about that, was in the middle of something else. Generally, we just create the jenkins jobs as needed per project (we don't have a lot of these yet). What package is this for?16:12
plarsok16:12
plarsjdstrand: didn't understand that, thanks16:12
jdstrandplars: it was only the autopilot apparmor dbus denials had to do with aa-clickhook16:12
ogra_=== IMAGE 157 Promoted !!! ===16:14
plars\o/16:14
pmcgowannice!16:14
cjwatsonbzoltan1: empty MR> yes, although you have to use "force rebuild" in the build job parameters16:14
pmcgowanolli, jdstrand^^16:15
jdstrandnice!16:15
pmcgowanthanks plars, psivaa16:15
jdstrandplars: so, I was just asking if there was a hardware issue with the device that ran 583.16:15
cjwatsonoh, brilliant16:15
=== gatox_lunch is now known as gatox
tvosshah, we are moving again?16:17
jdstrandplars: if you think that was a possible cause. if you rule that out-- there is something that is undoing the aa-clickhook changes. would probably need some instrumenting in the test infrastructure to figure it out16:17
plarsjdstrand: I don't see anywhere that it could be undoing the aa-clickhook changes, but I think you were suggesting earlier that they looked like they were reverted?16:17
kgunnsil2100: is there a way to check on ubuntu-system-settings in silo6....i think i saw some other silos y'day....but now gone? (landed?)16:18
kgunnjust need to check to see if we need to rebuild?16:18
jdstrandplars: if you are going to instrument it, I would suggest grepping for the '#include' line I mentioned earlier after aa-clickhook, and then grepping for it again right before the autopilot tests are run16:18
sil2100kgunn: after the meeting I'll try to check that :)16:18
=== psivaa is now known as psivaa-bbl
kgunnsil2100: ta, it was the only other thing that i was worried/keeping an eye on16:18
kgunntvoss: its happening...train chugging away from station16:19
pmcgowankgunn, you ever landing that silo?16:19
pmcgowan;)16:19
jdstrandplars: actually, could jest do 'grep "# injected via click hook" <path to profile>' || failtest16:19
kgunnpmcgowan: don't jinx it16:19
jdstrandjust*16:19
jdstrandplars: ie, if we check that the autopilot rules are correctly added, we can fail the whole thing if they are not16:20
tvosskgunn, gotta say that in German: so schön, dass Emma wieder fit ist :)16:20
tvossogra_, ^16:20
ogra_:D16:20
jdstrandplars: but the check needs to be done right before the tests are run, and ideally, additionally after aa-clickhook --include is run16:21
plarsjdstrand: I'll try to take a look at that on some manual ones at least - did you have a link for somewhere you saw the aa stuff getting reverted though?16:22
jdstrandplars: for i in /var/lib/apparmor/profiles/click_* ; do grep -q "# injected via click hook" $i || failtest '$i' does not have autopilot rules ; done16:22
jdstrandplars: nope. I couldn't find it in the diff16:22
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): Ursinha | CI Train support: trainguards | CI Train Status: #133 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): Ursinha | CI Train support: trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
jdstrandplars: something akin to that ^ may at least save time for next time16:23
sil2100kgunn: give me a minute and I'll check that for you16:23
* sil2100 has firefox problems16:23
jdstrandand may provide clues for next time16:23
ollisil2100, cjwatson, pmcgowan, ogra_, jdstrand, rsalveti, plars, psivaa-bbl, everyone that I forgot... THX!16:28
sil2100kgunn: ok, just checked and it seems that no new ubuntu-system-settings was released, so the version in silo 006 seems good!16:35
kgunnsil2100: woohoo!16:37
kgunnsil2100: its all good to go then16:37
robrusil2100, hey hey hey what's the word?16:38
sil2100robru: hey! So!16:39
sil2100robru: we promoted o/16:39
sil2100robru: not a perfect image, but promoted16:39
robrusil2100, great!16:39
sil2100robru: anyway, could you publish 006 once you have some time?16:39
ToyKeeperDid kgunn's silo land too?16:39
kgunnToyKeeper: not yet, but its 1st in line16:39
robrusil2100, of course!16:39
robrulike, right now16:40
sil2100robru: if you can, kick a new image once 006 is in the archive, since this will be a good image for a second promotion ;)16:40
robruoh, 6 is building16:40
kgunn@ good image for a second promotion, yes it will my friends....yes it will16:40
kgunnrobru: ah! what?16:40
kgunnlemme check16:40
sil2100robru: since silo 006 seems like the golden bullet here, fixing at least two of our issues ;)16:41
kgunnarrg...yeah, an update sanity build robru16:41
kgunnonce its done, its good to go16:41
kgunnrobru: just making all the gles twins happy16:41
kgunnnow its ready16:44
kgunnrobru don't quit now16:45
kgunnToyKeeper: davmor2 ^ anyone want to show some qtcomp love ?16:46
sil2100;)16:46
sil2100robru's in a hotel right now16:47
sil2100Anyway, kgunn are you triple sure that I can press 'publish' on 006?16:47
sil2100If yes, I can press it!16:47
sil2100Oh, and there's robru back16:48
robruweird, stupid hotel wifi is crap16:48
robrusil2100, kgunn: i guess i missed some messages from you guys16:48
robrujust wondering about gles in silo 616:48
* olli holds his breath16:50
ToyKeeperkgunn: If so, it'll be a bit...  I need to relocate before I can start anything.16:51
sil2100kgunn: ^ :) ?16:52
davmor2kgunn: I spent spent Monday testing it.  It was fine unless it has been massively updated since then?16:54
davmor2I can give it a blitz testing now though16:55
bzoltan1cjwatson: rsalveti: I have added this to the line 40 -> https://code.launchpad.net/~bzoltan/kubuntu-packaging/enable_ubuntu_devices/+merge/228725 The best would be to get a silo for it and I will add the rest of the plugins one by one.17:02
robrusil2100, kgunn: so nobody answered my question about gles in silo 6. is it tested?17:04
sil2100kgunn: ^ ?17:04
robrukgunn, sil2100: oh sorry, i just noticed it's a no-change rebuild, nevermind.17:05
robrukgunn, sil2100: ok, publishing silo 6 then!17:05
Saviqmterry, https://ci-train.ubuntu.com/job/landing-006-2-publish/36/17:08
Saviqrobru, mterry will have a look at ↑17:08
=== alan_g is now known as alan_g|EOD
robruSaviq, you can summon him just like that, can you?17:08
kgunnrobru: sil2100 thanks (sorry, snuck to the kitchen for a moment)17:09
Saviqrobru, he's sitting opposite, so yes17:09
* tvoss thinks we should have fancy videos of packages landing in the archive17:10
robrumterry, well, it's a big one, good luck!17:10
robrusil2100, how was your first day with the new spreadsheet? really nice, huh? ;-)17:15
sil2100robru: not bad! Although I didn't have too many occasions to use it!17:15
sil2100Traincon you know17:15
robrusil2100, hehe, time will come ;-)17:15
kgunnmterry: btw, langasek had already package reviewed qtmir17:16
ollisil2100, is there a way for me to see the current queue of silos, ideally in the order you guys will process them?17:16
kgunnin case that matters17:16
mterrykgunn, right17:16
robruolli, not really. just the pending tab of the spreadsheet, but they're not really assigned in the order requested, more like "assigned in the order that people ping about them on IRC"17:17
=== Ursinha-afk is now known as Ursinha
mterryrobru, I've already looked at most of this changes during MP time actually.  I've just gone through them and I don't see anything awful.  ACK17:17
robrumterry, thanks buddy!17:17
ollirobru, thx17:17
robruolli, you're welcome! Is there one you want assigned soon?17:18
ollirobru, next pick would simply be a line that's entirely green?17:19
robruolli, err, nope. more like, green-green-red.17:20
robru(right third one is testing pass state, taht can only get green after the silo is assigned)17:20
olligotcha17:20
olliso there is a good lineup... let me check if I have an opinion17:21
robruolli, https://docs.google.com/a/canonical.com/spreadsheet/lv?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&type=view&gid=0&f=true&colid0=2&filterstr0&colid1=35&filterstr1=Yes&sortcolid=-1&sortasc=true&rowsperpage=250 try this on for size. this is a special "filtered list" view on the spreadsheet, it hides rows that are already assigned, and hides rows that are set as ready:no, which means those are the potential candidates for assignment.17:22
robruunfortunately I can't actually process the assignments from that view, otherwise it might actually be useful ;-) but if you just wanna look, it's an interesting way to slice the data.17:23
sil2100Man, my head hurts17:24
ollirobru, there is a whole bunch17:25
olliif I was talking with my Unity/Mir head on I'd give preference to things related there17:26
ollihead/hat17:26
robruolli, yep. many of them are months old as well. since there is only 1 silo available, I have to be very careful who I give it to!17:26
olliputting my Rick hat on, I'd say go for bugfixes17:26
robruolli, oh, we just promoted an image, doesn't that mean it's time for Feature Bonanza?17:27
robru;-)17:27
sil2100o/17:27
robrusil2100, goodnight!17:27
cwayne_hihi, now that we're out of traincon0, can we get silo 008 landed without qa validation? or is it still needed?17:27
ollirobru, when are you planning to promote again17:27
=== Ursinha is now known as Ursinha-afk
olliheh17:27
robrucwayne_, yeah probably17:27
robruolli, well i think the plan is to land silo 6, build an image, consider that one for promotion as well, and then after that, open it up for any & all landings.17:28
=== Ursinha-afk is now known as Ursinha
ollirobru, I don't think I have more to add17:28
robruolli, no worries. is rick off or something? I didn't understand why you're wearing his hat ;-)17:29
ollirobru, once open for any & all landings... when are you cutting an image again?17:29
ollirobru, yeah, get to be rick this week, wasn't sure if you asked me for input in that role17:29
ollihence the hats ;)17:30
robruolli, well cron kicks an image daily, but sometimes we manually kick 1 or 2 extra depending on how many landings there are. so today I think I'm just kicking the one.17:30
olliok, wfm17:30
rsalvetitvoss: you don't usually set the silo as 'passed' before the MRs are approved17:30
rsalvetipass here means ready to land17:30
rsalvetiwhich is not the case as the mrs are not yet approved17:30
robruolli, thanks17:31
rsalvetigezzz, seems we're landing qtcompositor?17:31
bzoltanrsalveti: is that MR and the landing line 40 good?17:32
robrursalveti, qtcompositor is happening! it was ready since yesterday. any problems, blame kgunn! ;-)17:32
rsalvetibzoltan: I didn't get why the blank mr, do you just want to land the latest in the packaging branch?17:32
bzoltanrsalveti:  yes17:32
rsalvetilol, you guys are fast17:33
rsalvetijust out of trainco 017:33
rsalvetinice17:33
robrursalveti, well this qtcompositor stuff is supposed to fix one of the blocker bugs, so we're doing it.17:33
rsalvetibzoltan: should be enough, will take a look later today17:33
bzoltanrsalveti:  thanks17:33
rsalvetirobru: new features, hopefully without new bugs :-)17:33
robrursalveti, bugs? never!17:36
robruinfinity, cjwatson: anybody around to NEW qtmir and qtmir-gles? I need to get those in so I can build & image before I can release a bunch of other silos.17:36
cjwatsonslangasek: ^- I gather you'd pre-reviewed those, so can you do the honours?17:41
robrucjwatson, slangasek: thanks guys17:43
slangasekyep17:43
slangasekoh, which honors am I doing?17:44
cjwatsonah, Steve had beaten me to it anyway17:44
slangasekit's not in NEW17:44
slangasekno, somebody else17:44
cjwatsonsomebody else did; it did hit NEW for ~20 minutes17:44
* slangasek nods17:45
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
rsalvetirobru: mind reconfiguring silo 1?18:06
slangasek161! we go through a lot of numbers18:07
robrursalveti, done: https://ci-train.ubuntu.com/job/prepare-silo/1185/console18:07
=== rsalveti changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mthanksDv1FS know your silo status before the spreadsheet does.
robruslangasek, what?18:07
rsalveticrap18:07
=== rsalveti changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
rsalvetithanks :-)18:08
slangasekrobru: oh, just idle comments on the mailing list discussion :)18:08
slangasekrobru: I'm not sure how Saviq went from 157 to 161, but sil2100 clarified that 158 is next :)18:08
rsalvetix86 is 3 ids ahead18:09
robruslangasek, apparently the i386 and arm image numbers are out of sync18:09
robrursalveti, lol, took me a while to notice what you did with the topic there18:09
rsalvetiyeah, mouse was in the wrong place :-)18:09
robrursalveti, what IRC client you using? mine doesn't let me live-edit topics like that. have to copy & paste into the message area, kind of a hassle18:10
rsalvetiold xchat18:10
rsalvetifor some reason I have enough permission to change the topic18:10
robrursalveti, anybody can change the topic in this channel, it's unrestricted18:11
rsalvetioh, that's why then18:11
rsalveti:-)18:11
rsalvetifixed, rebuilding18:14
* slangasek eagerly updates to 15718:14
Saviqslangasek, oops ;)18:16
Saviqslangasek, emulator images apparently ;)18:16
Saviqdidn't know they have different numbers to the phones18:17
mhr3robru, anything blocking 008?18:17
robrumhr3, yep, waiting for 6 to finish landing, then I'm going to kick an image. give it a couple hours18:17
mhr3alright18:17
robrubarry, system-image progressbar problem went away by itself, not sure what ever caused it!18:18
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cprov | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
popeyrobru: any plans to trigger a new image soon?18:37
robrupopey, yep, as soon as silo 6 finishes landing, which should be soonish18:37
popeycan you hang fire, I'm approving core apps clicks right now18:37
robrupopey, oh ok, sure, just let me know18:39
popeyta18:39
robrupopey, how long do you think you need? (just curious, no rush)18:40
popey~30 m18:40
robrupopey, perfect, I'll take lunch ;-)18:40
robrubrb18:40
=== Ursinha-afk is now known as Ursinha
popeyrobru: all done, all new clicks in the next image18:52
=== psivaa-bbl is now known as psivaa
Saviqnow migrate already!19:01
Saviqshould we worry about http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-system-settings or will this get sorted out by itself?19:01
tvosscjwatson, still around?19:02
Saviqah fook oh noes19:04
Saviqrobru, kgunn, we've a problem...19:04
Saviqubuntu-system-settings is all arch (arm64, ppc etc. as well), but qtmir is only armhf/i386/amd6419:05
kgunnSaviq: ug...19:06
* olli is watching live while in a HO with kgunn19:06
Saviqso u-s-s from the silo is blocked in proposed because qtmir is not available in all the arches u-s-s is available in19:06
kgunnSaviq: so we gotta build qtmir for all archs ?19:06
robrupopey, thanks19:06
Saviqkgunn, that's probably not possible19:06
Saviqbecause we don't have mir for all those arches19:07
robruSaviq, ugh, how did this happen?19:07
Saviq;( help19:07
Saviqrobru, usual, there's no hardware using arm64/powerpc/ppc64el phone19:07
robruSaviq, you need to add a build-dep on qtmir so that it knows not to build on those arches19:08
Saviqrobru, and u-s-s didn't have a dependency like that before19:08
Saviqrobru, it doesn't19:08
Saviqrobru, but u-s-s was on those arches before19:08
robruSaviq, ok then we need somebody like infinity or cjwatson to manually override that. it's out of my hands19:08
Saviqrobru, yeah I thought so :|19:09
kgunnslangasek could you possibly help ^ ?19:09
SaviqTBH not even sure how it could be available before when it used unity-mir... that's only armhf/i386/amd64... probably no explicit dep19:11
Saviqyeah, it only got away with it because no one tried it on the other arches19:11
kgunnrobru: whom might we plea to for some help ?19:31
robrukgunn, I'd go with cjwatson, infinity, stgraber, or slangasek but nobody seems to be responding to pings at the moment.19:32
kgunnrobru: ok, will sit tight...19:33
robrukgunn, yeah it's all we can do19:33
robrukgunn, care to speculate on what potential consequences might arise from an image build that has all of silo 6 except system settings?19:33
slangasekSaviq, kgunn, robru: you don't get manual overrides for such things; you update the uninstallable package to not be built on the arch where it's uninstallable and we remove the binaries from the archive19:34
kgunnrobru: yeah, i don't think it'll boot actually....infinite spinning logo would be the result i think19:34
robrukgunn, cool19:35
slangasekso someone please upload ubuntu-system-settings to limit its Arch list or make it FTBFS on !i386 !x86_64 !armhf19:35
robruslangasek, so what, like add a build-dep on mir?19:36
slangasekrobru: probably just change the Architecture: any to Architecture: i386 amd64 armhf on the binary packages19:37
robruslangasek, isn't hard-coding arches technical debt? I've been told not to do that19:37
slangasekbut if you prefer to build-dep on mir instead, that's ok19:37
slangasekrobru: yeah, for this reason a build-dep on an arch-specific mir package is fine19:37
robruslangasek, ok, will do19:37
robruslangasek, will need you to delete those binaries in a minute19:38
slangasekack19:38
robrukgunn, slangasek, https://code.launchpad.net/~robru/ubuntu-system-settings/build-dep-mir/+merge/228755 k, will build this in the silo if it looks good to you.19:41
kgunnrobru: thanks looking19:41
robruwhoops, looks like I proposed to the wrong place19:41
robrukgunn, slangasek: sorry try https://code.launchpad.net/~robru/ubuntu-system-settings/build-dep-mir/+merge/22875619:43
kgunnrobru: got it, so that'll make it just ftbfs19:44
kgunnfor those archs19:44
robrukgunn, yep, it won't be able to build without that on arches that don't have it19:44
kgunnrobru: crap...need an approver19:45
kgunnbfiller: do you have capability? to top approve19:45
kgunnhttps://code.launchpad.net/~robru/ubuntu-system-settings/build-dep-mir/+merge/22875619:45
bfillerkgunn: looks like I don't on that MR19:46
bfillerkgunn: kenvandine might ^^^^^19:46
kgunnrsalveti: ^19:46
kgunnjust an mp to cast off the need for ppc/arm6419:47
kgunnin the case of qtmir19:47
kgunncharles: you might be able to help....just need a top approver19:48
kgunnhttps://code.launchpad.net/~robru/ubuntu-system-settings/build-dep-mir/+merge/22875619:48
* kenvandine looks19:51
* kgunn hugs kenvandine19:51
kenvandinekgunn, done19:53
kgunnkenvandine: thanks, bullet dodged19:53
charleskgunn, kenvandine, thanks19:57
robrugosh that status is misleading ;-)19:59
robruslangasek, I guess this is what success looks like? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-006/+build/6222567 can you delete those binaries now?20:00
slangasekrobru: absolutely :)20:04
robruslangasek, thanks!20:04
alecuso, is the train already moving? Who do we bribe around here for silos?20:11
alecu:-)20:11
kgunnthanks slangasek20:13
kgunntakin' a break bbiab20:13
cjwatsonslangasek: um, ubuntu-system-settings has rdepends on those arches; I'm not sure you're improving things by just pushing the uninstallability up a level20:28
cjwatsonslangasek: and in particular it leaks into the whole online-accounts stack which is a real pain to arch-limit (BTDT)20:28
slangasekah20:29
slangasekcjwatson: so from the discussion above, the packages are de facto not usable on those architectures because of a (logical but previously undeclared) dependency on mir20:29
cjwatsonthey've been usable enough to satisfy build-deps20:30
cjwatsonI understand the wider point, but I've analysed this stack before and it's a nightmare to disentangle20:30
cjwatsonso I think we need to figure something out even if it's not in u-s-s itself20:31
cjwatsonthe deps are: indicator-bluetooth; ubuntu-system-settings-online-accounts <- (account-plugin-{lots}, friends-app, reminders-app, etc.)20:32
cjwatsonthe main difficulty is where it globs into account-plugin-* and requires making a bunch of things explicitly Architecture: amd64 armhf i386 to avoid building uninstallable things20:32
robrualecu, no silos to be had just yet20:35
robrucjwatson, uh, I *just* hit publish on u-s-s with a new qtmir build-dep20:35
cjwatsonubuntu-system-settings-online-accounts seems pretty tied to ubuntu-system-settings, and the account-plugin-* packages seem pretty tied to it20:36
cjwatsonrobru: sorry to come into this late, it was dinnertime20:36
cjwatson(and I'm about to be called away again)20:36
robrucjwatson, thanks for looking at it... soo... do I need to rebuild it again or is this gonna work*?20:36
robru* for values of 'work' that include 'unblock it from proposed'20:37
cjwatsonrobru: depends whether slangasek has already removed binaries; if he has then he's created uninstallables, and I would not do that20:37
slangasekI haven't yet20:37
alecurobru: not even with some hefty bribe? ;-)20:38
slangasekcjwatson: how do you want to handle?20:38
alecurobru: no problem, I'll ask again in some hours.20:38
cjwatsonI get that it's not usable, but it apparently worked well enough to not have to tear UOA apart.  can we make the dependency conditional?20:38
robrualecu, you can't bribe me to give you something that doesn't exist ;-)20:38
robrualecu, but something should free up soon hopefully...20:38
alecugreat20:38
robrucjwatson, I have no clue about this component. I'm just doing what people tell me to do with it20:39
cjwatson(maybe it mostly just needed the library to work, and then to be able to depend on ubuntu-system-settings although nothing ends up being used in the build chain)20:39
cjwatsonrobru: I'm mostly talking to slangasek20:39
robrucjwatson, ok20:39
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
* robru secretly hopes that the thing he just publishes unblocks u-s-s from proposed so he can kick an image and then land the 4 other silos that have been waiting all day20:41
cjwatsonI doubt it20:42
slangasekcjwatson: so I'm coming around to the conclusion that forcing u-s-s in might be a lesser evil20:44
slangasekto unblock, and then we can unpick the dependencies without Landing Team pressure20:45
cjwatsonmy inclination would be http://paste.ubuntu.com/7898248/ on top of use-qtComp20:45
cjwatsonthat's possible, but please check how many uninstallables it yields first20:45
slangasekthat's for u-s-s?20:45
cjwatsonyeah20:45
cjwatsondropping the build-dep-mir branch20:45
* slangasek nods20:46
cjwatsonall the options here are suboptimal in one way or another; that one more or less restores the status quo on the secondary arches20:46
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): fginther | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
robrucjwatson, so should I apply that diff and rebuild and reupload or can you just upload that for me since you have the diff there already20:48
robru?20:48
cjwatsonrobru: I have a five-year-old more or less begging for my attention20:48
cjwatsonso I kind of don't want to supervise right now20:49
robrucjwatson, ok I'll do it then, sign off!20:49
cjwatsonok :)20:49
robruslangasek, so if I apply that ^ is it gonna unblock without needing you to delete packages?20:52
slangasekrobru: yes20:53
robruslangasek, ok, it's building now20:53
cjwatsonrobru: oh, just to make it clear, that doesn't conflict with your build-dep-mir branch directly, but you will need to drop that change in order for this to be useful20:53
slangasekrobru: ok, perfect :)20:53
slangasekright, what cjwatson said20:53
robrucjwatson, yep, done20:53
cjwatsonright, LGTM20:54
popeyfginther: http://paste.ubuntu.com/7898371/21:05
popeypayui fails the click-reviewer-tools21:05
popeyjdstrand: ^21:05
popey      "text": "id 'payui_payui' != 'com.canonical.payui_payui'"21:05
jdstrandpopey: yeah, so, I think we need tedg21:08
popeypaging Mr Gould, paging Mr Gould. Mr Gould to the white courtesy phone...21:09
jdstrandtedg: looking at other online accounts application ids, my understanding is it should be <click pkgname>_<appname>21:09
alecujdstrand, popey: tedg is on vacations this week21:09
popeyerk21:09
alecujdstrand: popey: can I help instead?21:09
jdstrandah, well, whoever uploaded this then21:09
popeyfginther: did21:10
alecugatox asked for this to be uploaded, but seems to be gone now.21:10
jdstrandpopey: the "unconfined" template for this is 'ok' (previously discussed)21:10
popeysure21:10
popeythis was new though, hence me rejecting it21:10
jdstrandyes21:10
jdstrandI think you are right21:11
jdstrandI think that is a legitimate error in the app21:11
jdstrandaiui21:11
jdstrandwe might want mardy's input too though21:11
alecujdstrand: popey: pay-ui just started using libonlineaccounts-client. Is that error due to this?21:11
jdstrandalecu: it is related to its use of online accounts, yes. it isn't declaring its application id correctly21:12
jdstrand= click-check-online-accounts =21:12
jdstrand{21:12
jdstrand  "error": {21:12
jdstrand    "online_accounts_payui_account-application_id": {21:12
jdstrand      "text": "id 'payui_payui' != 'com.canonical.payui_payui'"21:12
jdstrand    }21:12
jdstrand  },21:12
jdstrandalecu: ^21:13
jdstrandalecu: I think it is just a simple string change in the xml21:13
alecuok, I'll propose a branch for that21:13
jdstrand== online account-application: com.canonical.payui.application ==21:13
jdstrand<?xml version="1.0" encoding="UTF-8" ?>21:13
jdstrand<application id="payui_payui">21:13
jdstrandalecu: ^21:13
jdstrandchange that to 'id="com.canonical.payui_payui"' and it should be fine to upload. granted, I don't know if something else needs to change internally21:14
alecujdstrand: I'll test that change on my phone, and will ask for it to be reuploaded21:15
jdstrandalecu: awesome, thanks! :)21:16
alecuyes!21:36
Saviqrobru, thank you for getting silo 6 sorted out21:39
* Saviq wasn't sure what was the right solution21:39
robruSaviq, me either but I got told ;-)21:39
Saviqrobru, yeah, lesson learned!21:40
robruSaviq, you're welcome! I'm super stoke to get that published and an image kicked21:40
Saviqrobru, ↑21:46
robruyep ;-)21:46
gatoxjdstrand ping21:51
jdstrandgatox: hey21:54
jdstrandgatox: so, I am heading out. all my comments on the payui application id are in scrollback and alecu is handling it21:59
gatoxjdstrand, i'm trying to propose a branch for payui fixing the problems in the xml...but when trying to do it as it is suggested... the ubuntu sdk fails to build it if i declare the project as com.canonical.payui.... and if i just put the whole names without using cmake var to build the tihngs it fails to launch online accounts21:59
jdstrandgatox: I do read backscroll though, so feel free to ping me21:59
jdstrandah21:59
jdstrandgatox: I think we need bzoltan and mardy to comment22:00
jdstrandgatox: I wrote the tests based on what I observed other apps did (eg, reminders). I don't know what the sdk is doing, though istr mardy and the security talking about how these would be namespaced22:01
jdstrandgatox: unfortunately, they are both eod right now22:01
jdstrands/security/security team/22:01
gatoxjdstrand, so.... is not going to be posible to land this?22:01
gatoxtoday22:01
jdstrandI think it is in error. I just don't know how to tell you to fix it :\22:02
gatoxjdstrand, because the way it is right now.... was working in the phone..... trying to make the changes as it was suggested brakes the build with the sdk..... or breaks the launching of online accounts22:03
Saviqrobru, it looks like there's some action from archive admins needed now (removing the old binaries?) http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-system-settings22:10
robruSaviq, no, that page is stale (note it says v...29 and not v...29.1)22:10
Saviqrobru, ah, not ran yet, than, tx22:11
jdstrandgatox: it may work but it is breaking namespacing rules22:18
gatoxjdstrand, i think i found the solution22:18
jdstrandok, cool22:19
gatoxjdstrand, yes.... just tested it.... proposing the branch22:20
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: robru, trainguards | CI Train Status: #157 promoted | Known issues: Read http://bit.ly/1k4uBJR before asking about the spreadsheet changes. Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
jdstrandgatox: nice!22:23
Chipacacould I have silo 9 landed please?22:25
gatoxfginther, hi.... sorry to bother you again... if you are still around, i just sent you an email with a new click version22:25
fginthergatox, got it22:26
gatoxfginther, thanks..... and sorry for the trouble22:26
fginthergatox, uploaded (and no worries)22:26
gatoxfginther, thanks!22:27
popeygatox: fginther ERROR: Could not load 'payui.json'. Is it properly formatted?22:32
gatoxpopey, :s checking22:33
popeyhttp://paste.ubuntu.com/7898990/22:33
popeymissing a line-feed?22:33
gatoxpopey, how can i run those checks locally?22:33
popeylp:click-reviewers-tools22:34
popeybin/click-run-checks foo.click22:35
popeyhttp://paste.ubuntu.com/7899020/ is an example good one gatox22:36
popeyhttp://paste.ubuntu.com/7899029/ is the one from the terminal app22:37
popey(also unconfined)22:37
popeygatox: also failed in other ways, ERROR: Could not find 'payui.desktop'22:37
gatoxpopey, yes.... i found that issue22:37
popeyi need to EOD now...22:38
popeywill check for new payui in the store in the morning22:39
gatoxpopey, i'm about to send the click22:40
gatoxpopey, after running the tools22:40
popeyok22:41
popeywill hang around 10 mins22:41
fginthergatox, I'm here as well22:44
gatoxfginther, popey thx both.... i just sent the new click to francis.... as far as i can see the only error is about unconfined that it says it needs manual check22:44
popeythats fine22:45
popeywe have already discussed and accepted that22:45
fginthergatox, popey it is uploaded22:45
popeygot it22:45
popeyapproved it gatox fginther, thanks22:46
popeyshould be in the next image22:46
gatoxpopey, fginther great! thanks!22:46
rsalvetiawesome23:00
cjwatsonubuntu-system-settings from silo 6 is in utopic according to rmadison - kicking an image build23:32
cjwatson(someone tell robru if he shows up again)23:32
SaviqLaney, FWIW, the wizard wouldn't work on other arches before anyway (since it needed libunity-mir1, which was only available for the usual arches as well)23:37
SaviqLaney, only difference is now it doesn't get built instead of just failing when you tried it23:37
imgbot=== trainguard: IMAGE 158 building (started: 20140729 23:40) ===23:39
cjwatsonSaviq: we had to start building it again23:41
cjwatsonSaviq: the fallout is too complicated on secondary arches23:41

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