[09:12] <dbarth_> jibel: o/ i commented on the oxide silo card; we found a regression so we'll need to respin a build
[09:15] <jibel> dbarth_, silo 38?
[09:15] <jibel> okay
[09:16] <dbarth_> jibel: yes silo 38; sorry
[09:23] <charles> grumble
[11:06] <jin_> jibel, Hello jibel,
[11:07] <jin_> could you help us to approve this one in your Trello?
[11:07] <jin_> jibel, https://requests.ci-train.ubuntu.com/#/ticket/1312
[11:07] <jin_> jibel, we will have a release about Telegram
[11:08] <jin_> sil2100, hey man
[11:10] <sil2100> jin_: hey!
[11:10] <jin_> sil2100, HI!!!
[11:10] <jin_> we will have a release of Telegram
[11:10] <jin_> could you help to sign off that? since it is a click package request
[11:11] <jin_> sil2100, this one! https://requests.ci-train.ubuntu.com/#/ticket/1312
[11:12] <jibel> jin_, set to ready for QA. I'll be on our board soon.
[11:12] <sil2100> jin_: ^
[11:12] <jin_> jibel, super!!!!!
[11:12] <jin_> sil2100, hey thanks man!!
[11:13] <sil2100> jin_: I didn't do anything really ;) It's all in QA's hands now
[11:14] <jin_> sil2100, OKAY, I gotcha man!
[12:50] <Saviq> kgunn, jibel, I think the only reason for mir 0.22 not being ready for QA is something with s390x in the builders
[12:50] <Saviq> Mirv, can you recap ↑?
[12:51] <jibel> Saviq, okay, that answers my question. Thanks.
[12:53] <kgunn> oh boy
[12:59] <Mirv> Saviq: jibel: yeah s390x autopkgtests are stuck due to s390x machines failing, but there is no other blocking issue on silo 019
[13:33] <Mirv> mzanetti: I think it would be useful (at least I'd be interested) documenting why removing stuff adds support in https://code.launchpad.net/~mzanetti/ubuntu-touch-session/enable-obex-push/+merge/291978 - and what are the opp and filesystem removed
[13:34] <Mirv> mzanetti: like a comment in the MP
[13:40] <mzanetti> Mirv, done
[13:46] <tedg> So I've fixed an issue on the card in the QA tracker. I put a comment in. Is there anything else I'm supposed to do?
[13:49] <dobey> tedg: wait patiently ?
[13:49] <tedg> Hehe, I can do that.
[13:49]  * tedg waits
[13:49]  * tedg waits
[13:49]  * tedg waits
[13:50] <tedg> Hmm, perhaps not.
[13:50] <tedg> ;-)
[13:50] <dobey> !patience | tedg
[13:50] <dobey> tedg: or ping whomever was testing it i guess, if it's urgent
[13:51] <tedg> It's not that urgent, just wanted to make sure I was using the tools right.
[14:03] <Mirv> mzanetti: cool, fun option :)
[14:38] <rvr> mzanetti: Saviq: Silo 13 approved
[14:51] <Saviq> rvr, \o/
[17:32] <salem_> jibel, ping
[18:27] <jibel> salem_, pong
[18:28] <salem_> jibel, hey, just wanted to check if we have any update on silo 55 with the unity8 test failures. Can we get that silo on the testing queue?
[18:35] <jibel> salem_, why is unity8 failng?
[18:35] <salem_> jibel, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid-ci-train-ppa-service-landing-055/vivid/armhf/u/unity8/20160418_180555@/log.gz
[18:36] <salem_> jibel, I don't know, I thought that was a known issue.
[18:38] <jibel> salem_, I don't know. Did you ask the unity8 team?
[18:38] <salem_> Saviq, ^^ do you know if this is a known issue?
[18:38] <jibel> salem_, this patch touches something related to account service and the failing test is the account page in the wizard.
[18:39] <jibel> salem_, maybe it's a coincidence but worth checking
[18:39] <jibel> but it fails on only one arch
[18:40] <salem_> jibel, yes, that's why I believe it's unlikely to be caused by our patch. I had this very same problem on a past telephony-service landing.
[18:41] <jibel> salem_, we didn't force silos recently due to flaky tests in unity8
[18:43] <salem_> jibel, I think this is the silo I am talking about: https://requests.ci-train.ubuntu.com/#/ticket/1203
[18:47] <jibel> salem_, get a confirmation from the unity8 team and we can move on. Otherwise you can also re-run the tests on i386
[18:48] <salem_> jibel, ok, thanks
[19:37] <AlbertA> trainguards: any ideas why the s390x tests just never complete? https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-019/excuses.html
[19:39] <dobey> AlbertA: i gues that only gets updated once every 50m-1hr now, so perhaps should get updated the next pass
[19:40] <dobey> (as i don't see anything on the running.shtml anyway)
[19:41] <AlbertA> dobey: thanks, it's been like that for 4 hrs though... normal?
[19:44] <dobey> 4 hours?
[19:44] <dobey> the generated time says it was generated an hour ago
[19:45] <dobey> the s390x tests might have only finished in the last hour?
[19:46] <dobey> oh, now it's just updated again and still in progress
[19:46] <dobey> robru: ^^ any idea
[19:46] <AlbertA> dobey: yeah I hit approve on https://requests.ci-train.ubuntu.com/#/ticket/1303 about 4 hours ago... all other tests have finished
[19:46] <AlbertA> except those... and not sure if they are even running
[19:47] <dobey> AlbertA: right, but when you hit approve is unrelated to when they actually run :)
[19:47] <dobey> other than they will run sometime after that
[19:47] <AlbertA> ok
[19:47] <dobey> but i don't see them in the queue, so i can only assume they've already finished
[19:47] <dobey> and now the xenial queue is empty on http://autopkgtest.ubuntu.com/running.shtml
[19:47] <dobey> so i guess something is certainly wrong there
[19:48] <dobey> but i don't know what. i'd say we need to get robru to poke
[19:48] <AlbertA> dobey: I see thanks
[19:53] <sil2100> hmmm
[19:53] <sil2100> Well, robru is on leave this week, so this might be tricky
[19:54] <dobey> oh
[19:54] <robru> sil2100: dobey more of an issue for pitti
[19:55] <robru> Fortunately the debug logs are still enabled from last time
[19:55] <robru> Also qa status can be overridden even if britney fails so no big deal
[19:55] <sil2100> AlbertA: could you poke pitti about it on #ubuntu-devel or #ubuntu-touch ?
[19:56] <robru> Bbl
[19:59] <AlbertA> sil2100: yeah thanks