/srv/irclogs.ubuntu.com/2016/08/29/#ubuntu-devel.txt

pitti@pilot out04:32
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
pitti(whoops, forgot to reset on Friday)04:32
pittiGood morning04:32
jbicha_pitti: good morning, have you seen bug 1614820 ?04:37
ubottubug 1614820 in apport (Ubuntu) "Respect gsettings org.gnome.desktop.privacy report-technical-problems" [Wishlist,New] https://launchpad.net/bugs/161482004:37
=== jbicha_ is now known as jbicha
pittijbicha_: hey, good morning! I saw it fly by, just haven't looked at it yet (ETIME, sorry)04:38
jbichaok, maybe next release cycle then04:39
pittijbicha: it would be really hard to avoid generating the /var/crash/ files, but merely not reporting them should be fairly straightforward in apport-gtk?04:48
pittijbicha: i. e. this is just checking for that gsettings key?04:48
pittiorg.gnome.desktop.privacy report-technical-problems false04:50
pittijbicha: but why is this off by default?04:50
pittijbicha: we certainly don't want that04:50
jbichawe can ship a gsettings override, perhaps in apport itself, for that04:52
pittijbicha: not in apport, that would be rude (changing defaults of some other package)04:52
jbichathe package is gsettings-desktop-schemas04:53
jbichawe have lots of overrides in ubuntu-default-settings and ubuntu-gnome-default-settings but some people don't have those installed04:53
jbicha(ubuntu-settings)04:53
jbichathe only thing actually using that key right now I believe is Fedora's abrt so it doesn't hurt anything to set that key how we want it04:54
pittijbicha: another concern is that we already have such a setting somewhere ("Send error reports to Canonical")04:57
pittiso that ^ one should move to this new official key04:57
pittiI followed up to the bug with a summary04:57
jbichapitti: the gsettings key is from update-notifier so maybe that part of the bug doesn't need any apport changes05:04
jbichabut the other part of the bug is that GNOME expects the bug reporting service to run a org.freedesktop.problems.daemon dbus service, what do you think about that?05:05
pittijbicha: apport isn't a daemon, what should this  do?05:11
pittiand what happens if it's not there?05:11
jbichaif it's not there, GNOME doesn't show the on/off switch to report bugs in Intial Setup and gnome-control-center's Privacy pages05:12
jbichawe could run a service that does nothing (that works) or we could patch the 2 apps to skip checking for that service05:13
jbichaI guess patching the apps would be better if there's no reason otherwise for apport to listen on dbus05:32
pittirharper, smoser: FYI, netplan 0.10 just landed in y, with support for vlan05:59
pittimwhudson, rharper, smoser: I'm going to look into wifi with networkd first (blocking ogra), is there anything else which is blocking you wrt. netplan?06:00
cpaelzergood morning06:16
mwhudsonpitti: if you could spend 5 mins looking at https://github.com/snapcore/snapd/pull/1765 that'd be great07:15
mwhudsonpitti: but i am off sick _and_ EOD so no hurry :)07:16
LocutusOfBorgjbicha, hi, do you plan to look at kido?07:21
LocutusOfBorgI see some upstream activity07:22
jbichaLocutusOfBorg: the best I came up with was filing bug 1617835 but if you can do better, go ahead07:30
ubottubug 1617835 in kido (Ubuntu) "Please remove fcl 0.5.0-1 from yakkety-proposed" [High,New] https://launchpad.net/bugs/161783507:30
LocutusOfBorgjbicha, fcl is fixed in Debian I see07:32
LocutusOfBorglet me see07:32
LocutusOfBorgit might be trivial07:35
Saviqpitti, morning, could I ask you to restart the last missing test in https://requests.ci-train.ubuntu.com/static/britney/ticket-1864/landing-067-xenial/excuses.html - it seems to have disappeared - and also https://requests.ci-train.ubuntu.com/static/britney/ticket-1864/landing-067-yakkety/excuses.html - not sure what made it uninstallable there07:46
pittimwhudson: ugh, get well soon!07:59
pittiSaviq: sorry, had to kill some running tests due to cloud maintenance, will restart08:00
Saviqtx08:05
=== JanC is now known as Guest45177
=== JanC_ is now known as JanC
=== carlo is now known as Guest67116
ogra_pitti, nothing else for now ...08:50
ogra_(we dont have networkd on the images though)08:50
ogra_(and i dont see it in the xenial archive)08:51
pittiogra_: sure you do08:52
pittiit's in the systemd package :)08:52
ogra_ah, it doesnt have its own binary package ?08:52
* ogra_ kind of expected that 08:52
gb_mkshello09:48
gb_mksI found a bug related in the package "click-review". Can anyone help me to solve it? https://bugs.launchpad.net/click-reviewers-tools/+bug/161728809:49
ubottuLaunchpad bug 1617288 in Canonical Click Reviewers tools "click-review assumes Ubuntu vendor" [Undecided,New]09:49
=== zigo_ is now known as zigo
Saviqpitti, hey, we're trying to get to grips with unity8 failures in britney, we've a bunch of flaky fixes in store, but the most common issue these days seems to be a time out, how long is the timeout on autopkgtests in britney by default? from looking at timestamps, it seems to be 3h - a passing run of unity8 seems to be between 2h and 2h54m (even though http://autopkgtest.ubuntu.com/packages/u/unity8/yakkety/amd64/ says 5h33m, but that seems to be some09:57
Saviq delay outside of the test run itself?)09:57
pittiSaviq: right, the default timeout is 10,000s, i. e. roughly 2:50 hours09:58
pittiSaviq: right, lcy01 has been very unstable (should be fixed now), so some tests were attempted several times09:58
Saviqyup, that sounds about right09:58
Saviqpitti, is it possible to increase the time out for unity8?09:59
pittiSaviq: but these cloud failures should not appear as test failures, they get auto-retried until it finishes09:59
SaviqI can easily imagine it going over the 2:50h mark if the system load is higher, for example09:59
pittiSaviq: it is, if they legitimately take that long09:59
pittiso if they don't just hang eternally on something09:59
pittiSaviq: does that affect all arches?10:00
Saviqpitti, we only claim victory on those on amd64 and i386, and both sometimes go over the 2h50m limit10:00
Saviqpitti, it would go down considerably if they were run in parallel10:01
pittiSaviq: qmluitests.sh seems to need around 1:45 h, well below the 2:50 h limit10:01
Saviqbecause there's at least some time spent in those tests waiting (we're improving that now, too)10:01
pittiSaviq: do you actually see such a timeout in http://autopkgtest.ubuntu.com/packages/u/unity8/yakkety/amd64/ ? I don't10:02
Saviqpitti, I think it depends a lot on the load, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid-ci-train-ppa-service-landing-092/vivid/i386/u/unity8/20160822_110521@/log.gz10:02
pittithe failures there are pretty fast10:02
Saviqpitti, I've only seen those on PPA tests, couldn't find any example on proposed migration10:03
Saviqlemme have a good look again10:03
pittiSaviq: so this might rather be vivid vs. yakkety?10:03
pittiSaviq: anyway, I can bump it, but I'd really not do it if these are eternal hangs10:03
pittithese are blocking the infra long enough already10:03
Saviqpitti, we have one potential example of an eternal hang there, we're working on fixing that now, too - but it's tricky to say it really is if we're getting timeouts for other reasons, too10:05
Saviqpitti, about parallel, do the test nodes have more than one core?10:05
pittiSaviq: normally not10:06
pittiSaviq: we can mark it as "big test" and give it 4 cores and more RAM, if that helps to speed up the test considerably, i. e. if it actually *can* run in parallel10:06
Saviqpitti, they do run in parallel in our CI10:07
pittiSaviq: the tradeoff is that they are much more likely to fail due to cloud capacity issues10:07
pittiSaviq: so if they automatically use more available cores, I can add it to that list10:07
Saviqpitti, we rely on DEB_BUILD_OPTIONS=parallel, is that going to be set?10:08
pittiyes, that happens automatically10:08
Saviqpitti, I'd say let's try that10:08
pittiSaviq: oh, is the autopkgtest a package build?10:08
Saviqpitti, no10:08
Saviqit's 1300 UI tests10:08
pittiD_B_O is only set for builds, not for tests10:08
pittias this is a dpkg-buildpackage specific thing10:09
Saviqhmm, bug #1399177 ?10:09
ubottubug 1399177 in autopkgtest (Ubuntu) "adt-run should parallelize builds as necessary by default" [Wishlist,Fix released] https://launchpad.net/bugs/139917710:09
pittitests should ask nproc or /proc/cpuinfo etc.10:09
Saviqah ack10:09
Saviqso builds but within adt-run10:09
Saviqstill10:09
Saviqwe'll fix that then10:09
pittieek, indeed10:09
Saviqpitti, let's mark unity8 big, then, and I'll land a fix to the test script to talk nproc10:10
pittiSaviq: is it really necessary to build the package for running the tests?10:10
Saviqpitti, we're not building the package10:11
Saviqwe're building a few mocks10:11
pittiSaviq: also, the build doesn't happen via "Restrictions: build-needed" by autopkgtest itself, but the test calls dh_auto_configure etc., so it's manually building the package without dpkg-buildpackage10:11
Saviqpitti, it's not building the whole thing, only some mocks10:11
Saviqbut yes, we're doing away with that too10:12
pittiah, ok10:12
Saviqwe'll package those mocks soon10:12
pittiSaviq: so, back to the question: will any of this actually use more than one core if they are available?10:12
Saviqpitti, not right now, if adt-run doesn't set D_B_O parallel, I'll have to fix the test to do that from nproc then10:13
Saviqso maybe it doesn't make sense to mark it big yet10:14
Saviqto not block the infra10:14
Saviqpitti, can we increase the time out to 3h30m or so for now, it should give us a bit more info on whether we have a real issue or not10:15
Saviqand I'll work on getting nproc in and we'll mark unity8 big after that's done10:16
pittiSaviq: I can set it to 40,000 s by adding it to the "long_tests" list (i. e. roughly 12 h)10:16
Saviqpitti, right, if I see any time out there then, we'll know it's our fault10:17
Saviqthat would work10:17
pittiSaviq: ok, rolled out that change10:19
Saviqpitti, thanks, I'll let you know how we're doing10:19
pittiack10:19
=== hikiko is now known as hikiko|ln
mardypitti: hi! a new version of gnome-control-center-signon has landed in yakkety, so hopefully the version number is now consistent10:44
mardypitti: (talking about bug 1565772)10:44
ubottubug 1565772 in gnome-control-center-signon (Ubuntu Yakkety) "[SRU] Allow plugins to decide which username to set on new accounts" [Critical,In progress] https://launchpad.net/bugs/156577210:44
LocutusOfBorgjbicha, kido is good11:20
LocutusOfBorgfcl too, assuming somebody removes the armhf binary :)11:20
pittimardy: thanks! I'll mark it as v-needed  (dropping v-failed) once LP comes back (has been down for me in the last 10 mins)11:22
mardypitti: OK, thanks11:23
=== hikiko|ln is now known as hikiko
=== _salem is now known as salem_
smoserpitti, we do need bonds.12:34
ogra_james bonds ?12:36
pittismoser: ok, I have that on the list for early September12:58
=== dpm is now known as dpm-afk
=== dpm-afk is now known as dpm
kenvandinepitti, ping13:48
kenvandinepitti, we're about ready to land some work in libertine that makes it build depend on content-hub, which depends on ubuntu-app-launch... which of course depends on upstart :)13:48
kenvandineso we need the libertine binaries to be removed for s390x in yakkety13:49
kenvandinepitti, can you please help out with that?13:50
dobeyomg circular deps13:53
pittikenvandine: removed; AFAICS the reverse dependencies of libertine shoudl already be removed13:58
kenvandinepitti, thanks!13:58
kenvandineChrisTownsend, ^^13:59
ChrisTownsendpitti: kenvandine: Thanks!14:00
jonathonIs it possible to get a package update into universe? The SRU wiki page doesn't mention universe (there's a link to an anchor from the MOTU page but it's not there any more).14:20
pittijonathon: there is no difference wrt. the policy, i. e. "yes"14:20
jonathonRight-o, thank you. I'll read through the pages a few more times. :)14:25
=== kirkland` is now known as kirkland
rbasakinfinity: are you chairing the DMB meeting in five minutes?14:55
rbasakBenC: around?14:56
rbasak!dmb-ping15:00
ubottubdmurray, BenC, cyphermox, infinity, micahg, rbasak, sil2100: DMB ping.15:00
=== jcastro_ is now known as jcastro
pittiawe: yay, I read the NM 1.4 announcement yesterday, seems our ofono patches are upstream now? congrats!15:10
ogra_woah !15:11
awethanks pitti!15:11
pittiawe: Debian already has 1.4, so merge o'clock soon?15:11
awehehe15:11
* awe hopes there are no dbus interface changes15:11
pittiawe: yeah, "Canonical contributed ... ofono support" was a nice read there :)15:11
ogra_the result of years of work ....15:11
aweindeed15:11
pittiawe: allegedly the API has stayed very stable, even 1.2 plugins still work with NM 1.415:12
aweabeato got a nice mention as well for his statistics API15:12
awepitti, yes... that's pretty much true, although the move to gbus had some unexpected side-effects15:12
awealso, there's still a bit of code that didn't get merged upstream15:13
aweso we'll still need to carry some patches15:13
awebut it was a good start15:14
aweand hopefully we can continue to push more code to them15:14
cpaelzerhi, anybody here knows how/where I should reach out to get s390x enabled in an ppa on LP ?15:37
=== salem_ is now known as _salem
attentehi, i'm getting this debootstrap error: "chroot: cannot change root directory to '/home/william/tmp/root': Operation not permitted"16:02
attentethis is when running it with fakeroot in my home directory16:03
attenteis there a reason why debootstrap needs to chroot here?16:03
attenteis there a better way than using fakeroot?16:07
=== _salem is now known as salem_
jonathoncpaelzer: #launchpad might worth a look?16:27
dobeyattente: sudo?16:35
attentedobey: trying to do this unprivileged in my home16:48
ogra_attente, wont work, deboostrap needs to create device nodes ... you can try fakechroot ... if you actually like cans of worms16:55
ogra_(or just download an ubuntu-base tarball ;) instead of building yourself )16:56
dobeyyeah, download the preinstalled tarball then16:57
attentewhere is the tarball? i'll try that16:58
ogra_http://cdimage.ubuntu.com/ubuntu-base/releases/xenial/release/ or http://cdimage.ubuntu.com/ubuntu-base/daily/current/17:02
ogra_depending what you want17:02
elbrusginggs_: thanks (unfortunately the autopkg fails on ci.debian.net and I don't know why, as it works on my computer)19:32
elbrushere it doesn't ask the password and that is correct. however on ci.d.n it does ask and fails because the isn't a valid answer at all19:34
* elbrus shakes his head in disbelief and will probably need to upload a package with more debugging output... but doesn't know what output would be good.... mysql -vvv or something19:35
=== SotK_ is now known as SotK
ginggs_elbrus: yw and good luck with the autopkg stuff19:41
=== acheronuk_ is now known as acheronuk
=== alexisb is now known as alexisb-afk

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