=== TheMuso` is now known as TheMuso
=== thumper is now known as thumper-afk
[05:59] <hikiko> hello
[06:15] <didrocks> good morning
[07:57] <pitti> Bonjor tout le monde !
[08:01] <didrocks> rebonjour pitti ;)
[08:09] <Trevinho> Morning
[08:12] <didrocks> hey Trevinho!
[08:13] <Trevinho> didrocks: hey, how is it?
[08:14] <didrocks> Trevinho: I'm great, thanks! Yourself?
[08:15] <seb128> hey desktopers
[08:15] <seb128> hey Trevinho, re didrocks
[08:15] <Trevinho> didrocks: quite good thanks
[08:15] <seb128> Trevinho, managing to get back in business? ;-)
[08:15] <Trevinho> Hi seb128
[08:15] <Trevinho> I already am for two days, but you know... Backlog...
[08:17] <seb128> yeah, he took me the week to feel like I had an handle again on things and a better idea on what to work on next
=== ara is now known as Guest95629
[08:48] <willcooke> morning all
[08:48] <willcooke> evening TheMuso
[08:49] <TheMuso> Hey folks. :)
[08:51] <seb128> hey willcooke TheMuso
[08:51] <willcooke> morning seb128
[08:51] <seb128> how are you?
[08:58] <didrocks> good morning willcooke, hey TheMuso
[09:01] <Laney> yo yo yo
[09:02] <seb128> hey Laney
[09:07] <Laney> hey seb128
[09:07] <Laney> how's it going?
[09:08] <didrocks> hey Laney
[09:08] <seb128> Laney, good! and you?
[09:09] <Laney> I strained my groin at climbing yesterday!
[09:09]  * Laney is walking funny
[09:09] <Laney> hey didrocks!!!
[09:11] <willcooke> g'night TheMuso
[09:11] <TheMuso> Night willcooke, night folks.
[09:12] <willcooke> Laney, seb128 - added you to a snappy store meeting on Monday.  Optional.
[09:13] <willcooke> but figured you might be interested
[09:14] <Laney> hi and bye TheMuso!
[09:14] <Laney> hey willcooke, ok, might poke my snout in
[09:19] <seb128> willcooke, ok, thanks
[09:19] <seb128> Laney, utch :-(
[09:19] <didrocks> pitti: so, large tests works on wily, it seems? (the only issue seems to be an incorrect go-lang download)
[09:20] <pitti> didrocks: oh, they do?
[09:21] <didrocks> pitti: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-wily-ubuntu-desktop-ubuntu-make/wily/amd64/u/ubuntu-make-git/20160113_232648@/log.gz
[09:21] <didrocks> however, it can't download the docker image
[09:21] <didrocks> I wonder if this one isn't using docker.io config file despite the version :p
[09:22] <willcooke> Trevinho, andyrock, hikiko - ahead of the review meeting tomorrow please could you update the trello board as appropriate
[09:24] <willcooke> desktoppers, someone was playing with the trello import script and was getting auth errors.  I think I've fixed that now, so let me know if you need more info
[09:25] <hikiko> willcooke, sure but I'll do it at the end of the day because I might have progress by then
[09:25] <hikiko> (I hope so at least)
[09:25] <willcooke> hikiko, sure thing, thanks
[09:39] <didrocks> pitti: so, I tried another run with a branch where I set /etc/docker/docker.io file for wily, but it seems that it can't pull from it (look at the 2 running instances)
[09:39] <didrocks> pitti: can it be that some workers don't have the same access rules?
[09:40] <pitti> didrocks: where does hte /etc/default/docker.io thing come from?
[09:40] <pitti> debian/docker.io.docker.init does
[09:40] <pitti> ……………………. /etc/default/$BASE
[09:40] <pitti> BASE=$(basename $0)
[09:41] <pitti> which is still /etc/init.d/docker
[09:41] <pitti> didrocks: I'm not convinced that the .io ending there is actually a thing
[09:41] <pitti> that is xenial, but I doubt it's much different in wily
[09:41] <didrocks> pitti: it was on trusty at some point for sure, but newer
[09:41] <didrocks> version seems to use another one
[09:41] <didrocks> as we did major upgrade there…
[09:42] <didrocks> I was just poking out loud, in case this transition hasn't been done there
[09:42] <pitti> didrocks: so, fw access rules aren't really different between releases; it could be that the rules differ between the clouds, but for now I'd blame the wrong file name
[09:42] <didrocks> pitti: hum? which wrong file name
[09:42] <pitti> didrocks: /etc/default/docker.io
[09:42] <didrocks> pitti: hem, it's the same with /etc/default/docker
[09:42] <didrocks> as this was my first attempt
[09:43] <didrocks> pitti: look at the master (and yesterday's run)
[09:43] <didrocks> I changed the file *BECAUSE* (and I only added, not remove the other one) this was failing to give it a try on wily
[09:43] <pitti> right, http://autopkgtest.ubuntu.com/running.shtml#pkg-ubuntu-make-git is clearly a firewall/proxy issue
[09:44] <pitti> $ wget -O- https://index.docker.io/v1/repositories/didrocks/docker-umake-manual/images
[09:44] <pitti> that works (I'm in the current instance)
[09:45] <didrocks> so, we are maybe not sourcing /etc/default/docker there
[09:45] <pitti> and both docker and docker.io default files have the proxy (NB, easier to do a symlink)
[09:45]  * didrocks looks at the systemd jobs
[09:45] <pitti> $ sudo cat /proc/838/environ |xargs -0n1
[09:45] <pitti> -> no proxy
[09:45] <didrocks> EnvironmentFile=-/etc/default/docker
[09:46] <pitti> oh, I was looking at the .init, does it have a .service?
[09:46] <pitti> ah, so it has
[09:46] <pitti> so that's upstart vs. systemd
[09:46] <pitti> ah!
[09:46] <pitti> /etc/default/docker
[09:46] <didrocks> ah, but I bet it's already started
[09:46] <pitti> isn't really a PAM-like EnvironmentFile, perhaps due to that?
[09:46] <didrocks> contrary to the trusty case
[09:47] <didrocks> that or being started…
[09:47] <didrocks> if you are on the instance
[09:47] <didrocks> mind restarting the service?
[09:47] <didrocks> and looking at the env?
[09:47] <pitti> it's more like a PAM one
[09:47] <pitti> restart doesn't help
[09:48] <didrocks> ok
[09:48] <pitti> didrocks: dropping the "export" does help, docker has the proxy now
[09:48] <didrocks> so, I need to special case trusty and the rest
[09:48] <pitti> didrocks: I actually think we shoudl fix docker.service
[09:49] <pitti> if /etc/default/docker is supposed to be a shell script instaed of a PAM-like environment file, then it should not use EnvironmentFile
[09:49] <didrocks> yeah
[09:50] <pitti> ExecStart=/bin/sh -c "[ -r /etc/default/docker ] && . /etc/default/docker; exec /usr/bin/docker -d -H fd:// $DOCKER_OPTS"
[09:50] <pitti> ?
[09:50] <didrocks> sounds good to me, I wonder however the time to sru this…
[09:50] <didrocks> (and it's breaking existing config from admins)
[09:50] <didrocks> if they are using wily
[09:50] <didrocks> and confired it the right way for docker
[09:51] <didrocks> configured*
[09:51] <pitti> I don't think the above change is a regression; it rather fixes a regression
[09:51] <pitti> oh, you mean if they didn't specify "export"
[09:51] <didrocks> yeah
[09:51] <pitti> # If you need Docker to use an HTTP proxy, it can also be specified here.
[09:51] <didrocks> because they stumbled upon the issue in wily
[09:51] <pitti> #export http_proxy="http://127.0.0.1:3128/"
[09:51] <pitti> that's what's tehre by default
[09:51] <didrocks> and "fixed" it
[09:51] <didrocks> then, they get an upgrade
[09:51] <didrocks> which breaks them
[09:51] <pitti> so I had assumed that people would start with "export"
[09:52] <pitti> so, add a set -a above?
[09:52] <pitti> ExecStart=/bin/sh -c "[ -r /etc/default/docker ] && { set -a; . /etc/default/docker; set -a }; exec /usr/bin/docker -d -H fd:// $DOCKER_OPTS"  (syntax untested, might need a little adjustment)
[09:52] <pitti> err, set +a after sourcing
[09:52] <didrocks> you mean set +a?
[09:52] <didrocks> yep
[09:52] <didrocks> (for the second one)
[09:52] <pitti> not that it matters much, the very next thing is an exec; we could just drop it
[09:53] <pitti> didrocks: FWIW, this should just source /etc/environment
[09:53] <pitti> then this would automatically use proxy vars etc., this would be so much less hassle
[09:53] <pitti> and that's a proper EnvironmentFile=
[09:54] <didrocks> pitti: maybe we should check with the cloud team who is in charge of docker?
[09:54]  * didrocks needs "only" to special case in between :/
[09:54] <pitti> didrocks: not sure that we have anyone, but sure
[09:54] <didrocks> pitti: when I touched docker, I got some people pinging me :)
[09:54] <didrocks> so I guess yeah
[09:55] <pitti> didrocks: yeah, so [ -d /run/systemd/system/ ] → "no export"; else "export" ?
[09:55] <didrocks> rbasak IIRC
[09:55] <didrocks> pitti: yep, was writing tihs :)
[09:55] <didrocks> this*
[09:55] <didrocks> then, restart the daemon, which I guess was autostarted
[09:55] <didrocks> on install
[09:55] <pitti> ah, good point (you'd need that for trusty too I suppose?)
[09:56] <didrocks> pitti: no, we don't, and I really wonder why TBH
[09:56] <didrocks> as it's working here as you saw…
[09:56] <pitti> wow, that's a bit of a surprise indeed
[09:56] <didrocks> oh
[09:56] <didrocks> I reboot
[09:56] <didrocks> forget it :)
[09:57] <pitti> ah :)
[10:00] <didrocks> pitti: ok, reran, so the remaining unknown issue is the large tests failing, under $random condition, when other tests are ran first, and this, only when not connected to a tty and only in trusty autopkgtest infra (not on a qemu image)
[10:01] <pitti> didrocks: so that $random thing happens for running a wily or xenial guest too?
[10:01] <pitti> didrocks: or do you mean only a trusty guest?
[10:01] <didrocks> pitti: only a trusty guest, it works on wily
[10:02] <pitti> wow
[10:02] <didrocks> pitti: on xenial, I keep having out of date image issue
[10:02] <didrocks> so, can't say
[10:02] <pitti> didrocks: how do you mean?
[10:02] <pitti> I thought I dist-upgrade the testbed before starting the test
[10:02] <didrocks> pitti: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ubuntu-desktop-ubuntu-make/xenial/amd64/u/ubuntu-make-git/20160113_150906@/log.gz
[10:02] <didrocks> for dep requirements?
[10:03] <pitti> --apt-pocket=proposed
[10:03] <pitti> didrocks: I suppose I shouldn't enable -proposed for --git stuff
[10:03] <didrocks> pitti: yeah, doesn't really make sense I think
[10:03] <pitti> Broken checkbox-gui:amd64 Depends on checkbox-ng-service [ amd64 ] < none -> 0.20.1-1 > ( utils )
[10:03] <pitti>   Considering checkbox-ng-service:amd64 1 as a solution to checkbox-gui:amd64 0
[10:03] <pitti>   Holding Back checkbox-gui:amd64 rather than change checkbox-ng-service:amd64
[10:03] <didrocks> when you enable proposed though, you do apt-get update afterwards, right?
[10:04] <pitti> yes
[10:04] <pitti> and dist-upgrade
[10:04] <didrocks> so it's "just" the checkbox-gui uninstallable issue
[10:05] <seb128> Laney, Trevinho, is there a bug to track webkitgtk2 scrollbar issues?
[10:05] <Laney> dunno
[10:05] <seb128> Laney, do you see corrupted bg/artifact after scrolling as well?
[10:05] <larsu> good morning!
[10:05] <seb128> or just that they don't do the overlay/merge to a thin bar issue?
[10:05] <pitti> didrocks: I locally cowboyed the worker, if you request xenial again it ought to work now; want to try?
[10:05] <seb128> larsu, "morning"
[10:05] <seb128> :-)
[10:06] <seb128> larsu, how was the gym?
[10:06] <larsu> seb128: hehe :) How are you?
[10:06] <pitti> hey larsu!
[10:06] <larsu> seb128: no gym, some errands this morning
[10:06] <seb128> I start feeling better, thanks!
[10:06] <seb128> ah ok
[10:06] <larsu> seb128: nice!
[10:06] <larsu> morgen pitti!
[10:06] <seb128> I though you started to do like didrocks
[10:06] <seb128> exercice every day
[10:06] <larsu> nah
[10:06] <Laney> it doesn't redraw the background or something
[10:06] <Laney> hi larsu!
[10:06] <larsu> that's crazy!
[10:06] <larsu> g'day Laney
[10:06] <seb128> Laney, ok, same than I see then
[10:06] <Laney> look at devhelp
[10:07] <Laney> it has the same thing
[10:07] <seb128> right
[10:07] <Laney> larsu: how's the snow?
[10:08] <didrocks> pitti: done!
[10:08] <didrocks> pitti: TESTS=medium
[10:08] <didrocks> works now on wily, nice!
[10:08] <didrocks> thanks for helping debuggin :)
[10:08] <didrocks> debugging*
[10:08]  * didrocks hugs pitti
[10:09] <pitti> yay
[10:09]  * pitti hugs didrocks back
[10:09] <pitti> crap!
[10:10] <didrocks> pitti: you might want to kill 2 of them btw
[10:10] <pitti> WARNING:root:instance adt-wily-amd64-ubuntu-make-git-20160114-092052 (package ubuntu-make-git) has no associated adt-run; orphaned, deleting
[10:10] <didrocks> (wily TESTS=all)
[10:10] <pitti> didrocks: sorry, my janitor script doesn't recognize these git builds
[10:10] <pitti> didrocks: I'm afraid I just killed your three wily runs
[10:10] <didrocks> no worry :)
[10:11] <didrocks> I'll restart an "all" wily and xenial one, that's ok?
[10:11] <larsu> Laney: no snow. Sunshine and ~10°
[10:11] <seb128> Laney, Trevinho, could be https://bugs.webkit.org/show_bug.cgi?id=145513
[10:11] <ubot5> bugs.webkit.org bug 145513 in WebKit Gtk "Scrollbars render with glitches using GTK themes that do not define a background for them" [Normal,New]
[10:11] <Laney> shucks
[10:11] <Laney> laney@ubuntu.com gets 55 emails
[10:12] <Laney> that's usually a "pitti!" moment
[10:12] <pitti> didrocks: hang on
[10:12] <pitti> Laney: yeah, it's "pitti cowboys a change for didrocks and screws up", sorry
[10:12] <Laney> hehe
[10:13] <pitti> didrocks: ok, go ahead and queue them
[10:13] <pitti> didrocks: http://autopkgtest.ubuntu.com/running.shtml already has one queued for xenial
[10:13] <didrocks> pitti: thanks! yeah, only queued wily now
[10:13] <pitti> they will start once the workers restart
[10:15] <didrocks> hum, the queue didn't update, but that's maybe related to workers waiting
[10:16] <pitti> didrocks: yeah; I do see it in rabbit, though, just not on running.html
[10:17] <didrocks> as long as it's not a rabbit hole :)
[10:17] <pitti> sorry Laney
[10:18] <didrocks> moar emailssssss for Laney
[10:18] <pitti> ok, there we go
[10:18] <didrocks> ah nice, tests racing on wily and xenial :)
[10:18] <didrocks> let's see!
[10:19] <pitti> didrocks: adt-run has no --apt-pocket any more
[10:19] <didrocks> pitti: as xenial is going to be a LTS, I would say if all large tests pass on them, let's give up on trusty large tests…
[10:19] <didrocks> pitti: excellent :)
[10:20] <pitti> didrocks: hm, if that's good enough; I'd still like to know what's going on, though
[10:20] <pitti> didrocks: but if that unblocks you for the time being, so much the better
[10:20] <didrocks> yeah, would be great, but without reproducing directly when sshed into the worker…
[10:20] <didrocks> yeah
[10:20] <Laney> 183!
[10:20] <pitti> ok, promised, next time I'll test this locally before
[10:21] <seb128> Laney,  just flag pitti as a spammer
[10:21] <seb128> ;-)
[10:21] <pitti> Laney: speaking of which... next week (or so) we're going to have a virtual sprint about the autopkgtest infra
[10:21] <pitti> Laney: the idea was that I do one for autopkgtest, barry one for system-image, robru one for ci-train, bdmurray one for errors.u.c.
[10:22] <pitti> for learning from each other and increase the bus factor
[10:22] <pitti> in case you (or anyone here, really!) want to join the presentation or some hack session
[10:22] <Laney> interesting
[10:22] <Laney> do you have a schedule or something?
[10:23] <pitti> Laney: not yet, so far it just came up as an idea in the 1-on-1 with slangasek yesterday evening
[10:23] <pitti> we'll probably have some more info after today's team meeting
[10:23] <pitti> Laney: but probably I'll do the talk next Tuesday late afternoon
[10:24] <Laney> pitti: alright, I'll keep an eye out
[10:24] <Laney> it would be good to work on email notifications at some point
[10:25] <pitti> *nod*
[10:28] <pitti> didrocks: that's without recommends now, is it?
[10:37] <didrocks> pitti: it is, yeah
[10:37] <didrocks> (without)
[11:06] <andyrock> morning
[11:09] <seb128> andyrock, "morning" ;-)
[11:09] <didrocks> hey andyrock
[11:17] <didrocks> pitti: I looked at the golang failure (as it seems it was the only failure), and as the medium test pass, but not the large ones, it means it's the 3rd party breaking me, looking :p
[11:17] <didrocks> and go 1.5.3 has been released 14h ago, suspicious…
[11:19] <didrocks> ah, they did change from sha1 to sha256, the test telling that checksum isn't good is right!
[11:19]  * didrocks fixes and adapt medium tests
[11:21] <didrocks> fixed in master, need a quick release now
[11:21] <didrocks> (yeah tests \o/)
[11:24]  * pitti ^5s didrocks
[11:37] <didrocks> pitti: hum, the xenial request (the one made at the same time than wily) disappeared? I don't find it on running nor on https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ubuntu-desktop-ubuntu-make?format=plain
[11:40] <Laney> attente: it is uploaded, waiting in the new queue now
[11:42] <pitti> didrocks: ah, found the log; it failed with a "testbed failure", and already retried twice
[11:42] <pitti> didrocks: third retry has restarted a minute ago
[11:42] <pitti> didrocks: after that fails as well, I'll get a log
=== hikiko is now known as hikiko|ln
[11:50] <willcooke> Laney, found the new URL and updated the bug
[11:50] <willcooke> I think we need a new bug for the legal text because it will need to go to legal for approval
[11:51] <willcooke> Could you give me a link to the file with the full text in LP?
[11:51] <Laney> thx
[11:51] <Laney> why a new one though, can't they use the same?
[11:51] <didrocks> pitti: thx!
=== alan_g is now known as alan_g|afk
[11:51] <Laney> https://bazaar.launchpad.net/~unity-control-center-team/unity-control-center/trunk/view/head:/panels/info/searchingthedashlegalnotice.html
[11:52] <Laney> WTF at whoever put it all one one line
[11:52] <willcooke> urg
[11:53] <Laney> it's okay, they can use the URL I gave which is installed on every Ubuntu system these days
[11:53]  * Laney sniggers and runs off
[11:55] <davmor2> willcooke: what's the plan with regard online accounts for the calendar app currently I can't add any calendars if I click on the google button, also there seems to be some icons missing from the that page
[11:56] <Laney> I attached it anyway
[11:56] <Laney> no need to ping our manager about bugs thanks, we'll fix them
[11:58] <Laney> that bit isn't integrated with ubuntu online accounts yet
[12:03] <willcooke> Laney, I've sent an amended text over to legal, will add to that bug when I get it back again...
[12:03] <Laney> you rule, yay!
[12:03] <pitti> WARNING:root:instance adt-xenial-amd64-ubuntu-make-git-20160114-101739 (package ubuntu-make-git) has no associated adt-run; orphaned, deleting
[12:03] <pitti> WARNING:root:instance adt-wily-amd64-ubuntu-make-git-20160114-101739 (package ubuntu-make-git) has no associated adt-run; orphaned, deleting
[12:03] <pitti> WAH WAH!
[12:03] <pitti> didrocks: I'm so sorry for this; I'll fix this right now
[12:04] <pitti> oops, the 6-hourly maintenance cron job did it again
[12:08] <didrocks> :)
[12:08] <didrocks> no worry!
[12:10] <pitti> ok, I think I fixed it, and commented out the instance.delete(), so that I'll just see what's going on
[12:10] <didrocks> oki :)
[12:13] <pitti> didrocks: ack, please re-queue
[12:17] <didrocks> done
[12:17] <pitti> didrocks: I see xenial, not wily yet?
[12:21] <didrocks> pitti: wasn't that xenial? wily was running happily
[12:21] <pitti> didrocks: ah, if wily succeeded already, nevermind; the above run killed a running wily instance too
[12:21] <didrocks> oh :(
[12:21] <didrocks> this was closed if not finished
[12:21]  * didrocks looks if it finished
[12:22] <didrocks> ..............................................E..........adt-run [12:11:14]: ERROR: Received signal 15, cleaning up...
[12:22] <didrocks> it has been killed
[12:22] <pitti> yes, and it had one error
[12:22] <didrocks> just had something like 5 tests to finish first :/
[12:22] <pitti> perhaps the one that you fixed an hour ago
[12:22] <didrocks> I guess the error was go
[12:22] <didrocks> hoping so
[12:23]  * didrocks reruns all the tests once more then
[12:23] <didrocks> (testing a contributor's branch meanwhile)
[12:23] <didrocks> queued
=== hikiko|ln is now known as hikiko
[12:43] <hikiko> Trevinho,
[12:43] <hikiko> here?
[12:43] <Trevinho> hi hikiko
[12:43] <hikiko> hi :)
[12:43] <hikiko> I have a question
[12:43] <hikiko> I noticed that the unity windows
[12:44] <hikiko> are continuously redrawn
[12:44] <hikiko> is this intentional?
[12:45] <hikiko> I think they shouldn't
[12:56] <didrocks> pitti: sorry to be a PITA, but it seems the xenial request disappeared again (the "all" one)
[12:56] <didrocks> ah, it restarted, so I guess a testbed failure?
[12:57] <didrocks> ("running for" still increments?)
[13:00] <xnox> there is also a 5-minute sync gap between completion and being able to see the results via e.g. packages report.
[13:12] <didrocks> xnox: yeah, not the case here as it's a ppa run, and there is no visualisation, just rough data
[13:22] <pitti> didrocks: right, it will tmpfail 3 times, then it'll give up and give me a log
[13:23] <xnox> didrocks, wow you are hipster =)
[13:23] <didrocks> xnox: isn't it? And you haven't seen my tests wrapper handling local, vm or remote tests :p
[13:24] <pitti> xnox: no, that 5 min gap just applies to autopkgtest.u.c., but didrocks doesn't use that
[13:25] <pitti> results appear on swift as soon as the test finishes
[13:25] <willcooke> Design work for the Xerus animal is scheduled!  Should be delivered a week before Beta 1
[13:25] <Laney> does that include the default wallpaper?
[13:26] <Laney> if so, swwwwwweeeeettttttttttttt
[13:27] <willcooke> Laney, should be.  Will confirm
[13:27]  * willcooke lunches 
[13:27] <Laney> bacon sandwich?
[13:27]  * Laney saved some last night for one of those
[13:27] <willcooke> no such luck.  I've got, surprise surprise, some turkey to eat up :)
[13:33] <didrocks> seb128: FYI, I still had some comments on the new packages from the student, I've asked him to fix those before pushing to the archive
[13:33] <didrocks> then, I sponsor, you NEW, I MIR, and changing the seed :p
[13:33] <seb128> didrocks, ok, no hurry from my part, I've enough to do to not be bored ;-)
[13:33] <seb128> wfm!
[13:33] <didrocks> ;)
[14:02] <andyrock> willcooke: the meeting is at 10:30 utc right?
[14:02] <andyrock> maybe I'll be there half an hour later
[14:03] <andyrock> I've an exam
[14:03] <andyrock> pretty sure I'm not going to use the all four hours
[14:03] <andyrock> just in case
[14:03] <andyrock> ten minutes later not half an hour ;
[14:03] <andyrock> ;)
[14:07] <willcooke> andyrock, yeah, correct time.  No worries
[14:24] <didrocks> pitti: ok, all wily tests pass. xenial still mysteriously fails at the very end, after running all tests (or most, I saw it printing large one?). Maybe let's see if after one more automatic retry, it dumps stuff
[14:52] <Sweet5hark> did you already tweak your ssh_config today? http://www.mail-archive.com/misc@openbsd.org/msg144351.html (note ssh, not sshd -- thus client)
[14:53] <mdeslaur> Sweet5hark: alternatively, wait to install our updates in two hours
[14:53] <willcooke> oh boy
[14:53] <willcooke> ha, nice!  thanks mdeslaur
[14:54] <Sweet5hark> mdeslaur: thx! from the waves this makes already it sounds like you guys had to put in quite a few extra hours ...
[14:56] <mdeslaur> just had to make sure updates were ready
[14:58] <Sweet5hark> mdeslaur: thanks anyway, you guys rock. ;)
[15:01] <pitti> didrocks: http://autopkgtest.ubuntu.com/running.shtml#pkg-ubuntu-make-git is getting connection timeouts again
[15:02] <pitti> didrocks: well, that, or "Unable to find image 'didrocks/docker-umake-manual:latest' locally
[15:02] <pitti> means something else
[15:13] <pitti> didrocks: hmm @ http://paste.ubuntu.com/14496457/
[15:14] <pitti> didrocks: oh, nevermind, that was just my ssh to prodstack; seems I just have some networking troubles
[15:14] <pitti> incidentally canonistack also stopped working
[15:16] <pitti> didrocks: ok, it's still runnning, network is bck
[15:19] <willcooke> Laney, confirming - yes will include wallpaper
[15:20] <Laney> w00t
[15:27] <seb128> nice!
[15:42] <pitti> didrocks: here we are: http://paste.ubuntu.com/14496639/
[15:42] <pitti> didrocks: (medium passed, FTR)
[15:43] <pitti> didrocks: I'll fix the tmpfail ("stdout: no such file")
[15:44] <pitti> didrocks: so it sounds like some test got previously run as root, and then as user?
[15:44] <pitti> didrocks: the differenve between wily and xenial is obviously python 3.5
[16:17] <seb128> andyrock, is https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1156566 something you were working on?
[16:17] <ubot5> Launchpad bug 1156566 in indicator-session (Ubuntu) ""Restart" is missing from the system menu" [Medium,Triaged]
[16:18] <seb128> it's about having separate dbus calls/dialogs for shutdown/restart
[16:18] <andyrock> mmm yeah I've the branch here
[16:18] <andyrock> 99% completed
[16:18] <qengho> Hi hi. May I have a sponsor for grub to probe zfs filesystems better? https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727
[16:18] <ubot5> Launchpad bug 1527727 in grub2 (Ubuntu) "grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/..." [Medium,Confirmed]
[16:19] <andyrock> I'll try to complete it
[16:19] <andyrock> seb128: ^^^
[16:19] <andyrock> sorry about that
[16:19] <seb128> andyrock, no worry, just found the bug while triaging, maybe assign it to yourself if you work on it?
[16:19] <seb128> or mark it as duplicate if you already have one
[16:19] <andyrock> yup assign it to me
[16:19] <andyrock> link?
[16:25] <seb128> andyrock, I pinged you with the url? or what do you mean?
[16:25] <didrocks> pitti: yeah, some as running and root, and some aren't, however, I can't reproduce in qemu that particular issue, so doesn't seem to be 3.5 (
[16:25] <andyrock> ops sorry
[16:25] <seb128> :-)
[16:25] <didrocks> pitti: I wonder if that's just a snaffu, if I should try to get everything pre-compiled to avoid this or…
[16:25] <andyrock> working at -15°C
[16:25] <andyrock> not my fault :P
[16:30] <seb128> andyrock, somewhat your fault, you decided to go study there ;-)
[16:53]  * didrocks waves good evening and good night, going to a docker meetup tonight!
[16:54] <Laney> bye didrocks!
[16:54] <Laney> dock away!
[16:55] <didrocks> see you Laney! I will cloudify myself even! ;)
[16:55] <Laney> come and snow on me
[17:28] <Sweet5hark> sooo, when do we get opteron a1100s as ARM builders?
[17:30] <Sweet5hark> 8 a57 cores@2GHz, 4x1MB L2 cache, 8MB L3 cache sounds sweet.
[18:08] <willcooke> night all
[18:42] <Laney> bye!
[19:03] <seb128> Laney, night!
[21:38] <popey> Sweet5hark, yo, when you're around, we should talk about maybe a LO update for docviewer :)