=== salem_ is now known as _salem
=== _salem is now known as salem_
=== fginther` is now known as fginther
=== salem_ is now known as _salem
sil2100seb128: hey! Would need a quick formal binNEW ACK for the usual mir ABI bump binary package renames: https://ci-train.ubuntu.com/job/ubuntu-landing-051-2-publish/12/console :)09:02
sil2100(if you have a moment)09:02
seb128sil2100, hey! looking in a minute09:02
seb128sil2100, looks fine, +1 from me09:22
sil2100\o/ Thanks again :)09:22
Mirvalan_g: sil2100 already published it an hour ago10:18
alan_gMirv: cool. Thanks10:18
=== joc|away is now known as joc_
=== _salem is now known as salem_
rvrjgdx: ping13:28
Saviqsil2100, hey, not sure if you're the one to ask, but any idea why ubuntu-touch/rc-proposed/ubuntu is hidden: true? https://system-image.ubuntu.com/channels.json13:28
Mirvsomeone was indeed asking why of all the channels the recommended channel isn't showing when listing the channels..13:29
SaviqMirv, indeed13:29
jgdxrvr, pong13:29
rvrjgdx: Hi13:29
rvrjgdx: I'm testing silo 12 and found an issue with system settings and indicators.13:29
rvrjgdx: Tapping on the settings options on various indicators eventually makes the panel not to hide automatically.13:30
jgdxrvr, it's known and not introduced by this silo13:30
jgdxrvr, let me fetch you the bug13:31
rvrjgdx: Oh, really? I tried without the silo and couldn't reproduce13:31
abeatotrainguards, is it normal getting "Automated Signoff" == Running for a long time? See https://requests.ci-train.ubuntu.com/#/ticket/102713:33
jgdxrvr, https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502223 :)13:34
ubot5Launchpad bug 1502223 in unity8 (Ubuntu) "Delay in opening system-settings from indicators" [High,Triaged]13:34
jgdxrvr, who's this victor guy :p13:35
jgdxrvr, seems it has something to do with unity8, since Ken found the url-dispatcher to launch USS immediately, always.13:36
rvrjgdx: lol13:37
rvrjgdx: Hmm13:37
jgdxrvr, fix seems to be targetted for 08, i.e. ota1013:38
rvrjgdx: Right, it is a long delay13:38
Mirvabeato: you can check the excuses page to see what exactly is running13:48
abeatoMirv, https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-046/excuses.html13:48
Mirvabeato: yes, so armhf ntp13:48
abeatotest in progress for armhf13:48
Mirvabeato: following that link brings you to a page that at least no longer mentions ntp, so if it's still not updated 1h from now, it might be time to ping pitti about a stale autopkgtest. but it might be also that it's just waiting to be refresh the page.13:49
abeatoMirv, apparently there is lack of resources for armhf, yesterday it took hours for another silo to build for armhf too13:50
Mirvabeato: hours is also unfortunately the length of some test runs, added by delay of up to an hour before the excuses page updates13:52
abeatoMirv, :-/13:52
rvrjgdx: Silo 12 approved14:49
jgdxrvr, thank you14:49
Saviqrobru, hey, any idea why it suddenly takes 50mins to prepare just qtmir https://ci-train.ubuntu.com/job/ubuntu-landing-064-1-build/52/console ?15:14
Saviqit's four source packages in total, but still...15:15
abeatoMirv, mind publishing https://requests.ci-train.ubuntu.com/#/ticket/1027 ? need permissions for that15:37
sil2100morphis_: hey!15:41
morphis_sil2100: hey!15:41
sil2100morphis_: if you'd have a moment, could you take a look at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-062/+sourcepub/6095171/+listing-archive-extra ? I prepared a xenial android upload to remove the manta and hammerhead builds from it15:42
sil2100morphis_: could you check if that looks ok?15:42
morphis_sil2100: sure15:42
sil2100morphis_: thanks :)15:43
sil2100morphis_: I checked the build logs and found no mention of manta or hammerhead builds (at least the kernels are not used)15:43
morphis_sil2100: are we landing the same change for vivid?15:53
=== morphis_ is now known as morphis
sil2100morphis: I could potentially, it wasn't a direct requirement as we're not really building any manta images for rc-proposed15:56
sil2100And yeah, the kernel team never really cared about what's in the overlay15:57
morphissil2100: I would like to to minimize the diff between both15:57
abeatosil2100, mind publishing https://requests.ci-train.ubuntu.com/#/ticket/1027 ?15:58
sil2100morphis: ok, I can push the same change to the same silo for vivid :) But I would take care of a full android source sync some other time15:59
morphissil2100: I have that still on my list as there are some changes we need to land16:01
sil2100morphis: ok :) But does the android change look good so far?16:06
morphissil2100: yes, fine with that16:07
sil2100morphis: thanks!16:12
sil2100morphis: so I'll add the vivid part and then publish if you're fine with that16:12
morphissil2100: yes16:13
sil2100morphis: regarding the fix for ntp - is that change already in xenial, or is this phone-specific only?16:16
morphissil2100: better to ask abeato about that16:17
morphissil2100: I just did the silo upload for him :-)16:17
sil2100Oh, ok, since I saw the changelog was from you ;)16:17
sil2100abeato: ^16:17
sil2100ping pong16:17
abeatosil2100, it's for xenial too, see https://bugs.launchpad.net/canonical-devices-system-image/+bug/152626416:18
ubot5Launchpad bug 1526264 in Canonical System Image "ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16)" [High,Confirmed]16:18
abeatosil2100, but we need it in the overlay too16:18
sil2100abeato: indeed - we'll have to prepare a version for xenial too then16:19
abeatosil2100, changing topic, I've built a new system image for frieza with capomastro, which is the process for releasing it?16:22
sil2100abeato: hmmm, you mean a new device tarball?16:23
abeatojohn-mcaleely is out but we need to continue creating images16:24
sil2100abeato: not sure about the details, john-mcaleely would know more, but system-image expects the new tarball in http://people.canonical.com/~jhm/avila/ubuntu/device_frieza.tar.xz16:24
sil2100abeato: and the build ID file here: http://people.canonical.com/~jhm/avila/ubuntu/device_frieza.build16:24
sil2100abeato: once s-i notices a new build in the build ID file, it fetches the device_frieza tarball16:25
abeatosil2100, hmm, I see, I'll need john-mcaleely to push the files there then16:26
Trevinhorobru: something weird happened: https://ci-train.ubuntu.com/job/ubuntu-landing-042-1-build/12/consoleFull16:32
sil2100abeato: I could use a different URL if needed16:38
Trevinhosil2100: do you have any clue on what happened above? ^16:38
abeatosil2100, john-mcaleely is telling me that he will upload it, let's stick with that for the moment16:38
sil2100Trevinho: hey! This usually means someone updated one of the branches from the MPs without rebuilding the silo16:39
sil2100Trevinho: so, if you have an MP, build the silo and then someone pushes a change to that branch, the train will notice and alarm that you have unbuilt revisions (IIRC)16:39
Trevinhosil2100: no... I mean https://ci-train.ubuntu.com/job/ubuntu-landing-042-1-build/12/consoleFull16:40
TrevinhoIt looks like the committer value has too many apices..16:40
Trevinhoouch yeah... committer: ""Andrea Azzarone <azzaronea@gmail.com>16:40
Trevinhobzr per se doesn't fail though, so maybe... For such cases bileto should just trim the string16:41
sil2100Trevinho: hm, I suppose robru would have too look into that16:46
Trevinhosil2100: do you think he could fix it or, should I rebuild the branch?16:46
TrevinhoI mean, in short time? Since we'd need to get this before beta freeze16:47
sil2100Trevinho: I guess rebuilding might help, but robru should be around in ~1-2 hours to give professional advice16:47
Trevinhosil2100: ok thanks16:48
robruTrevinho: I have no idea where those quotes are coming from, but I can push a branch that trims the string, yeah. Will hit production in about an hour17:05
Trevinhorobru: nice, well... It was a mistake from the committer indeed... Since the log has these17:05
Trevinhorobru: see https://www.irccloud.com/pastebin/VqXKKr8W/17:05
TrevinhoHowever, if you can fix that it would be ncie17:06
robruJust need coffee17:06
robruTrevinho: ok fix is in trunk, should hit production in exactly one hour, try again then17:18
Trevinhorobru: nice, thanks17:18
abeatosil2100, do you want me to do something for the ntp? I'm waiting for some sponsor for xenial, but would like to land this for frieza as it was raised by clients17:22
rvrdbarth__: mardy: Silo 61 approved17:47
Saviqtrainguards, can you please retry the failed i386 build in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010 thanks17:50
Saviqfor messaging app I mean17:51
robruSaviq: done17:51
Trevinhorobru: things are working fine now... Thanks for fixing this very-edge case!18:29
=== alan_g is now known as alan_g|EOD
robruTrevinho: haha it was a one-liner. you're welcome18:29
Trevinhorobru: well, I guess it was just about stripping, but still it was kind of you ;-)18:30
robruTrevinho: i love stripping!18:30
Trevinhoahah :D18:31
=== blr_ is now known as blr
dbarth__rvr: thanks20:05
Saviqrobru, can you please copy oxide-qt from ppa:saviq/train to silo 10 (for vivid only atm, xenial in progress)20:28
Saviqactually xenial's still in proposed, won't bump that until that's out of proposed20:31
veebersrobru: not sure about that message/error for veebers/autopilot ^22:43
robruveebers: so sync code is a little bit bit-rotty...22:45
robruveebers: so the package is built in the PPA if you want to start testing it in vivid. can you please file a bug with that traceback? there's some code that's assuming everything is merges and then that sync is failing because there's no merge.22:47
veebersrobru: where would I see the traceback? I can't see it in the jenkins job22:52
robruveebers: what are you looking at? if you click 'status' on the ticket page it goes directly to the jenkins log that is like 90% traceback.22:52
veebersrobru: ah right :-) I was just looking at the build job log that popped up when I hit 'build'22:55
robruveebers: oh yeah no, the status job runs every 15 minutes, it's a different job.22:55

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