[00:02] <ogra_> slangasek, no idea, sorry jibel mentioned that something changed recently, perhaps he knows more, I did just hit the build button...
[07:16] <Mirv> welcome back sil2100, it's been ok but slightly challenging :)
[07:18] <sil2100> Mirv: thanks! Hope you'll finally be able to fully rest, feeling any better?
[07:19] <Mirv> sil2100: somewhat better now yes
[07:20] <sil2100> morphis: hmm, looking at silo 29 now - why is the final version number prefixed with a ~stublinker4 ? Is that wanted?
[07:22] <morphis> sil2100: it shouldn't, uploaded 0ubuntu11 yesterday
[07:22] <morphis> see https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-029/+packages
[07:23] <morphis> only shows me 0.1.0+git20151016+6d424c9-0ubuntu11
[07:23] <sil2100> Maybe it's a stale diff, let me run diff_only
[07:23] <morphis> ok
[07:23] <morphis> sil2100: and welcome back :-)
[07:23] <sil2100> morphis: thanks :)
[07:23] <morphis> sil2100: you already saw if we got an successful image build yesterday?
[07:24] <jibel> morphis, there is a new image this morning
[07:24] <morphis> jibel: awesome!
[07:25] <jibel> sil2100, something has been wrong with the importer, it failed with http://paste.ubuntu.com/16207648/ then an image appeared in the middle of the night
[07:25] <jibel> sil2100, good morning :)
[07:44] <sil2100> jibel: yeah looking into that, there are some weird things going on with one custom tarball it's processing
[08:22] <davmor2> jibel: so turns out my isp have picked today to remove cables and put in new ones \o/ fortunately for me I have a mifi but irc will most likely be out so I'll stay connected here
[08:31] <jibel> davmor2_, ok
[09:28] <sil2100> morphis: I don't know much about the stub linker bits in hybris so apologies if this question doesn't make sense, but just confirming - is it ok that for the arm64 case we don't build with --enable-arch=arm and only with the --enable-stub-linker ?
[09:31] <sil2100> morphis: ah, I guess it's ok as it's a no-op linker right now anyway
[09:53] <morphis> sil2100: yes
[09:53] <morphis> sil2100: --enable-arch= only has an effect if we have a real linker implementation which we don't have with the stub
[10:06] <sil2100> Argh
[10:06] <sil2100> Wrong target
[14:07] <jgdx> rvr, hey, where are we with the vpn silo? :)
[14:07] <rvr> jgdx: It's on the queue
[14:08] <rvr> Actually, on the t op of the queue :)
[14:10] <jgdx> rvr, \o/
[14:11] <kenvandine> jibel, unity8 autopkgtests are failing for my landing in silo 49, but they aren't related.  can you guys go ahead and move it to ready to land?
[14:11] <kenvandine> jibel, also, how are those autopkgtest rdepends defined for britney?  I'm not sure ubuntu-system-settings should require unity8 tests anymore, it was probably useful when settings provided the wizard
[14:17] <jibel> kenvandine, done
[14:18] <kenvandine> jibel, thanks!
[14:19] <jibel> kenvandine, IIRC tests are triggered for all the direct reverse dependencies with auto package tests
[14:19] <jibel> kenvandine, and unity8 depends on ubuntu-system-settings
[14:20] <kenvandine> i wonder why it depends on uss
[14:20] <kenvandine> i think that is a bogus depends now...
[14:20] <kenvandine> Saviq, ^^ any idea?
[14:20] <Saviq> could very well be
[14:24] <Saviq> kenvandine, https://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/1475 this came in with the wizard - ltinkl do you know if unity8's dependency on ubuntu-system-settings is real? or could we limit ourselves to libsystem-settings or so?
[14:26] <kenvandine> if you need libsystemsettings1 then it would still trigger this
[14:26] <kenvandine> do you directly import any of our components?
[14:26] <kenvandine> if you do it's a valid depends
[14:28] <ltinkl> kenvandine, Saviq: we do import the components in Wizard at least
[14:28] <kenvandine> ok, then it's valid
[14:28] <kenvandine> thanks!
[15:21] <tedg> sil2100: Can you retry this build for me please? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+build/9689457
[15:23] <sil2100> tedg: on it
[15:23] <sil2100> tedg: done
[15:23] <tedg> sil2100: Thanks!
[15:24] <sil2100> np!
[15:55] <popey> pstolowski: what logs do I need for https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1578283 ?
[15:55] <popey> My phone is pretty unusable with rc-proposed when I can't see any apps :)
[16:03] <pstolowski> popey, ~/.cache/upstart/scope-registry.log
[16:05] <pstolowski> popey, also unity8-dash.log may be useful (same directory)
[16:10] <popey> pstolowski: okay
[16:10] <pstolowski> popey, does it help if you pull-to-refresh when this happens?
[16:10] <popey> pstolowski: if I do that about 30 times, yeah, sometime
[16:11] <dobey> popey: and there's no crash for the scope in /var/crash/ ?
[16:11] <popey> nope
[16:12] <popey> pstolowski: linked logs in bug
[16:12] <pstolowski> popey, thanks
[16:13] <ChrisTownsend> trainguards: I have a regression shown in my request's britney run, but it doesn't look like it's my packages fault: https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-031/excuses.html
[16:13] <dobey> popey: how many apps do you have installed btw?
[16:14] <robru> ChrisTownsend: you can ask qa to add it to their queue anyway
[16:16] <popey> phablet@ubuntu-phablet:~$ click list | wc -l
[16:16] <popey> 230
[16:17] <popey> dobey: ^
[16:17] <ChrisTownsend> robru: Ok, works for me:)  Thanks
[16:17] <dobey> hmm
[16:17] <pstolowski> popey, looking at this log, was it a case where pull-to-refresh helped after ~5 refreshes?
[16:17] <robru> ChrisTownsend: you're welcome
[16:17] <popey> no, way more
[16:18] <popey> i had to pull and then started rotating the phone around
[16:19] <dobey> very weird
[16:20] <ChrisTownsend> ubuntu-qa: Hi, could we get https://requests.ci-train.ubuntu.com/#/ticket/1328 back on the queue again?  It failed automated signoff, but it is due to some transient issue not related to my package.
[16:20] <pstolowski> dobey, indeed. the log has a couple messages with "flushUpdates: "clickscope" #results = 0 finalize: true"
[16:20] <ChrisTownsend> ubuntu-qa: That previously failed QA, but I have fixed it.
[16:22] <davmor2> jibel: ^ is that a you or sil2100 thing?
[16:25] <dobey> pstolowski: is it possibly timing out?
[16:26] <Mirv> ChrisTownsend: I've retried the failed test now
[16:26] <Mirv> the page will be slow to upload though, plus the time to do the run
[16:26] <ChrisTownsend> Mirv: Ok, thanks!
[16:27] <pstolowski> dobey, I think we would see something in the log if it timed out (scope-registry.log probably)
[16:33] <jibel> davmor2, what is me?
[16:34] <jibel> davmor2, ah silo 31
[16:34] <davmor2> jibel: ChrisTownsend has a failed automation silo that he wants to get back into QA it fails on a unity8 test
[16:34] <jibel> we are forcing lot of packages failing autopkgtest lately
[16:34] <jibel> ChrisTownsend, what is this ofono-phonesim error?
[16:35] <jibel> clearly nothing to do with kbd layouts
[16:36] <jibel> or keymaps
[16:36] <jibel> ChrisTownsend, marked ready
[16:36] <ChrisTownsend> jibel: Ok, thanks.  It truly looked transient.
[16:37] <ChrisTownsend> jibel: I really don't understand why that tests runs against xserver anyways, but I digress.
[16:39] <jibel> ChrisTownsend, yeah, I don't see any obvious dependency
[16:40] <jibel> ChrisTownsend, ah ofono-phonesim-autostart depends on xvfb built from xorg-server
[16:41] <ChrisTownsend> jibel: Ah, ok.
[16:55] <boiko> jibel: earlier this morning I saw you were testing silo 46, but now it is in ready for testing column again, any problem with this one?
[16:58] <jibel> boiko, yes, I cannot fake an emergency number and don't want to test a real one
[16:59] <jibel> boiko, the method with mc-tools stopped working apparently. Do you have any way to test emergency numbers?
[16:59] <boiko> jibel: I usually just call a real one and hangup quiclky
[16:59] <jibel> lol
[16:59] <jibel> I cannot do that
[17:00] <jibel> you don't even know if the call is really made if you hangup really quickly
[17:01] <dobey> calling a real emergency number just to test your phone is a really good way to rack up fines and get arrested :)
[17:02] <jibel> if boiko stops replying on irc we'll know why now :)
[17:02] <boiko> jibel: :)
[17:04] <boiko> jibel: telepathy-ofono still has the fakeEmergencyNumbers property
[17:04] <boiko> jibel: I mean, fakeEmergencyNumber, that should still be working
[17:04] <jibel> boiko, yes that's what I tried but it didn't work.
[17:05] <salem_> jibel, did you set on both ofono accounts?
[17:06] <jibel> salem_, just one, I'll try with both