=== salem_ is now known as _salem
=== chihchun_afk is now known as chihchun
Mirvjgdx: seb128 is asking for revert of indicator-datetime from https://requests.ci-train.ubuntu.com/#/silo/054 because it's crashing on login screen on Unity 7. a revert is currently building at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-017/+packages06:56
Mirvideas/fixes welcome06:56
Mirvjgdx: duflu discovered it on #ubuntu-desktop http://pastebin.ubuntu.com/20008534/06:58
Mirvso bug #160425106:58
ubot5bug 1604251 in indicator-datetime (Ubuntu) "indicator-datetime-service crashes immediately on the yakkety login screen; with signal 5 (SIGTRAP) in g_object_new_valist()" [Medium,New] https://launchpad.net/bugs/160425106:58
bzoltancjwatson: I could not figure anything out with chdits about this - https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-019/xenial/ppc64el/u/ubuntu-system-settings-online-accounts/20160718_054019@/log.gz07:01
Mirvsil2100: indicator-datetime possible revert needed http://pastebin.ubuntu.com/20011634/07:53
sil2100Mirv: ACK, are you using the train revert function for this?07:53
Mirvsil2100: yes07:54
Mirvthe silo is ready, just not sure if it's safe to revert only that either, but at least is ready07:54
sil2100I'm thinking if we shouldn't just revert it for yakkety07:55
sil2100Oh, no, actually not07:56
jgdxMirv, ugh okay.07:56
jgdxMirv, seb128: okay, I'll bump the version08:04
seb128jgdx, Mirv, I think the issue is that the key is in the touch schemas which isn't installed on the desktop and not in the depends08:06
jgdxseb128, okay08:07
seb128jgdx, Mirv, ignore that, looks like we merged the schemas (which makes sense) so it's likely just the version that needs to be updated08:07
jgdxseb128, okay, there's a dep there, on gsettings-ubuntu-schemas (>= 0.0.7)08:08
jgdxbut the change was in -touch-schemas08:09
seb128that's not new enough08:09
seb128it was not there in 0.0.7+16.10.20160615.1-0ubuntu108:10
seb128which is > 0.708:10
seb128you want >= 0.0.7+16.10.2016070108:10
jgdxgsettings-ubuntu-schemas == gsettings-ubuntu-touch-schemas, though right?08:11
seb128gsettings-ubuntu-touch-schemas is a dummy transational binary08:13
jgdxseb128, the whole silo was reverted?08:14
seb128Mirv ^08:14
jgdxseems so08:16
jgdxMirv, sil2100: okay, I'm waiting for the word on what happened to the silo, if we need to land that again with the deps in order or what. :)08:24
Mirvjgdx: no the https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-017/+packages currently just has indicator-datetime08:25
Mirvjgdx: and it's only a silo, nothing is really reverted yet08:25
Mirvjgdx: but ubuntu-system-settings and gsettings-ubuntu-touch-schemas are stuck in proposed from the original landing https://requests.ci-train.ubuntu.com/#/silo/05408:25
jgdxMirv, not sure what you're saying. I'm thinking maybe I could help fix this in Arthur's absence, but it's not clear to me what I need to do.08:29
Mirvjgdx: you were asking about what happened to the silo - it's still landed. there's another silo with just indicator-datetime revert in it, but I don't know if it is safe to revert just indicator-datetime alone.08:33
Mirvjgdx: and additionally regarding the silo, the two packages are stuck in proposed so not really in yakkety08:34
seb128which ones?08:36
seb128because the indicator is not stucked in proposed08:37
seb128which is why users hit the issue08:37
Mirvhttps://requests.ci-train.ubuntu.com/#/silo/054 -> Proposed pocket ( gsettings-ubuntu-touch-schemas/yakkety, ubuntu-system-settings/yakkety).08:49
cjwatsonbzoltan: Nor can I.  I've asked pitti to help11:47
ogra_sil2100, can your pending livecd-rootfs chnages be uploaded ?12:01
ogra_(happy to do it, just want to make sure )12:01
sil2100ogra_: yes, we have the same bits in vivid already released and nothing exploded12:27
sil2100I didn't want to unnecessarily release those since they weren't needed in yakkety instantly12:28
rvrrenatu: ping12:29
Mirvsil2100: any silo to follow regarding xenial not booting (on my krillin)?12:31
sil2100Mirv: we didn't check unbootability on xenial recently12:32
MirvI'm trying to figure out what's reported and what's not, since I'd need working xenial base in order to try out Qt 5.6.1 soon12:32
Mirvsil2100: yeah something would seem to be up12:32
Mirvcrashalot http://pastebin.ubuntu.com/20030881/12:33
bzoltancjwatson: thanks12:33
renatutrainguards, any idea what is happening on silo 73? It was building nice last week. This week is not building and we did not change any code13:15
renaturvr, hey victor13:16
rvrrenatu: Hi13:16
rvrrenatu: You already answered my question :)13:16
renaturvr, I am trying to solve the build problem with trainguards13:16
rvrrenatu: Ack13:16
Mirvrenatu: account-polld fails with dh_auto_build: go install -v launchpad.net/account-polld/... returned exit code 113:16
renaturvr, it is not a code problem. Something has changed on the build system13:16
Mirvrenatu: go build error on all three (yakkety, xenial, vivid), but I think you need to try to build it locally to find out what's wrong as there's not much error output. on vivid it's "dh_auto_build: go install -v launchpad.net/account-polld/accounts launchpad.net/account-polld/cmd/account-polld launchpad.net/account-polld/cmd/account-watcher-test launchpad.net/account-polld/cmd/qtcontact-test launchpad13:17
Mirv.net/account-polld/gettext launchpad.net/account-polld/plugins launchpad.net/account-polld/plugins/gcalendar launchpad.net/account-polld/plugins/gmail launchpad.net/account-polld/plugins/twitter launchpad.net/account-polld/plugins/twitter/oauth launchpad.net/account-polld/pollbus launchpad.net/account-polld/qtcontact returned exit code 1"13:17
Mirvsee log at https://launchpadlibrarian.net/273920282/buildlog_ubuntu-vivid-amd64.account-polld_0.1+15.04.20160719-0ubuntu1_BUILDING.txt.gz13:18
renatuMirv, yes something changed on the build environment. I will check with go experts what I can do to fix that.13:19
Mirvok, thanks13:21
rvrrenatu: Another question. I have a "Reminders" calendar in Google Calendar, that I cannot see in the calendar app. Do you know whether "reminders" is a special calendar in Google?13:22
renaturvr, yes "reminders" as a special kind not supported by calendar-app13:22
rvrrenatu: Ok13:23
renatuwe should have a reminder app or implement integration on our calendar-app13:23
renatunot defined yet13:23
rvrrenatu: Related... How can I reproduce "Reminders synced from google does not appear on the app"?13:24
renaturvr, create a notification on your event.13:25
renaturvr, maybe I should rephrase that it could cause confusions :D13:26
renaturvr, edit you event and add a reminder/notification on it (like 10 mins before the event)13:26
renatumake sure that appear on the calendar-app13:26
renatuMirv, it builds nice on my machine13:27
=== _salem is now known as salem_
renatuMirv, this error: rc/launchpad.net/account-polld/cmd/account-polld/account_manager.go:27:2: cannot find package "launchpad.net/ubuntu-push/click/cblacklist" in any of:13:30
renatu/usr/lib/go/src/pkg/launchpad.net/ubuntu-push/click/cblacklist (from $GOROOT)13:30
renatulooks strange13:30
renatusince this file is part of "golang-ubuntu-push-dev" and it is already in the build dep list13:31
renatuMirv, oh, wait the version of that package used by the build system is not the same version that I have in my machine13:33
Mirvrenatu: since it's failing consistently on all three series, it's at least not eg yakkety devel specific problem but a general one13:34
renatuMirv, yes it is using a version from overlay ppa13:34
renatuthis version changed something that broken the build13:35
renatuMirv, I think I found the problem: https://requests.ci-train.ubuntu.com/#/ticket/137813:39
renatuMirv, this silo needs to land13:39
Mirvrenatu: it has landed for xenial + vivid already, so it can't be the reason for xenial/vivid builds landing13:40
renatuMirv, the mr did not merged13:42
Mirvrenatu: ah right, yes, that would be a problem. because the yakkety packages are stuck, the merge is not happening.13:42
sil2100It seems this one landing causes various issues everywhere13:42
renatuit contains the necessary changes for account-polld to build again13:43
Mirvwell at least the fact that it hasn't really landed13:43
Mirvit seems ubuntu-system-settings is stuck in yakkety-proposed for the same mysterious problem on ppc64el that UITK can't get to QA queue: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/ppc64el/u/ubuntu-system-settings-online-accounts/20160718_185637@/log.gz13:43
Mirvbzoltan and cjwatson were talking about it earlier, and that looks similar13:44
=== kzapalowicz is now known as koza
kenvandineMirv, i've confirmed that indicator-datetime bug seems to be caused by the schema package being held in yakkety-proposed14:21
kenvandineso no need to revert it... we just need to get that package promoted :)14:21
kenvandineMirv, jgdx has a branch bumping the depends version, which is good but won't actually fix it for anyone that has updated until that package is promoted14:22
dbarthhey trainguards; could you remove the signon-ui packages in silo 062 please?14:27
sil2100dbarth: on it14:27
dbarthi have reconfigured the silo to exclude a broken merge proposal14:27
sil2100dbarth: removed :) yw!14:27
=== chihchun is now known as chihchun_afk
seb128Mirv, you didn't land the indicator-datetime revert?15:10
kenvandineseb128, hey15:17
kenvandineseb128, please don't revert that ;)15:17
kenvandineonce the schema gets migrated to release it'll be fine15:18
seb128wth people15:18
seb128meanwhile everybody is broken in yakkety15:18
kenvandinewe have a branch that bumps the depends15:18
kenvandinebut that won't actually fix anything15:18
seb128if it had been reverted 10 hours it would be already fixed for users15:18
kenvandinesince it'll get blocked as well15:18
kenvandineyeah... but now we'll know in an hour or so if it'll migrate15:18
seb128which is why I wanted a revert this morning15:18
seb128best path to fix users15:18
kenvandinewaiting for those flaky unity8 tests15:18
seb128then figure out the screwups15:18
kenvandinethe autopkgtests passed for yakkety in the silo15:19
seb128meanwhile we just screwed all the users who updated since this morning15:19
kenvandinei know15:19
kenvandinebut we're close now15:19
seb128we should have reverted15:19
kenvandineor if we could force the migration?15:19
seb128yeah, classic "it's going to be fixed soon"15:19
bfillerseb128, kenvandine : quickest solution would be to get those packages held in proposed from silo 54 landed15:19
seb128and one day later users are still screwed15:19
kenvandinewe know the tests passed in the silo15:19
bfillerand not wait for the autopackage tests to run again15:19
seb128that silo is not going to fix anything15:20
kenvandineseb128, no, that shows the tests passed there15:20
seb128it's going to block the silo version in proposed with the schemas until that one migrates15:20
kenvandinecan we force the migration?15:20
bfillerkenvandine, seb128: yes that's what I'm saying, force migration as we know the tests alaready passed15:20
seb128I guess pitti or such could15:20
* kenvandine hates those flaky unity8 tests15:20
seb128also who approved that landing?15:20
seb128was that reviewed by somebody with upload rights?15:21
seb128it has packaging changes15:21
seb128it should have gone through a coredev ack15:21
kenvandineoh... me :)15:21
kenvandineyou can yell at me :)15:21
seb128well errors happens :p15:21
seb128I'm going to rent at you for arguing against reverting in case of regressions15:21
kenvandine8-               gsettings-ubuntu-schemas,15:21
kenvandine9+               gsettings-ubuntu-schemas (>= 0.0.7),15:21
kenvandinei saw that15:21
kenvandineand thought it was good enough15:22
kenvandinebut it wasn't15:22
seb128yeah, honest mistake, don't worry15:22
seb128still when there is a regression that hits users we should revert15:22
kenvandinei should have checked the archive15:22
seb128not wait half a day that u.s wake up to start figuring out to fix15:22
seb128and have another half a day to land a fix15:22
kenvandinethe revert silo failed to build15:23
seb128next time I guess I just dput a revert15:23
seb128screw buggy ci processes :p15:23
kenvandinefor vivid only15:23
kenvandinea revert to yakkety only would have been harmless15:23
seb128I should have done that15:23
seb128Mirv also didn't tell me he was stucked on not acting on it15:24
bfillerkenvandine, seb128: so options I see at this point  to fix broken yakety 1) force migration of silo 54 2) revert changes 3) wait until autopackage tests (hopefully) pass so migration of silo 54 can continue. My pref is 1). thoughts?15:27
kenvandinei'd prefer 1 as well15:27
kenvandinebut a manual dput of indicator-datetime reverting the change to yakkety only would be harmless too15:28
bfillerfine with that15:28
kenvandinebut we'd have to wait for it to get through the proposed migration as well15:28
kenvandineforced migration would be quicker15:28
seb128let me poke pitti15:28
kenvandineseb128, thx!15:28
seb128kenvandine, bfiller, pitti is letting it through but somebody needs to fix the unity8 tests15:33
kenvandineseb128, we've complained about it15:33
kenvandinethey said someone is looking into it15:34
kenvandineit's been a problem for quite a while15:34
bfillerseb128: ack15:34
seb128right, pitti and L_aney pointed out that, next time not forcing over because apparently it has been like that for a while and skipping removes the incensitive the fix things15:35
kenvandineseb128, these tests cause me to spend days clicking retry ever 3 hours :(15:35
seb128why isn't anyone in the unity8 team dealing with it?15:35
seb128it's stupid15:35
kenvandineSaviq said someone is working on it15:35
seb128where is Saviq? ;-)15:36
kenvandinea couple weeks ago15:36
kenvandinehanging out in germany :)15:36
kenvandinehe's at the sprint15:36
rvrrenatu: Silo 73 approved15:37
ogra_he said he is on vacation til tomorrow (i met him in the hotel restaurant/garden)15:37
renaturvr, thanks, bfiller ^^15:37
rvrmardy: dbarth: I need the test scope and credentials for silo 5915:39
dbarthrvr: ack; on a call, brb15:41
Mirvseb128: I mentioned it was unclear to me whether it's safe to revert just indicator-datetime while 054 had many related packages in it. there were too many cooks handling this soup.15:41
seb128when in doubt revert it all :-)15:42
seb128oh well, it's forced though now15:42
Mirvyeah I read the backlog15:42
rvrMirv: What is the problem with 54?15:42
kenvandinervr, the gsettings schema was held in proposed and broke indicator-datetime in yakkety15:43
kenvandineheld because of the flaky unity8 autopkgtests15:43
kenvandinewhich passed in the silo, but get rerun for proposed migration15:44
rvrkenvandine: I see15:44
* kenvandine needs to step out for lunch, bbiab15:44
sil2100seb128: hey! I know I overused your trust through the repowerd preNEW thing (;p), but maybe you could take a look in some spare time at the binNEW of https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-1037/2016-07-19_14:11:37/yakkety_address-book-service_packaging_changes.diff from silo 73? ;)15:44
popeysil2100: when is ota-12 due?15:46
seb128sil2100, hey, don't worry about that, miscommunication can happen ... looking ;-)15:46
sil2100popey: next week, hopefully early next week - worst case around Wednesday15:46
popeysil2100: thanks, hope it goes well!15:47
rvrjgdx: Silo 37 merge proposal needs approval.15:47
seb128sil2100, usr/lib/evolution-data-server/registry-modules/module-ubuntu-sources.so is moved between binaries, that needs a N15:48
seb128sil2100, the binary naming doesn't seem really great, e-d-s-ubuntu?15:48
seb128I've no clue even from the description how that's ubuntu specific15:49
seb128is that of ubuntuone accounts?15:49
sil2100Right, didn't look into the packaging yet, this needs to be fixed before we can push that out! For the descriptions, it's ubuntu specific I guess because it deals with apps for the Ubuntu app store15:52
* sil2100 needs to get back to the habbit of checking packages first before giving them to preNEW review16:08
ogra_pffft ... just wait til you get bug reports from users ...16:09
dobeyseb128, sil2100: what the heck is that?16:43
dobeythe e-d-s-ubuntu thing16:43
seb128I don't really understand it from the description16:44
dobeyyeah, that oesn't make much sense to me either16:44
dobeyhttps://code.launchpad.net/~renatofilho/address-book-service/create-eds-extension-package/+merge/296447 doesn't tell me anything more either really16:47
kenvandineBroken ubuntu-system-settings:ppc64el Depends on powerd:ppc64el < none | 2016.06+16.10.20160706.1-0ubuntu1 @un uH > (>= 0.15)16:48
kenvandineseb128, ^^ does that make any sense to you?16:48
seb128kenvandine, is that yakkety?16:48
kenvandinei guess it's just the lack of powerd for ppc64el16:49
kenvandinethe system-settings migration is held up because of the ubuntu-system-settings-online-accounts autopkgtest failure on yakkety ppc64el16:49
seb128kenvandine, unsure, but powerd is built from repowerd there now16:50
kenvandinewhich is failing to resolve depends16:50
seb128but that was reverted in the overlay16:50
seb128so yakkety and overlay are out of sync on that16:50
seb128unsure how that works with landings16:50
kenvandinethe depends it's missing is actually system-settings16:50
dobeythe problem is repowerd isn't build on ppc16:51
seb128you mean?16:51
kenvandineuss-oa depends on uss, uss depends on powerd16:51
seb128well powerd wasn't either16:51
dobeythen how would it have passed before?16:51
kenvandinemaybe the lack of passing tests for ppc64el didn't used to hold up proposed migration?16:52
seb128britney blocks regressions16:52
seb128it doesn't require you to build on all arches16:52
seb128just to not build on less than you used to build on16:52
kenvandineso it must have passed on this arch before16:52
dobeyright, but if it's blocking, then it must have regressed16:52
seb128so if it never existed there it's fine16:52
seb128well https://launchpad.net/ubuntu/+source/powerd/0.16+16.04.20160204.1-0ubuntu2~xenial116:52
seb128britney compare pockets16:52
seb128and it doesn't exist there16:52
seb128what page are you looking at?16:53
dobeyhmm, weird16:53
dobeykenvandine: i see s390x was marked ignored16:53
kenvandineautopkgtest for ubuntu-system-settings-online-accounts/0.7+16.10.20160628.2-0ubuntu1: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Ignored failure16:54
seb128it fails the autopkgtest for online accounts on ppc64el16:54
dobeymaybe it need to be flagged16:54
kenvandinethe failure is that it can't install system-settings16:54
kenvandinebecause of missing powerd16:54
kenvandineso powerd must have been built there at one point16:54
kenvandineand deleted?16:54
cjwatsonI'm sceptical that it's just that16:55
cjwatsonubuntu-system-settings depends on powerd | gnome-settings-daemon, and gnome-settings-daemon is installable on ppc64el16:55
kenvandineso maybe i'm going down the wrong rabbit hole16:55
cjwatsonYou might be.  I'd suggest looking at old successful test logs and seeing which set of packages they managed to install16:56
cjwatsonIf they installed gnome-settings-daemon, then powerd is very likely the wrong rabbit-hole16:56
kenvandine  Holding Back ubuntu-system-settings:ppc64el rather than change gnome-settings-daemon:ppc64el16:56
cjwatsonYeah, but why :)16:57
cjwatsonI couldn't reproduce in chdist when I tried earlier16:57
cjwatsonBut I didn't have quite the same setup, and I ran out of time to dig16:57
kenvandineSetting up gnome-settings-daemon (3.18.2-0ubuntu3) ...16:57
kenvandinefrom the last pass16:57
dobeyugh what a mess16:59
dobey(this silo)16:59
kenvandineactually i was asking mardy about this a few days ago16:59
kenvandinei saw this failure in a silo16:59
kenvandinenot silo 54 :)17:00
kenvandinebut 54 does seem cursed17:00
dobeyright, but either way, it's the same issue17:00
kenvandineand these logs are very confusing17:00
dobeywell, this issue is the same issue. all the other issues i have with that silo are different from this one :)17:01
cjwatsonkenvandine: If you have a recent-ish successful log, diffing against the latest failure is sometimes a helpful approach17:01
kenvandinediff the logs?17:02
kenvandinedoubt that will help, the successful one installs the deps :)17:02
kenvandinenever get to that point on the failing log17:02
jgdxkenvandine, do you have acc to set [1] as approved too? [1] https://code.launchpad.net/~jonas-drange/ubuntu-settings-components/tap-not-swipe/+merge/29979817:02
jgdxkenvandine, I don't17:02
kenvandinejgdx, i'll check17:02
kenvandinecjwatson, the passing log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/ppc64el/u/ubuntu-system-settings-online-accounts/20160711_105452@/log.gz17:03
kenvandinejgdx, done17:03
jgdxkenvandine, thanks!17:04
jgdxrvr, it's done (silo 37 mp approved)17:04
cjwatsonkenvandine: I'm not going to look in more detail, but the reason I think it might help is that perhaps the packages installed earlier on in the log will differ17:04
dobeykenvandine: i think the issue is related to the gnome-settings-daemon/gnome-control-center vs unity-settings-daemon/unity-control-center stuff17:05
dobeycjwatson: since your here, might you have any idea why when building a package with sbuild, a dep like "pyflakes3 | pyflakes (>= M.N)" would not be falling back to the or-depends (ie, it wants to always intall pyflakes3)?17:08
dobeyit seems to work fine on lp builders, but is failing in jenkins17:09
cjwatsondobey: sbuild --resolve-alternatives17:09
dobeyi wonder if it's not doing that. thanks17:09
kenvandineonly obvious difference is binutils17:10
kenvandine-Get:3 http://ftpmaster.internal/ubuntu yakkety/main ppc64el binutils ppc64el 2.26.1-1ubuntu1 [2,324 kB]17:10
kenvandine+Get:3 http://ftpmaster.internal/ubuntu yakkety/main ppc64el binutils ppc64el 2.26.1-1ubuntu2 [2,322 kB]17:10
cjwatsonmkay, so maybe not17:11
kenvandineyeah :/17:11
kenvandineworth a shot though17:11
cjwatsonsomething is probably not coinstallable - may even be worth running autopkgtest on this locally with qemu-system-ppc64 (which I've never tried but maybe it will work?) to get an environment where you can poke interactively17:12
dobeywell, the difference probably won't be obvious in a diff when you're looking at that, since the dependencies didn't resolve17:12
robrukenvandine: https://requests.ci-train.ubuntu.com/log/1378/finalize/1/info/ Holy hell19:09
kenvandineyeah... what the heck was that?19:10
kenvandineit succeeded though19:10
robrukenvandine: some experimental code to delete dangling bzr tags that don't point at real commits, but I'm also amazed by the sheer number of packages being deleted19:11
kenvandinei think there was many rebuilds19:12
kenvandinethat silo has been around for weeks19:12
kenvandinei'm not all that familiar with it19:12
robrukenvandine: yeah, compounded by trio19:12
kenvandineit took ages to finalize too19:13
kenvandinei guess that was all the deletion of tags?19:13
kenvandinenice to keep it tidy though :)19:13
kenvandine2016-07-19 19:11:15,178 ERROR This ticket is busy. Try again later.19:14
kenvandinerobru, what's up with that?19:14
kenvandinestill shows it as building19:14
robrukenvandine: yeah each tag to delete is a round-trip to the server so quite slow. It parallelizes between packages at least19:14
robrukenvandine: looking at a cached page? There's no evidence that anything has run since the finalize19:16
robruOn that ticket19:16
kenvandinedifferent ticket19:16
robrukenvandine: which one?19:17
kenvandineoh wait19:17
kenvandineyeah, ticket 103719:17
kenvandinelatest log says it failed19:18
kenvandinebut it's also currently building19:18
robrukenvandine: https://requests.ci-train.ubuntu.com/log/1037/ 77 still running when 78 attempted, should work now19:18
kenvandineoh... maybe someone else kicked a rebuild right before me :)19:18
robrukenvandine: actually yours is the one that worked, just a race condition that you were shown the log from renatu 's failed attempt19:20
robruslangasek: not much to say since the meeting yesterday, want to skip?20:29
slangasekrobru: can do20:29
robruslangasek: great, thanks20:29
=== salem_ is now known as _salem
camakorobru, any idea why britney is failing on silo 69? ppc64el arch failure... https://requests.ci-train.ubuntu.com/static/britney/ticket-1693/landing-069-yakkety/excuses.html22:41
robrucamako: I'm not familiar with that error,  no. kenvandine is this the same thing you were seeing earlier? ☝22:44
kenvandinerobru, camako: yes22:45
kenvandineand i'm still clueless22:45
camakokenvandine, thanks..... at least not my fault22:45
kenvandinei think we're down to thinking either powerd, gnome-settings-daemon or unity-control-center is uninstallable22:45
robrukenvandine: weird that it's just one arch?22:46
kenvandinecjwatson suggested i try to run ppc64el autopkgtest locally to poke at it22:46
kenvandinebut i can't get it to build a freaking qemu image for it22:46
kenvandineadt-buildvm-ubuntu-cloud just keeps timing out22:47
kenvandineit downloads the ppc64el image22:47
kenvandineboots it to run cloud-init22:47
kenvandinethen times out22:47
* kenvandine has about had it!22:47
robrukenvandine: camako: I guess just poke QA to override britney and add to the queue?22:47
kenvandinegot feature work with deadlines!22:47
kenvandinenot a great idea...22:47
kenvandineit'll still get stuck in the yakkety proposed migration22:48
kenvandineso it's just moving the problem to later22:48
kenvandineanyway, i'm late... gotta jet22:48
robrukenvandine: night22:48
camakothanks take care22:48
camakosil2100, just FYI... ^^ since you were interested in this silo...22:51
camakoand kgunn ^^22:53

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