/srv/irclogs.ubuntu.com/2016/04/25/#ubuntu-ci-eng.txt

=== chihchun_afk is now known as chihchun
=== pete-woods1 is now known as pete-woods
dbarth_jibel: o/ i commented on the oxide silo card; we found a regression so we'll need to respin a build09:12
jibeldbarth_, silo 38?09:15
jibelokay09:15
dbarth_jibel: yes silo 38; sorry09:16
charlesgrumble09:23
=== vrruiz_ is now known as rvr
jin_jibel, Hello jibel,11:06
jin_could you help us to approve this one in your Trello?11:07
jin_jibel, https://requests.ci-train.ubuntu.com/#/ticket/131211:07
jin_jibel, we will have a release about Telegram11:07
jin_sil2100, hey man11:08
sil2100jin_: hey!11:10
jin_sil2100, HI!!!11:10
jin_we will have a release of Telegram11:10
jin_could you help to sign off that? since it is a click package request11:10
jin_sil2100, this one! https://requests.ci-train.ubuntu.com/#/ticket/131211:11
jibeljin_, set to ready for QA. I'll be on our board soon.11:12
sil2100jin_: ^11:12
jin_jibel, super!!!!!11:12
jin_sil2100, hey thanks man!!11:12
sil2100jin_: I didn't do anything really ;) It's all in QA's hands now11:13
jin_sil2100, OKAY, I gotcha man!11:14
=== alan_g is now known as alan_g|lunch
Saviqkgunn, jibel, I think the only reason for mir 0.22 not being ready for QA is something with s390x in the builders12:50
SaviqMirv, can you recap ↑?12:50
=== _salem is now known as salem_
jibelSaviq, okay, that answers my question. Thanks.12:51
kgunnoh boy12:53
MirvSaviq: jibel: yeah s390x autopkgtests are stuck due to s390x machines failing, but there is no other blocking issue on silo 01912:59
=== alan_g|lunch is now known as alan_g
Mirvmzanetti: 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 removed13:33
Mirvmzanetti: like a comment in the MP13:34
mzanettiMirv, done13:40
tedgSo 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:46
dobeytedg: wait patiently ?13:49
tedgHehe, I can do that.13:49
* tedg waits13:49
* tedg waits13:49
* tedg waits13:49
tedgHmm, perhaps not.13:50
tedg;-)13:50
dobey!patience | tedg13:50
ubot5tedg: Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or http://ubuntuforums.org or http://askubuntu.com/13:50
dobeytedg: or ping whomever was testing it i guess, if it's urgent13:50
tedgIt's not that urgent, just wanted to make sure I was using the tools right.13:51
Mirvmzanetti: cool, fun option :)14:03
=== Laney is now known as trmsu
rvrmzanetti: Saviq: Silo 13 approved14:38
Saviqrvr, \o/14:51
=== trmsu is now known as Laney
=== chihchun is now known as chihchun_afk
=== alan_g is now known as alan_g|EOD
salem_jibel, ping17:32
jibelsalem_, pong18:27
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:28
jibelsalem_, 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.gz18:35
salem_jibel, I don't know, I thought that was a known issue.18:36
jibelsalem_, 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
jibelsalem_, this patch touches something related to account service and the failing test is the account page in the wizard.18:38
jibelsalem_, maybe it's a coincidence but worth checking18:39
jibelbut it fails on only one arch18:39
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:40
jibelsalem_, we didn't force silos recently due to flaky tests in unity818:41
salem_jibel, I think this is the silo I am talking about: https://requests.ci-train.ubuntu.com/#/ticket/120318:43
jibelsalem_, get a confirmation from the unity8 team and we can move on. Otherwise you can also re-run the tests on i38618:47
salem_jibel, ok, thanks18:48
AlbertAtrainguards: any ideas why the s390x tests just never complete? https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-019/excuses.html19:37
dobeyAlbertA: i gues that only gets updated once every 50m-1hr now, so perhaps should get updated the next pass19:39
dobey(as i don't see anything on the running.shtml anyway)19:40
AlbertAdobey: thanks, it's been like that for 4 hrs though... normal?19:41
dobey4 hours?19:44
dobeythe generated time says it was generated an hour ago19:44
dobeythe s390x tests might have only finished in the last hour?19:45
dobeyoh, now it's just updated again and still in progress19:46
dobeyrobru: ^^ any idea19:46
AlbertAdobey: yeah I hit approve on https://requests.ci-train.ubuntu.com/#/ticket/1303 about 4 hours ago... all other tests have finished19:46
AlbertAexcept those... and not sure if they are even running19:46
dobeyAlbertA: right, but when you hit approve is unrelated to when they actually run :)19:47
dobeyother than they will run sometime after that19:47
AlbertAok19:47
dobeybut i don't see them in the queue, so i can only assume they've already finished19:47
dobeyand now the xenial queue is empty on http://autopkgtest.ubuntu.com/running.shtml19:47
dobeyso i guess something is certainly wrong there19:47
dobeybut i don't know what. i'd say we need to get robru to poke19:48
AlbertAdobey: I see thanks19:48
sil2100hmmm19:53
sil2100Well, robru is on leave this week, so this might be tricky19:53
dobeyoh19:54
robrusil2100: dobey more of an issue for pitti19:54
robruFortunately the debug logs are still enabled from last time19:55
robruAlso qa status can be overridden even if britney fails so no big deal19:55
sil2100AlbertA: could you poke pitti about it on #ubuntu-devel or #ubuntu-touch ?19:55
robruBbl19:56
AlbertAsil2100: yeah thanks19:59

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