[05:41] <dobey> anyone have any ideas as to why intel driver might cause X BadMatch/BadPixmap crashes, but only in Nautilus?
[06:25] <larsu> good morning!
[06:46] <pitti> Good morning
[06:51] <larsu> morgen pitti!
[06:52] <pitti> hey larsu, how are you?
[06:52] <seb128> good morning desktopers
[06:52] <seb128> hey larsu pitti
[06:52] <pitti> bonjour seb128 !
[06:52] <larsu> pitti: good thanks! How are you?
[06:58] <pitti> larsu: gut, danke!
[07:03] <didrocks> good morning
[07:04] <seb128> hey didrocks ;-)
[07:04] <larsu> hi didrocks!
[07:04] <didrocks> hey larsu!
[07:04] <didrocks> re seb128
[08:33] <seb128> dobey, thanks for transitioning software-center to CI landing and merges the ubuntu changes back to the upstream vcs
[08:35] <dobey> seb128: sure. was glad to finally get that done yesterday :)
[08:37] <seb128> :-)
[08:45]  * seb128 starts wondering if upgrading nautilus was good idea
[08:46] <didrocks> seb128: for the icon size or something else?
[08:47] <didrocks> I still find the move action to be confusing btw (especially if you move files to a network share)
[08:47] <seb128> quite some of the changes feel like regressions
[08:47] <seb128> upstream is reverting some of those in 3.20 so they seem to agree
[08:47] <seb128> like they dropped the context menu to delete and are restoring it
[08:47] <seb128> same for the one to create symlinks
[08:48] <seb128> the "in toolbar" copy dialog is less obvious
[08:48] <seb128> the icons are too big
[08:48] <seb128> the menubar patch is way more work that I was expecting
[08:48] <didrocks> the copy icon is clearly not obvious
[08:48] <seb128> like larsu has been on it for almost a month, I think we could have worked on more useful things
[08:48] <seb128> they change in trunk to open the popup copy dialog automatically
[08:48] <didrocks> even after knowing where it is, I do the action and always have this 0.5s "did I really start copying/moving?"
[08:49] <seb128> to workaround a bit the fact that it's not obvious
[08:49] <seb128> I'm going to backport that and see how it feels
[08:49] <didrocks> yeah, that one (and icon size) are the most obvious issues to me
[08:49] <seb128> but yeah, the icons size and the copy UI are the ones that concerns me most atm
[08:49] <didrocks> I even didn't notice about the delete removal
[08:50] <didrocks> but I either use del or command line
[08:50] <seb128> same here
[08:50] <didrocks> so not a good example :)
[08:50] <seb128> same for symlinks
[08:50] <seb128> I never use those
[08:50] <seb128> or at least not in nautilus
[08:50] <didrocks> yeah, I wonder if people use this
[08:50] <seb128> they are more "tech" work to me
[08:50] <didrocks> yep
[08:50] <seb128> and I use nautilus to manage my datas a bit
[08:50] <seb128> like move photos around
[08:51] <seb128> or clean up my downloads folder
[08:51] <didrocks> yeah, I wonder about the delete in context menu
[08:51] <didrocks> I never see "regular users" using the context menu
[08:51] <dobey> i just want my nautilus to not crash arbitrarily
[08:51] <seb128> dobey, does it do that in xenial for you?
[08:52] <dobey> seb128: haven't tried xenial. it does in trusty, i think because of intel drivers. i sometimes get BadPixmap crashes in it :(
[08:54] <seb128> :-(
[08:54] <seb128> I'm not aware of that one
[09:00] <willcooke> morning desktoppers
[09:00] <willcooke> seb128, how did the CC catch up go?  All ok?
[09:01] <dobey>          buf = "BadDrawable (invalid Pixmap or Window parameter)", '\000' <repeats 15 times>
[09:01] <dobey> :(
[09:02] <seb128> dobey, :-/
[09:02] <didrocks> good morning willcooke
[09:02] <seb128> willcooke, hey, it went very well, thanks
[09:02] <seb128> willcooke, didrocks and Laney joined
[09:02] <seb128> didrocks gave some updates on the online dash status and the code in
[09:02] <seb128> and Laney discussed a bit gnome-software
[09:02] <willcooke> super, thanks seb128, didrocks Laney
[09:03] <willcooke> I will go find the logs actually...
[09:03] <seb128> otherwise they seemed happy to know that we have active contributors on GNOME and other things and not much frictions
[09:03] <seb128> k
[09:03] <didrocks> yw
[09:03] <dobey> i don't know where the crash reports are going though :(
[09:03] <Laney> yo
[09:03] <didrocks> hey Laney
[09:03] <Laney> happy first friday!
[09:04] <dobey> hmm, nautilus package has 1800 open bugs :(
[09:06] <larsu> Laney: happy end of first week!
[09:06] <dobey> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1071155 is similar anyway
[09:07] <seb128> hey Laney, happy friday!
[09:07] <dobey> hrmm, 9 open bugs in nautilus for sig 5 in _XReply()
[09:07] <dobey> and 5 of them have bug heat > 160
[09:07] <dobey> other 4 are at 10
[09:08] <seb128> I think the issue is that not many people know how to deal with those bugs
[09:08] <seb128> they don't feel like gtk/gnome issues
[09:08] <dobey> they are a bit of a pain to debug, yeah
[09:09] <dobey> really needs someone who knows X well enough, to poke at them
[09:10] <dobey> not sure who's working on X for us any more though
[09:11] <seb128> not many people, that's part of the issue
[09:11] <seb128> tjaalton is but I don't think he has enough free slots to look at those
[09:11] <willcooke> what seb128 said
[09:13] <dobey> :(
[09:14] <tjaalton> dobey: happens only on intel? install the xenial driver, works fine in wily
[09:15] <davmor2> willcooke: the phone has a phone icon now when you connect it oh pretty :D
[09:16] <dobey> tjaalton: i'm running the wily kernel already. also it works fine on my intel laptop. it only crashes on my workstation
[09:16] <tjaalton> dobey: no, intel X driver
[09:16] <tjaalton> or try forcing uxa in xorg.conf
[09:17] <tjaalton> what generations are those?
[09:17] <hikiko> hi
[09:17] <dobey> when's the wily xorg going to end up in trusty for HWE?
[09:17] <tjaalton> once libdrm is past NEW
[09:17] <dobey> workstation is haswell
[09:17] <tjaalton> is when the rest is getting pushed
[09:18] <dobey> not sure on the laptop, i think also haswell
[09:18] <dobey> maybe ivybridbge
[09:18] <tjaalton> ok
[09:18] <tjaalton> my desktop is ivybridge, no issues there
[09:18] <tjaalton> on wily
[09:19] <dobey> i don't recall if it was crashing for me when i had ivybridge in my workstation
[09:19] <willcooke> davmor2, nice!!
[09:19] <tjaalton> what's the resolution on workstation?
[09:19] <dobey> 4k
[09:20] <tjaalton> that could be it
[09:20] <dobey> i had an nvidia card in for a week, and nautilus didn't crash on it
[09:20] <dobey> but had enough other problems with that, that i just returned it
[09:21] <tjaalton> so try forcing uxa, or pull the X driver from xenial
[09:22] <seb128> Laney, is there anything keeping gnome-calendar in main? it doesn't seem to be on the current iso yet?
[09:22] <seb128> I guess it's on your todolist?
[09:24] <Laney> I seeded it
[09:24] <Laney> so the Task presumably
[09:25] <seb128> k
[09:26]  * Laney runs ./update
[09:27] <Laney> you can't do that until after the promotion
[09:27] <Laney> so easy to lose it if there is a gap
[09:27] <seb128> that's a bit backward
[09:27] <seb128> because usually we do the promotion once something tries to pull the binary in
[09:27] <Laney> seed -> component mismatch -> promote -> ./update
[09:28] <seb128> but oh well, it's minor
[09:28] <seb128> k
[10:02] <seb128> mitya57, hey, thanks for updating nautilus in decembre, you didn't use the packaging vcs though? (there was commit/not released work that you seem to not have included and your version is not in there) or did you just forgot to push?
[10:06] <seb128> larsu, I'm working on a nautilus update, how is the menubar change coming? can I give it a test build even if it's not ready it to be proposed? just to see how it's working
[10:10] <larsu> seb128: I'm done with the action rewiring and am writing xml right now
[10:10] <seb128> k
[10:10] <larsu> you'll need a gtk patch too
[10:10] <larsu> let me open a bug for that one first
[10:10] <seb128> danke
[10:10] <seb128> is that something upstream is likely to agree on?
[10:10] <seb128> or an ubuntu hack?
[10:10] <larsu> upstream
[10:11] <larsu> well, depends on desrt ;)
[10:11] <seb128> k
[10:13] <desrt> hi
[10:13] <Laney> hi desrt!!!
[10:13] <willcooke> morning desrt
[10:14] <desrt> Laney!
[10:14] <larsu> morning desrt :)
[10:14] <desrt> willcooke: g'morn
[10:14] <desrt> hihi larsu
[10:14] <desrt> and hello didrocks and seb128 :)
[10:14] <seb128> hey desrt
[10:15] <didrocks> good morning desrt
[10:15] <larsu> desrt: since you're here - care to look at https://bugzilla.gnome.org/show_bug.cgi?id=760312 ?
[10:16] <seb128> bah
[10:16] <larsu> seb128: that's the patch I was talking about ^
[10:16] <seb128> bzr bd-do doesn't like lp:~ubuntu-desktop/nautilus/ubuntu it seems
[10:16] <seb128> UnicodeEncodeError
[10:16] <seb128> grrrr at python
[10:16] <seb128> larsu, thanks
[10:16] <didrocks> the usual :)
[10:17] <desrt> larsu: 'hi' was a subtle way of saying "i hope i get a bug link" :)
[10:17] <larsu> desrt: oh. I read it as "hi"
[10:17] <pitti> hey desrt, how are you? (and where?)
[10:19] <desrt> larsu: and yet i got my bug link =)
[10:19] <larsu> desrt: totally unrelated :P
[10:19] <desrt> pitti: good morning :D
[10:19] <desrt> pitti: i am before coffee, so i have difficulty answering "how are you" :)
[10:20] <desrt> and i am in toronto, where it is still very dark indeed
[10:20] <Laney> isn't it 05:20?
[10:21] <desrt> that is correct.
[10:21]  * Laney screams
[10:21] <desrt> larsu: are you sure this patch correctly handles the remoteactiongroup/platform_data stuff?
[10:22] <larsu> desrt: why would that have anything to do with it?
[10:22] <desrt> because GtkApplicationWindow doesn't wire that through, iirc
[10:22] <desrt> i'll do the review in the bug...
[10:22] <larsu> ugh, are you sure?
[10:23] <desrt> fairly sure, yes.
[10:25]  * desrt hopes that 5am pre-coffee reviewing doesn't come back to bite her
[10:26] <larsu> desrt: UNITY!
[10:26] <larsu> (thanks for the review)
[10:26] <desrt> "needs word" is certainly less dangerous than "accepted-commit_now"
[10:29] <larsu> heh
[10:29] <larsu> desrt: the gist: I want to export additional actions from inside a subclass of GtkApplicationWindow
[10:30] <desrt> amusing story of the day: (due to various online posts drawing equivalences between them) google translate is now confusing "russian federation" with "mordor", "russians" with "occupiers" and "sergey lavrov" with "sad little horse"
[10:30] <desrt> larsu: why can't the subclass simply add the actions like everyone else does?
[10:32] <larsu> desrt: that sounds horribly inefficient...
[10:32] <desrt> what kind of actions are we talking here, and how many?
[10:32] <larsu> but I'd rather do that than deal with the platform data mess
[10:32] <larsu> desrt: normal amount, nothing fancy
[10:33] <desrt> use action entries?
[10:33] <desrt> reimplementing the actiongroup infra is annoying and awkward and you're probably going to get it wrong
[10:33] <desrt> (for reasons like platform_data...)
[10:39] <larsu> desrt: hm? The actions already exist
[10:39] <larsu> in some widget deeper down
[10:39] <larsu> I don't like that reimplementing the interface doesn't work
[10:40] <larsu> seems like something that totally should work
[10:41] <desrt> we could possibly detect if you also reimplement RemoteActionGroup for yourself...
[10:41] <desrt> or we could implement it directly on the window itself, as well
[10:41] <desrt> that almost makes sense, in fact
[10:41] <larsu> yeah.... clearly
[10:42]  * larsu shall not shave this yak now though to not make seb128 more impatient ;)
[10:42] <larsu> desrt: thanks for catching this anyway
[10:42] <desrt> if you want to do the remoteactiongroup impl on the window itself and do a patch for that, i'd be happy to look at it... provided you give a better answer on the "why can't you just use actions" question
[10:43] <desrt> because i agree that it would be theoretically nicer
[10:43] <desrt> same argument could be made for GApplication itself
[10:43] <larsu> why didn't you do it this way in the first place i wonder?
[10:44] <desrt> it used to be possible to provide your own action group
[10:44] <desrt> maybe still is, although very much deprecated, and for a long time
[10:44] <desrt> it was the early days before we figured out what was really a good pattern here
[10:44] <larsu> ah, right
[10:44] <desrt> and before GActionMap existed
[11:02] <andyrock> morning all
[11:05] <willcooke> hey andyrock
[11:19] <hikiko> Trevinho|OFF,
[11:19] <hikiko> andyrock,
[11:19] <hikiko> I have a question
[11:20] <andyrock> yup
[11:20] <hikiko> without any of my code
[11:20] <hikiko> the old shadows update all the time
[11:20] <hikiko> it's like a busy loop
[11:21] <hikiko> do you know that it was intentional or there's something that marks regions as dirty etc?
[11:21] <hikiko> i mean
[11:21] <hikiko> that shouldn't happen anyway
[11:21] <andyrock> i don't think it's intentional
[11:21] <hikiko> but do you know why it happens?
[11:21] <andyrock> maybe it's a workaround for something
[11:22] <andyrock> to be honest nope
[11:22] <hikiko> mmm then I have to fix this first, otherwise unity will calculate the shape (and perform convolution) at almost every frame with the new shadows...
[12:05] <hikiko> andyrock, Trevinho|OFF ignore :) it was a program I left open that was causing the frequent updates!
[12:19] <didrocks> pitti: probably a very stupid question, but how can I trigger an autopkgtests using the test request format?
[12:21] <pitti> didrocks: ah, ATM you can't, I'm afraid; firewall limits that to snakefruit (or do you have access there?)
[12:21] <didrocks> pitti: I do have access here, ~ubuntu-archive
[12:21] <pitti> didrocks: ah
[12:21] <didrocks> but I don't see anything handy in run-autopkgtest --help
[12:21] <pitti> didrocks: now, I didn't yet expose those in run-autopkgtest
[12:21] <didrocks> ah, I'm not that crazy :)
[12:22] <pitti> amqp-publish -u amqp://autopkgtest-worker:SECRET@10.25.180.81 -r  debci-trusty-amd64 -b 'ubuntu-make-master {"test-git": "https://github.com/ubuntu/ubuntu-make.git", "ppas": ["ubuntu-desktop/ubuntu-make-builddeps", "ubuntu-desktop/ubuntu-make"]}'
[12:22] <pitti> didrocks: that's what I used for testing back then
[12:22] <pitti> didrocks: shoudl be straightforward to add it to run-autopkgtest, similar to --ppa
[12:23] <didrocks> SECRET will be replaced by the right thing in amqp-publish?
[12:23] <pitti> didrocks: if you want to have a go at it, please do; otherwise I'll try to do that on Monday
[12:23] <pitti> didrocks: no, I just edited it out for pasting into public IRC :)
[12:23] <didrocks> pitti: well, I can have a look, but let me ensure it can runs properly first :)
[12:23] <didrocks> ok ;)
[12:23] <didrocks> run*
[12:23] <didrocks> pitti: also, that I can play with the env variables and such, let's see
[12:24] <didrocks> between that and https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Test_request_format, should be workable :)
[12:24] <pitti> didrocks: for experiments it would be good if you could skip armhf for now, as that's horribly swamped
[12:24] <pitti> didrocks: go nuts on x86, they have plenty of capacity
[12:24] <pitti> . o O { me is *sooo* happy to be able to say that now, since Tuesday ☺ }
[12:25] <didrocks> haha! ok :) I just need one arch anyway for testing this
[12:29]  * didrocks looks fot amqp-publish
[12:29] <didrocks> for*
[12:31] <didrocks> pitti: amqp-tools isn't installed on snakefruit, though?
[13:18] <pitti> didrocks: no, it's not; I ran that from my adt control instance
[13:18] <pitti> didrocks: I can run stuff for you if you wwant
[13:18] <didrocks> pitti: well, it was easier for me to implement the options, I did this :p
[13:19] <didrocks> I saw the job running in the web ui, but then, it seems to fail
[13:19] <pitti> didrocks: ah, just got a worker failure mail
[13:19] <didrocks> the issue is that I can't find the logs back
[13:19] <pitti> W: Failed to fetch http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make-builddeps/ubuntu/dists/xenial/main/source/Sources  404  Not
[13:19] <pitti> +Found
[13:19] <pitti> didrocks: right, sorry; this counts as a "tmpfail", i. e. it thinks that this is a temporary glitch
[13:19] <didrocks> yeah, I think if test-git or test-bzr are provided, we shouldn't force a ppa or trigger
[13:19] <pitti> didrocks: so it retries instead of posting the log
[13:20] <pitti> didrocks: you don't need a trigger, but you need a PPA
[13:20] <didrocks> no, it's a real failure, I don't have anything in the ppa for the current devel serie
[13:20] <pitti> let's please not clutter the ubuntu result container for these
[13:20] <didrocks> so the archive doesn't exit
[13:20] <didrocks> exist*
[13:20] <pitti> ah, makes sense
[13:20] <didrocks> hum, should I do a dummy upload in the ppa then?
[13:21] <pitti> didrocks: usual workaround is to copy (or upload) a package into it and delete it again
[13:21] <didrocks> yeah
[13:21] <pitti> didrocks: upload, or copy-package with binaries
[13:21] <didrocks> can do this
[13:21] <didrocks> anyway, I tried on trusty then
[13:21] <didrocks> with the ppas
[13:21] <didrocks> and same, seems to have failed quite quickly
[13:21] <didrocks> (the 2 archives exists here)
[13:21] <didrocks> but I don't see anything in the ui
[13:21] <pitti> adt-run [13:19:34]: @@@@@@@@@@@@@@@@@@@@ apt-source ubuntu-make-master
[13:21] <pitti> E: Unable to find a source package for ubuntu-make-master
[13:22] <didrocks> making sense :)
[13:22] <pitti> this looks like this didn't get the git argument
[13:22] <didrocks> but the doc says it won't try to use the "pkg" as a "pkg"
[13:22] <didrocks> ah
[13:22]  * didrocks check for typos
[13:22]  * pitti looks at the full log
[13:24] <pitti> Received request for package ubuntu-make-master on trusty/amd64; params: {u'ppas': [u'ubuntu-d
[13:24] <pitti> esktop/ubuntu-make-builddeps', u'ubuntu-desktop/ubuntu-make'], u'test_git': u'https://github.com/ubuntu/ubuntu-make.git'}
[13:24] <pitti> didrocks: s/test_git/test-git/
[13:24] <pitti> did I typo that on the wiki?
[13:24] <didrocks> I guess you did
[13:25] <pitti> no, it's ok there
[13:25] <didrocks> waow
[13:25] <didrocks> I can't read
[13:25] <didrocks> indeed, I reopened the page and it's there
[13:25] <pitti> well, to be fair these pretty well look the same :)
[13:25]  * pitti hugs didrocks
[13:26]  * didrocks hugs pitti back
[13:26] <didrocks> ok, so running on trusty
[13:26] <didrocks> let's see
[13:27] <pitti> didrocks: I killed all adt-runs for u-make for now, to break the infinite retry loop
[13:27] <pitti> seems for this kind of operation this needs to become more clever
[13:30] <didrocks> urgh, sorry for the retry loop on this then :)
[13:30] <didrocks> did you kill last one?
[13:30]  * didrocks looks
[13:30] <didrocks> no, so looking at http://autopkgtest.ubuntu.com/running.shtml#pkg-ubuntu-make-master :)
[13:31] <pitti> didrocks: no need to be sorry; it's  my ongoing quest for minimizing human activity in a system where everything can (and does) fail all the time
[13:31] <pitti> didrocks: killed that too
[13:31] <didrocks> pitti: oh?
[13:31] <didrocks> that one wasn't with the correct parameters?
[13:31] <didrocks> (my last retry after the fix)
[13:32] <pitti> didrocks: oh sorry, I thought you said "this one is also old"
[13:32] <pitti> didrocks: as it already ran for 11 mins
[13:32] <didrocks> pitti: well, it's installing ubuntu-desktop! :p
[13:32]  * didrocks reruns
[13:32] <pitti> ok, running again
[13:33] <didrocks> pitti: so, then, I should see it stored in http://autopkgtest.ubuntu.com/packages/, right?
[13:33] <didrocks> (after the first run)
[13:33] <pitti> http://paste.ubuntu.com/14437805/ .. totally trivial command line, eh!
[13:33] <pitti> didrocks: no, there's no web UI frontend for PPAs right now
[13:34] <didrocks> pitti: ahah, and that's without the --env parameter still! :p
[13:34] <pitti> didrocks: if you run it against the ubuntu archive, it'll appear there, but not for PPAs; so far we haven't needed one,  but we could set up something
[13:34] <didrocks> ok
[13:34] <pitti> didrocks: no problem -- just start another one with env and let them run in parallel
[13:34] <didrocks> pitti: oh right, the *cloud*
[13:34]  * didrocks tries
[13:35] <didrocks> (done)
[13:35] <didrocks> this one should only run a pep8 test
[13:35] <pitti> didrocks: it's fine if you run 10 in parallel occasionally; if you need much more, and it starts blocking things, we need to ask for moar powah
[13:36] <didrocks> indeed, it will still takes time though until we have real ubuntu-desktop images
[13:36] <didrocks> pitti: I don't remember, the ppas artefacts archive in swift will be per ppa per release, right?
[13:37] <didrocks> (so we can remove the vivid one at some point, right?)
[13:37] <pitti> didrocks: correct
[13:37] <didrocks> sounds good :)
[13:37] <pitti> didrocks: oh, you don't have "ubuntu-desktop" in d/t/control Depends:, but call apt-get yourself?
[13:37] <pitti> didrocks: do you call it with $(which eatmydata 2>/dev/null) apt-get ?
[13:38] <pitti> didrocks: if not, it'll be awfully slow (test Depends: do that automatically)
[13:38] <didrocks> pitti: ah, I don't, I guess I should. There was a reason I minimize the deps in d/t/control (that was before the holidays…)
[13:38] <didrocks> pitti: ok, adding eatmydata
[13:38] <didrocks> ah yeah, the lines with test deps was getting really long
[13:38] <didrocks> and I have this "setup" tests
[13:38] <pitti> didrocks: testbeds have that magic dpkg force-unsafe-io flag in the config, but it doesn't seem to be nearly as fast as eatmydata
[13:39] <didrocks> and I need to have all them listing the same deps, to reuse the same test bed
[13:39] <didrocks> that's why I put the dep setup logic in setup (in addition to the other setup parts)
[13:39] <pitti> WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.
[13:39] <pitti> 0 upgraded, 1254 newly installed, 0 to remove and 0 not upgraded.
[13:39] <pitti> Need to get 534 MB of archives.
[13:39] <didrocks> yeah, I'm using simple apt, which is fine in trusty and xenial
[13:39] <pitti> After this operation, 2015 MB of additional disk space will be used.
[13:39] <pitti> pas mal :)
[13:39] <didrocks> ahah :)
[13:40] <didrocks> if you want to kill those 2 runs because they will be slow due to no eatmydata, please feel free
[13:40] <pitti> didrocks: I don't care
[13:40] <didrocks> I'm adding that to master meanwhile
[13:40] <didrocks> ok :)
[13:40] <pitti> let's just let it finish
[13:40] <pitti> didrocks: queues are empty right now anyway (except arm)
[13:40] <didrocks> yeah
[13:40] <didrocks> pitti: btw, if you are interested in the structure: https://github.com/ubuntu/ubuntu-make/tree/master/debian/tests
[13:41] <didrocks> you basically have: pep8/small/medium/large
[13:41] <didrocks> which are the real tests
[13:41] <didrocks> (you can pass TESTS="small large" for instance)
[13:41] <didrocks> no parameter is what we used to have "pep8 small"
[13:41] <didrocks> collect-coverage is for collecting and archiving global coverage report
[13:42] <didrocks> custom is used when you set one or more specific tests
[13:42] <didrocks> like TESTS="tests/small/test_foo.py:Bar.baz tests/…"
[13:42] <didrocks> and TESTS=all runs everything but custom ofc
[13:43] <didrocks> (well, it runs custom which is skipped)
[13:43] <pitti> didrocks: ah, https://github.com/ubuntu/ubuntu-make/blob/master/debian/tests/control is clever -- so you have a separate "setup" job and re-use the testbed for everything
[13:44] <pitti> didrocks: btw, there's no need to repeat all the stanzas
[13:44] <pitti> didrocks: as long as the depends:, restrictions: etc. are identical, you can just do
[13:44] <pitti> Tests: foo bar baz
[13:44] <didrocks> oh, even better then!
[13:44]  * didrocks modifies
[13:45] <pitti> didrocks: wouldn't it be easier to run https://github.com/ubuntu/ubuntu-make/blob/master/debian/tests/setup-testbed#L17 with "needs-root"?
[13:46] <pitti> didrocks: calling sudo in tests is a bit meh (if you do it, please call "sudo -n", to avoid eternal hangs because of password questions)
[13:46] <pitti> didrocks: you can do su -c "commands here" $ADT_NORMAL_USER
[13:46] <didrocks> ah, there is a variable for this :)
[13:46] <didrocks> I was going to ask how to not hardcode "ubuntu" for user name
[13:47] <didrocks> (I still have some commands I don't want as root)
[13:47] <pitti> meh, apt-get install has some trouble in the test
[13:47] <didrocks> argh?
[13:47]  * didrocks looks
[13:48] <pitti> didrocks: you can't :) (I just looked at the tail -f of the log)
[13:48] <pitti> http://paste.ubuntu.com/14437883/
[13:48] <didrocks> ah ok, so it's not the one running I see (I only see one btw? I maybe typoed the env variable…)
[13:49] <pitti> didrocks: that's the old one without --env, yes (no "env" in the command line)
[13:49] <didrocks> hum, I didn't get this kind of no tty issue on my xenial vm at least
[13:49] <pitti> DEBIAN_FRONTEND=noninteractive ?
[13:49] <didrocks> so, debconf doesn't really like it
[13:49] <didrocks> yeah, I didn't setup anything for this though here
[13:50] <didrocks> I wonder if a default changed
[13:50] <pitti> although wait, this is already set in tests
[13:50] <pitti> but this doesn't make it through  sudo
[13:50] <pitti> didrocks: that test run finished now (due to apt-get error), should be in swift now
[13:51] <pitti> didrocks: which PPA was that against?
[13:51] <didrocks> pitti: ubuntu-desktop/ubuntu-make
[13:51] <didrocks> (as I takes last ppa from the list IIRC to match against)
[13:51] <pitti> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ubuntu-desktop-ubuntu-make?format=plain
[13:52] <pitti> sorry, not xenial, trusty
[13:53] <pitti> didrocks: ah, this one looks happier, but that didn't install -desktop: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty-ubuntu-desktop-ubuntu-make/trusty/amd64/u/ubuntu-make-master/20160108_134929@/log.gz
[13:54] <didrocks> ah, they are not stored
[13:54]  * didrocks was stupidely looking at the first one
[13:55] <didrocks> so, I can ofc now change the Depends: line
[13:55] <didrocks> as I have everything in one line
[13:56] <pitti> didrocks: you can line-break test control just the same way as debian/control, FYI
[13:56] <didrocks> but that would mean that I don't add needs_root for setup (but I can add -n to sudo)
[13:56] <didrocks> ah nice :)
[13:56] <pitti> didrocks: you still need it to configure autologin and stuff though?
[13:56] <didrocks> yeah, and also the setup does some extra stuff
[13:59] <didrocks> oh, actually, I didn't really try to setup the testbed that way
[13:59] <pitti> hah, didrocks is serial-killing workers again :)
[13:59] <didrocks> as I already had an ubuntu-desktop VM
[13:59] <didrocks> (the adt one)
[13:59] <didrocks> and reused that one
[13:59] <didrocks> so sudo apt install ubuntu-desktop was a noop (only updating the metapacakge)
[14:00] <didrocks> pitti: I guess I'm going to start now from a cloud image as in the infra
[14:00] <didrocks> and see what's going on when installing ubuntu-desktop without any tty
[14:00] <didrocks> (or ssh)
[14:00] <pitti> didrocks: potential gotcha: test Depends: don't install recommends by default; if you do need them, Restrictions: needs-recommends
[14:02] <didrocks> pitti: ok, shouldn't be a problem. If I want to install ubuntu-make itself, even from a git repo, it will only try to match the package name, right? not the real version (like, if git changed debian/changelog but it's not released yet?)
[14:02] <pitti> didrocks: right, test-git is *only* for the test (debian/tests/control); it doesn't get built
[14:03] <pitti> --env=T --env=E --env=S --env=T --env=S --env== --env=p --env=e --env=p --env=8
[14:03] <pitti> didrocks: I don't think that was intended
[14:03] <pitti> didrocks: array vs. string confusion somewhere?
[14:03] <pitti> didrocks: "env" parameter is a list, not a string
[14:04] <didrocks> hum, not with adt-run, though?
[14:04] <didrocks> I had to sue --env="TESTS=medium large"
[14:04] <didrocks> for instance
[14:04] <pitti> didrocks: no, but that's what is on the command line
[14:04] <didrocks> yeah
[14:04] <didrocks> I checked the wrapper
[14:04] <didrocks> it's using a string parameter
[14:05] <pitti> didrocks: i. e. I suppose your run-adutopkgtest change submits it as a string, not a list
[14:05] <didrocks> so somewhere else in the chain?
[14:05] <didrocks> ah, it's not passed as such to adt-run?
[14:05] <pitti> didrocks: it needs to be {"env": ["foo=bar", ...]}
[14:05] <pitti> not {"env": "foo=bar"}
[14:06] <pitti> didrocks: so every entry in "env" is passed as --env=value, yes
[14:06] <pitti> but "every entry" in a string is a character onnly
[14:06] <pitti> {"test-git": "https://github.com/ubuntu/ubuntu-make.git", "ppas": ["ubuntu-desktop/ubuntu-make-builddeps", "ubuntu-desktop/ubuntu-make"], "env": "TESTS=pep8"}
[14:06] <didrocks> ok, I was still puzzled by the adt-run --env="TESTS=medium large" <…> format :)
[14:06] <pitti> didrocks: ^ that's what was in the queue
[14:06] <didrocks> but ok, making sense
[14:07] <didrocks> I would have had --env="TESTS='medium large'" <…> for instance
[14:07] <pitti> but it needs to be ... "env": ["TESTS=pep8"]}
[14:07] <pitti> didrocks: run-autopkgtest shoudl accept multiple --env options, then it'll automatically be a list
[14:09] <didrocks> pitti: ok, modified as such
[14:09] <attente> good morning all
[14:09] <didrocks> good morning attente
[14:09] <seb128> hey attente
[14:09] <attente> hi didrocks, hi seb128
[14:10] <pitti> didrocks: so that, eatmydata (if available), and DEBIAN_FRONTEND=noninteractive or moving the installation to d/t/control?
[14:10] <didrocks> pitti: moving the installation, one sec, finish up formatting and pushing
[14:10] <attente> seb128: thanks for approving that u-s-d merge. do you know who i should ping about maliit-inputcontext-gtk?
[14:10] <didrocks> and adding -n to remaining sudo calls
[14:10] <pitti> didrocks: btw, adt-run has a --testname option which sounds like what your $TESTS does; it sounds useful to expose that as test param too?
[14:10] <seb128> attente, no idea, try asking kenvandine or bfiller maybe?
[14:11] <seb128> they probably can redirect you
[14:11] <attente> seb128: sure, thanks
[14:11] <seb128> yw
[14:11] <pitti> didrocks: then it will only run that given test from d/t/control, not all of them
[14:11] <didrocks> pitti: mine is a little bit more complex than this, I always need setup and collect to run
[14:12] <didrocks> + the testname can be more specific
[14:12] <pitti> ah, ok
[14:12] <didrocks> like "tests/small/test_foo.py:Bar/baz tests/large/test_games:Unity3DTests"
[14:12] <didrocks> for instance
[14:12] <didrocks> to only run those 2
[14:12] <didrocks> (help debugging as some tests can take some very long time
[14:12] <didrocks> )
[14:13] <didrocks> and that results in the end to "setup/custom/collect" to be run
[14:13] <didrocks> (pep8/small/medium/large are all "passing", doing nothing)
[14:13] <didrocks> and custom do the right thing
[14:13] <didrocks> pitti: making more sense? ^
[14:13] <pitti> didrocks: yes, it does
[14:14] <kenvandine> attente, try Elleo
[14:14] <pitti> just looking for potential simplifications, but cf. "as simple as possible, but no simpler" :)
[14:14] <attente> kenvandine: thanks
[14:16] <kenvandine> np
[14:18] <didrocks> pitti: ah, but I remove ubuntu-make in some condition
[14:18] <didrocks> conditions
[14:18] <didrocks> pitti: so, I will need to keep that one installed in setup-testbed, right?
[14:18] <didrocks> pitti: or is adt-run a little bit dummy and just parsing d/t/c and see if things match?
[14:19] <didrocks> (even if tests can remove some packages)
[14:19] <didrocks> (I remove ubuntu-make in case of branch testing to ensure there is no confusion on what is running)
[14:19] <pitti> didrocks: yes, it only parses Depends:, it doesn't check what's actually installed on the testbed after a test
[14:19] <didrocks> ok ;)
[14:20] <didrocks> as I remove umake/ dir when running system setup to ensure I don't have an import which is magically resolved by the local folder (also, coverage report is then confused)
[14:24] <didrocks> pitti: looking good to you? https://github.com/ubuntu/ubuntu-make/blob/master/debian/tests/control
[14:25] <didrocks> hope you support trailing commas :)
[14:25] <pitti> didrocks: needs-recommends is really necessary with this?
[14:25] <pitti> didrocks: I think it does, test it locally with your desktop image? (just the smallest test you have, pep8?)
[14:26] <didrocks> pitti: well, I use needs-recommends to have a desktop image as close as possible to reality
[14:26] <didrocks> let's see with my dekstop image how that goes
[14:26] <pitti> didrocks: I haven't tested multi-line Tests: and Restrictions:, thanks for being guinea pig :)
[14:26] <pitti> didrocks: right, but reality changes quite often :)
[14:27]  * didrocks *guineas*
[14:27] <didrocks> :p
[14:27] <pitti> didrocks: and libreoffice, orca, thunderbird etc. will hardly matter?
[14:27] <didrocks> that's true, I'm still worried about things we miss that can interfere though (even if I mostly need lightdm and unity TBH)
[14:27] <pitti> didrocks: I'd actually argue the other way around: If u-make depends on something which isn't a depends: of u-desktop, then that dependency is missing
[14:28] <pitti> didrocks: well, leave it in for now, and then we can just try a run without
[14:28] <didrocks> pitti: well, it's more for frameworks we install on, TBH, than umake itself
[14:28] <didrocks> but yeah, agreed
[14:29] <pitti> no recommends: should make the install a looot faster
[14:29] <didrocks> yeah, if we don't start from a desktop image.
[14:29] <didrocks> let's get the thing running and then, we can give a try
[14:30] <didrocks> it*
[14:30] <pitti> agreed
[14:31] <didrocks> ok, multi-line worked!
[14:31] <pitti> cool
[14:31] <didrocks> so, let's try a run (running small tests, which are less than a minute)
[14:31]  * pitti puts an "officially didrocks approved" stamp onto autopkgtest
[14:31] <didrocks> that will test the env variable again :)
[14:31] <didrocks> don't go toooo fast :)
[14:34] <didrocks> http://autopkgtest.ubuntu.com/running.shtml#pkg-ubuntu-make-master
[14:34] <didrocks> let's see…
[14:35] <didrocks> at least env make sense :)
[14:35] <pitti> --env=TESTS=pep8
[14:36] <pitti> yep
[14:36] <pitti> and it's running
[14:37] <didrocks> I'm trying a second one in parallel which should give: --env="TESTS=pep8 small"
[14:38] <pitti> didrocks: I see three running tests, all have --env=TESTS=pep8 only
[14:39] <didrocks> 3? I made 2 requests…
[14:39] <didrocks> weird
[14:39] <seb128> bah, laptop not booting anymore
[14:39] <seb128> took me a bit to figure out that it boots with the previous kernel
[14:39] <didrocks> and I only see one in the web ui
[14:39] <seb128> also grrrr at systemd for not being able to reboot a machine
[14:40] <seb128> it's stucked for ever on the dots animate and never reboot, need to sit on the power key
[14:40] <pitti> didrocks: yeah, web UI bug -- it can't tell apart multiple tests with exactly the same params
[14:41] <didrocks> pitti: my 2 requests were: ubuntu-make-master
[14:41] <didrocks> hum
[14:41] <didrocks> grrr @middle-click bug
[14:41] <didrocks> http://paste.ubuntu.com/14438198/
[14:41] <didrocks> better
[14:42] <pitti> didrocks: hm, that got eaten somewhere then
[14:43] <didrocks> pitti: yeah, let's see first at least if one requests goes successfully to the end :)
[14:43] <didrocks> btw, run-autopkgtest isn't versioned?
[14:43] <pitti> didrocks: versioned how?
[14:43] <didrocks> (I just modified it on snakefruit, didn't seem to have been bzr add on the vcs)
[14:44] <pitti> didrocks: oh, britney2-ubuntu is in bzr
[14:44] <pitti> didrocks: you should see a bzr diff on snakefruit if you modified it there
[14:44] <pitti> didrocks: and it's there
[14:44] <didrocks> $ bzr diff run-autopkgtest@
[14:44] <didrocks> bzr: ERROR: Path(s) are not versioned: "run-autopkgtest@"
[14:45] <pitti> didrocks: ah, bin/run-autopkgtest is a symlink to ~/proposed-migration/code/b2
[14:45] <didrocks> it's under "unknown"
[14:45] <didrocks> ah
[14:45] <didrocks> hum
[14:45] <didrocks> a lot of other uncommited modif in this repo
[14:45] <pitti> didrocks: just the config (setting the password)
[14:45] <didrocks> where is my git add? ;)
[14:46] <pitti> didrocks:  you can't push on snakefruit anyway
[14:47] <pitti> didrocks: ah, TESTS=pep8 still installs ubuntu-desktop; I guess that's a consequence of moving to Depends:?
[14:47] <didrocks> pitti: yeah, that's wanted
[14:48] <didrocks> (until we have base images for this)
[14:48] <pitti> my hope is actually that without recommends and with eatmydata that thing is fast enough so that we stop caring as long as you aren't actually watching it :)
[14:49] <didrocks> pitti: I'm not in ~ubuntu-release, so I can't push from here (France, Lyon, @home) :)
[14:49] <didrocks> pitti: yeah, let's see :)
[14:49] <pitti> didrocks: send me a patch, bundle, or MP?
[14:50]  * didrocks will sms you the diff
[14:50]  * pitti does adb | git am -
[14:50] <didrocks> heh
[14:50] <pitti> didrocks: the fun thing is, my mobile just rang with a notification :)
[14:51] <pitti> (but it's just the reminder for the 16:00 UES update confcall)
[14:53] <pitti> didrocks: voilà: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty-ubuntu-desktop-ubuntu-make/trusty/amd64/u/ubuntu-make-master/20160108_145250@/log.gz
[14:53] <didrocks> pitti: https://code.launchpad.net/~didrocks/britney/additional-parameters/+merge/282007
[14:53] <didrocks> pitti: heh, on @mobile ringing :)
[14:54] <pitti> didrocks: that took 15 minutes, not tooo bad
[14:54] <didrocks> yeah, it's not as bad as it could have been :)
[14:54] <didrocks> ok, I need to check the artefacts
[14:55] <pitti> didrocks: so without recommends that's maybe just 7
[14:55] <didrocks> looks perfect!
[14:55] <didrocks> I still have the per-tests artefacts and the global coverage collect
[14:55] <pitti> didrocks: code coverage is a bit poor :)
[14:55] <pitti> didrocks: I see lots of coverage files etc. in artifacts.tar.gz, so looks ok?
[14:56] <didrocks> pitti: rohhhhhhhh, why pep8 doesn't test more, right! ;)
[14:56] <didrocks> pitti: yeah :p
[14:56] <didrocks> basically you have subfolders
[14:56] <pitti> didrocks: so, go and hit it with the full thing!
[14:56] <didrocks> like artifacts/{pep8, small, …}
[14:56] <pitti> didrocks: perhaps once with recommends, once without, then we can compare
[14:56] <didrocks> and the global one at root
[14:57] <didrocks> pitti: hum, I think I need to look at why --env="TESTS=pep8 small" didn't work first
[14:58] <pitti> ah, right
[14:58] <pitti> didrocks: do you need that for the full test suite?
[14:58] <didrocks> yeah
[14:58] <didrocks> I only run pep8 and small without arguments
[14:58] <didrocks> (as large depends on 3rd party services, unfair to block packages if some $networks are starting to fail and they can)
[14:59] <didrocks> medium were a little bit flacky, but I made them way better, I want to see how they run first
[14:59] <didrocks> (on the cloud)
[15:05] <didrocks> pitti: seems the target focus isn't the right branch, I've done another MP at https://code.launchpad.net/~didrocks/britney/additional-parameters/+merge/282015
[15:09] <pitti> didrocks: pulled, thanks!
[15:09] <didrocks> sweet :)
[15:10] <Laney> cyphermox / xnox: Can you remind me how to start ubiquity from a bzr checkout please? :)
[15:10]  * Laney has asked this loads of times before but always forgets
[15:11] <pitti> time for adding that to README?
[15:11] <pitti> or better ./run-from-checkout
[15:11] <xnox> Laney, .... are you in the vm?
[15:12] <xnox> (don't start ubiquity on the installed machine...)
[15:12] <Laney> xnox: I hacked main
[15:12] <Laney> it's not going to do anything bad now
[15:13] <xnox> don't go past partitioning step, is all that i can suggest ;-)
[15:13] <didrocks> "oupsss, pressed enter"
[15:13] <didrocks> :)
[15:13] <Laney> I want to make the slideshow step use wk2, no need to go beyond that
[15:13] <Laney> but I don't know how to launch the darned thing properly!
[15:27] <Laney> bleh
[15:29] <pitti> Laney: last time I hacked ubiquity, I gave up and just changed the code inline on a live session
[15:29] <pitti> Laney: i. e. scp the changed files, then run it from live
[15:29]  * Laney is going to just install it probably
[15:29] <Laney> I hacked it to just launch to the slideshow anyway
[15:35] <Laney> eww, those deps
[15:35]  * Laney goes for a vm after all
[16:02] <didrocks> pitti: oh, I know why you got 3 instances running before
[16:02] <didrocks> so run-autopkgtest -s trusty -a amd64 --ppa=ubuntu-desktop/ubuntu-make-builddeps --ppa=ubuntu-desktop/ubuntu-make --test-git https://github.com/ubuntu/ubuntu-make.git --env "TESTS=pep8 small" ubuntu-make-master
[16:02] <didrocks> (using the ssh redirection line) ends ups in running "small" (see the swift container) and ubuntu-make-master :p
[16:02] <pitti> ah!
[16:02] <pitti> yay quoting
[16:03] <pitti> didrocks: so if you'd run that directly on snakefruit it would work
[16:03] <didrocks> yeah, I guess so
[16:04] <pitti> didrocks: or use double quoting
[16:04] <didrocks> it's a little bit counter intuitive, I wonder if we can make that better
[16:04] <pitti> didrocks: use commas for separating test names :)
[16:04] <didrocks> yeah, sounds like an option
[16:04] <pitti> (actually I'm quite serious -- on CLIs it's mostly just not worth the trouble dealing with spaces correctly)
[16:04] <didrocks> I liked having a nosetests3 compatible format
[16:05] <didrocks> does nosetests3 support commas? it's just a list of args
[16:05] <pitti> didrocks: ah, maybe not, I don't know nose
[16:07] <didrocks> I guess commas is the best option, quite annoyed to change the format compared to runtests for local run, but I guess it's okish
[16:07] <pitti> didrocks: or double-quote
[16:07] <pitti> didrocks: you wouldn't trigger them manually that often, so it's not such a biggie
[16:08] <didrocks> pitti: yeah, it's more an issue of remembering when trying some PR branch
[16:15] <Laney> still mostly light at 16:15
[16:15] <Laney> spring is coming
[16:15] <seb128> :-)
[16:18] <didrocks> "some" yeah
[16:19] <Laney> xnox: how do I get ubiquity to show me tracebacks?
[16:19] <Laney> seems the wrapper is doing something with stderr
[16:20] <xnox> it's in ubiquity logs in like /var/log/ubiquity/ no?
[16:20] <Laney> nein
[16:20] <xnox> and/or in the popout window
[16:20]  * pitti waves good night
[16:20] <xnox> =(
[16:20] <Laney> no window
[16:20] <Laney> that log directory doesn't even exist
[16:20] <Laney> maybe it's erroring too early?
[16:20] <Laney> I put a syntax error in gtk_ui.py on purpose to test
[16:21] <didrocks> good night pitti!
[16:21] <seb128> pitti, have a good w.e!
[16:23]  * Laney tries to port directly sans-tracebacks :-)
[16:27]  * didrocks waves good evening, have a nice week-end everyone! :)
[16:28] <seb128> didrocks, thanks, you too
[16:29] <willcooke> cya didrocks
[16:30] <Laney> bye didrocks!
[16:30] <didrocks> see you willcooke, Laney, seb128!
[16:30]  * Laney appeciates that didrocks stays around for a minute now ;-) 
[16:31] <didrocks> Laney: thinking of you! :)
[16:31] <Laney> you BEAST!
[16:33] <willcooke> darn window focus
[16:34] <seb128> ctrl-w?
[16:34] <willcooke> ha, yeah
[16:34] <seb128> :-)
[16:34] <seb128> I do that often when I use dual screen
[16:34] <seb128> look at one screen and closing thing on the other
[16:37] <willcooke> exactly
[17:50] <Laney> weeeeeeeeeee
[17:50] <seb128> Laney, enjoy!
[17:50] <Laney> woah
[17:50] <Laney> no NO!
[17:50] <Laney> I was weeing at something working
[17:50] <seb128> ah ok :-)
[17:51] <Laney> Note that due to historical reasons, GtkNotebook refuses to switch to a page unless the child widget is visible. Therefore, it is recommended to show child widgets before adding them to a notebook.
[17:51] <Laney> that was a very helpful piece of documentation
[17:51] <Laney> thanks whoever wrote it
[18:05] <Laney> ok
[18:05] <Laney> now I am going
[18:05] <Laney> laters! happy weekend
[18:06] <seb128> bah
[18:07] <seb128> gnome-icon-theme upload rejected because the vcs was outdated
[18:07] <seb128> going to resolve that on monday
[18:07] <seb128> Laney, have a good w.e!
[18:07] <Laney> MY BAD
[18:07] <Laney> SORRY!!!!
[18:07] <seb128> & same to desktopers
[18:07] <willcooke> see ya
[18:07] <seb128> Laney, no worry, and I pushed my revision
[18:07] <seb128> let's sort that next week
[18:07] <seb128> no hurry
[18:08] <seb128> willcooke, have a good w.e!
[18:10] <willcooke> I'm off too - ta ta
[18:12]  * Laney pushed a fix up for seb128
[18:12] <Laney> didn't upload it though, too scary
[18:12] <Laney> byeee
[22:47] <attente> have a good w.e. everyone
[22:52] <flocculant> attente: have a good one too :)
[22:52] <flocculant> I thought I would say that - you're late, they've all gone already ;)
[22:53] <attente> flocculant: haha, thanks :)
[22:53] <flocculant> :)
[22:54] <flocculant> always someone waiting for Laney to throw sand at them it seems :D