mwhudsonok pop quiz time what is going on here https://launchpadlibrarian.net/448056138/buildlog_ubuntu-focal-amd64.python-gevent_1.3.7-1build2_BUILDING.txt.gz02:45
Unit193Looks like a build failure.02:53
mwhudson+1 insightful02:55
Unit193That looks fun, same file is in python3-greenlet-dbg and python3-greenlet.03:07
Unit193Specifically if you look at https://launchpadlibrarian.net/447991806/python-greenlet_0.4.15-2_0.4.15-2ubuntu1.diff.gz03:08
Unit193See why that'd be bad? :P03:08
mwhudsonoh yay03:12
mwhudsonthanks for chasing :)03:12
Unit193Sure.  I guess I can't just make a sarcastic comment. :303:16
mitya57sil2100: hi, can you add focal support to bileto please?07:23
sil2100mitya57: ah! Yes, let me bump the cache07:52
sil2100mitya57: should be enabled in up to 30 minutes07:55
mitya57sil2100: it works now, thanks a lot!08:47
LocutusOfBorgEickmeyer, hello, how can somebody sponsor a fix for LP: #1849168 if 1) there is no indication about which series are affected 2) there is no patch to sponsor ?08:48
ubottuLaunchpad bug 1849168 in carla (Ubuntu) "[SRU] Missing build dep libsndfile1-dev discovered" [Undecided,Fix committed] https://launchpad.net/bugs/184916808:48
LocutusOfBorgmwhudson, Unit193 do I have greenlet greenlight to upload a fix for it?09:01
LocutusOfBorgdoko, ^^09:01
Unit193I just pointed out what went wrong.09:02
LocutusOfBorgyes sure bug greenhighlighting you doesn't hurt!09:03
mwhudsonLocutusOfBorg: i'm all for fixing it, i guess doko can always reject it from the queue if he doesn't like it :)09:04
LocutusOfBorgmwhudson, I think I already crafted a fix09:04
LocutusOfBorgmwhudson, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/10667371/+listing-archive-extra09:20
LocutusOfBorgif you agree09:20
mwhudsonLocutusOfBorg: lgtm09:20
LocutusOfBorgstill have to debdiff debs09:21
LocutusOfBorgfeel free to upload if you like it, or I can do it and credit you :)09:24
LocutusOfBorgI'm also going to update the debian bug report09:24
LocutusOfBorgmwhudson, ping :) I have to replace keyboard and reboot laptop... please let me know if you want me to do it or not09:42
mwhudsonLocutusOfBorg: eh just update it, getting late here09:44
LocutusOfBorgthanks :D09:44
mwhudsonLocutusOfBorg: sorry if i was being ambiguous earlier09:44
LocutusOfBorgI "just" woke up :D09:45
cgm____Hi all, is there somewhere I can find the commands used to build the official Ubuntu netboot ISOs? Specifically the xorriso arguments10:35
rbasakrafaeldtinoco: o/11:18
rbasakrafaeldtinoco: Josh suggested I ask you to arrange a seed change so you can get familiar11:18
rafaeldtinocorbasak: morning o/11:18
rafaeldtinocorbasak: awesome, I read the docs already11:18
rbasakGreat! I want to get mysql-router seeded in Focal11:18
rafaeldtinocoalright, let me go through it11:18
rafaeldtinocoand ask you whenever I have questions11:18
rbasakActually, I should tell you what I really need, rather than presuppose a solution11:19
rbasakWhat I need is mysql-router in main in Focal :)11:19
rafaeldtinocoyep I thought it was that #)11:20
rafaeldtinocorbasak: do u have a MIR already ?11:20
rbasaksrc:mysql-8.0 is in main already, and mysql-router is built from that11:21
rbasakThat's the closest we have to an approved MIR11:21
rbasakcpaelzer: thank you for the uvtool reviews. I'm working on your emulation branch next.11:26
rbasakI have a rebased/squashed version locally.11:26
cpaelzerrafaeldtinoco: you reported a FTBFS on disco12:30
cpaelzerrafaeldtinoco: I wonder what might have changed as the last build worked12:30
cpaelzerand that was an SRU, there surely was no full bump of gcc in Disco since then12:30
cpaelzerdid you check what the reason whas that this now triggers?12:31
cpaelzeror is that a local build, and not one in a "normal" build environment?12:31
rafaeldtinococpaelzer: it was a local build indeed12:32
cpaelzerthen chances are this is "not-a-bug" (in disco)12:32
rafaeldtinocoit can be related to an enabled (in my env) Werror of somesort12:32
cpaelzeryou remember that if .ig tthen switch on developer mode thing12:32
rafaeldtinocoI noticed also that DEB_HOST_XXX variables are not set12:32
rafaeldtinocoso it only works with dpkg-buildpackage basically12:33
rafaeldtinocoi tried manually dh build, debian/rules build12:33
rafaeldtinocoand always got errors12:33
rafaeldtinocoand yes, there are chances of a false alarm12:33
rafaeldtinocosorry if that is12:33
rafaeldtinocoi was more focused in the backport12:33
rafaeldtinocodidnt think about being my build env, yes12:34
rafaeldtinoco(or my build environment is broken, dont tell me that pls)12:34
cpaelzermanual dh_... always calls for issues12:36
cpaelzerbuild in sbuild, if it fails you can login, if it doesn't \o/ and it will always be clean made fresh for you12:37
cpaelzer(if you have/want to build local)12:37
cpaelzerrafaeldtinoco: I have thrown it into a PPA, if it doesn't fail I'll mark it won't fix12:39
rafaeldtinocoyep, will do. thx and sorry if its just a noise12:39
=== ricab is now known as ricab|lunch
cpaelzernp rafaeldtinoco, I created enough nose with my quad-haproxy MPs going back and forther through two force pushes12:50
cpaelzerso I flooded all your inboxes, we are even I guess :-)12:50
* rafaeldtinoco looks at thunderbird and thx proper filters12:51
cpaelzerif paelzer then ->trash ?12:51
rafaeldtinococpaelzer: it also has "conversation" extension, showing only 1 mail per thread for me12:51
rafaeldtinocoand diff syntax highlight and compare extension12:52
rafaeldtinocothunderbird is pretty neat nowadays #)12:52
cpaelzerisn't grouping threads the default everywhere these days?12:52
rafaeldtinococpaelzer: yes, but not showing single lines per subject12:52
rafaeldtinocow/ no threads at all12:52
rafaeldtinocolike google does12:53
rafaeldtinococpaelzer: btw, i was checking qemu-arm folder12:53
rafaeldtinocothere wasn't a closure on the barrier subject, right ?12:53
cpaelzernot yet12:53
cpaelzerstuck on upstream discussion12:53
cpaelzerI haven't seen a major breakthrough12:53
rafaeldtinocomy assumption is that marvell is still investigating12:53
cpaelzerthe last active participant was Jan Glauber IIRC12:53
rafaeldtinocowhy the data alignment caused mitigation (or not)12:53
rafaeldtinoco(changing u32int -> u64int and so)12:54
cpaelzerI had that on my radar as "waiting on upstream / waiting on partner" or is/was there pressure on you to go haead?12:54
rafaeldtinocono pressure, just missed the discussion12:54
rafaeldtinocoi re-thought "maybe some conclusion happened and Im not aware of "12:55
rafaeldtinocobut reading last emails, all I can see is that memory alignment changes behavior (likely because of cache alignment and cpu <-> coherency)12:55
cpaelzeryep, they invalidate separately then12:55
rafaeldtinococausing more overhead for the HW sync (or less overhead) and making it more or less frequently12:55
cpaelzerbut that is not "a solution"12:55
rafaeldtinocook, my understanding is right then12:56
cpaelzerdoko: you asked for python-tornado yesterday as it triggers issues with python 3.8 rebuilds13:06
cpaelzerI think it is important to see that there is a newer 6.x but that was turned back to allow dependencies to follow13:06
cpaelzernever the less look at the changelog https://metadata.ftp-master.debian.org/changelogs//main/p/python-tornado/python-tornado_6.0.3+really5.1.1-1_changelog13:06
cpaelzergood old mwhudson has a change that sounds rather related "Bump ASYNC_TEST_TIMEOUT when running the autopkgtests as well"13:07
cpaelzeror do we have that already ...13:08
cpaelzeroh yeah, :-/ our Delta has that already13:09
cpaelzergrml, I thought this might be easy ...13:09
EickmeyerLocutusOfBorg: 1) It's tagged eoan, and 2) Doesn't really need sponsorship as I have PPU on the package. Just needs the green light.13:09
cpaelzercoreycb: he pinged you as well, please tell me that you have looked more at it and know what it is :-)13:12
coreycbcpaelzer: hey sorry I've not had a chance to look yet13:12
coreycbcpaelzer: let me wrap a few things up and look13:13
cpaelzersure, thanks for looking as well then13:15
cpaelzerif you also don't see what might be going on let me know, then we can bang our head against the wall together13:15
LocutusOfBorgEickmeyer, this is not usually how SRU are done13:23
LocutusOfBorg1) you have to first fix focal13:23
LocutusOfBorg2) you have to correctly use "target to series"13:24
EickmeyerLocutusOfBorg: Upload is in queue for focal.13:24
LocutusOfBorgok so please wait for it to migrate before uploading to eoan13:24
LocutusOfBorg[Regression Potential]13:24
LocutusOfBorg * None, simply adds a build dependency and patch to existing package13:24
EickmeyerOk. I don't have the ability to target to series.13:24
LocutusOfBorgmeh, adding a new dependency has a lot of side effects13:25
LocutusOfBorge.g. enables code that wasn't built, changes behaviour and so on13:25
LocutusOfBorgyou might change this to "the current package is completely broken", adding the dependency makes it less sucky13:25
LocutusOfBorgif this is true13:25
LocutusOfBorgor try to see what changes in the build system in case the dependency is found13:25
cpaelzercoreycb: I tried a few local build (maybe that helps you to find the right start): 6.0.3@unstable (worked), 5.1.1@eoan (worked), 5.1.1@focal (the reported timeouts), 5.1.1@focal-proposed (the reported timeouts), 6.0.3@focal-proposed (dependency issues)13:26
LocutusOfBorge.g. you could change it with something like "adding libsndfile enable the detection of various new plugins, otherwise unsupported, with the HAVE_SNDFILE preprocessor directive13:28
EickmeyerLocutusOfBorg: Unfortunately, that's not the case. It simply allows certain synthesizer plugins to actually make sound, which they weren't before.13:28
LocutusOfBorgthis list includes: aif aifc aiff au bwf flac htk iff mat4 mat5 oga ogg paf pvf pvf5 sd2 sf snd svx vcc w64 wav xi13:28
LocutusOfBorgEickmeyer, in any case, please try to be more verbose on the regression potential task, because it makes easier for release team to ack/nack the change13:30
LocutusOfBorgin any case, LGTM13:30
EickmeyerLocutusOfBorg: Thanks.13:30
cpaelzercoreycb: but since doko disabled the tests to be gating yo'll have to switch these back if you want to break on them13:37
cpaelzerthey are always triggered, just no more making the build fail13:37
=== ricab|lunch is now known as ricab
rbasakcpaelzer: when you have a couple of minutes, I'd like to chat about next steps for your armhf emulation branch please. More a process for adjustments since I'm juggling branches. Discussion of the technical details we can discuss in the MP.14:18
cpaelzerrbasak: is the standup hangout ok ?14:19
cpaelzercoreycb: in a failing build env you can switch between good/bad behavior by switching /usr/bin/python3 between 3.7 and 3.814:22
rbasakcpaelzer: you mean now or at standup time?14:22
coreycbcpaelzer: ok thanks. sorry working on charm release as well.14:22
coreycbcpaelzer: just starting to dig in14:22
cpaelzercoreycb: no problem, I just though I kept you posted on how far I get working a bit on it in background14:23
cpaelzercoreycb: to allow you a head start later on14:23
cpaelzerIf I find the time to do more I'll ping yu again14:23
=== ricab is now known as ricab|bbl
tseliottjaalton, hi, I have updated nvidia 430 and 435 for this SRU. The nvidia-settings package is not ready yet, unfortunately14:36
tseliottjaalton, but I think I'll hold that off until the next nvidia update14:36
tjaaltontseliot: was this a request to review them? :)14:40
tseliottjaalton, yes please, also, since you asked me about the SRU the other day14:41
tjaalton435 is in new, also the previous upload14:42
tseliottjaalton, oh, so that was never approved14:45
tjaaltonor looked at14:46
tseliotvorlon, ^^14:46
tjaaltonI was able to ack it from the new queue, the old one14:47
tjaaltonnow it should show a diff for the new upload :P14:47
tseliotgood, thanks14:49
blackboxswhi folks: probably a newbie schroot issue... I'm trying to share a directory into my schroot for collecting and sharing data after I destroy/clean the chroot for post-processing during an SRU test.   From `schroot --config` I can see my chroot base directory from the host and I `sudo mkdir ./host-data/subdir  $CHROOT_DIR/data; sudo mount -o bind ./host-data  $CHROOT_DIR/data; schroot -c <my-schroot> -- ls15:13
blackboxswThe issue ^ is that I don't see the "subdir" from within the chroot's "/data" and any files i write there are also not persisted outside on the hostfs/host-data dir15:14
vorlontseliot: sorry, I can't tell from context what the request is15:31
LocutusOfBorgcpaelzer, did you try the newer vbox for audio issues?15:35
LocutusOfBorgI mean, https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/184074915:35
ubottuLaunchpad bug 1840749 in virtualbox (Ubuntu) "Sound problems since 5.2.18" [Wishlist,Confirmed]15:35
LocutusOfBorgmaybe my prod to upstream worked15:35
cpaelzerLocutusOfBorg: I didn't yet as  6.0.12 was failing hard15:44
cpaelzerLocutusOfBorg: is there a newer one or a rebuild of 6.0.12 that is worth trying?15:44
cpaelzerrbasak: I have tested the uvtool branch, found two needs for fixups but now it is good15:51
cpaelzerrbasak: https://code.launchpad.net/~paelzer/uvtool/+git/uvtool/+merge/367641 contains what you need15:51
cpaelzerit is your branch + the two fixups15:51
cpaelzerThat I think you can merge now15:51
cpaelzertest results in the MP15:51
ahasenackLaney: hi, is there a way to get the logs for the arm64 test that says "always failed" in this bileto ticket? https://bileto.ubuntu.com/excuses/3830/trusty.html15:51
ahasenackit's not showing up in /running15:51
cpaelzerLocutusOfBorg: I see 6.0.14 I'll give it a try after dinner15:52
Laneyahasenack: "(always failed)" there means that there's no previous passes so it can't be a regression no matter what this run results in: http://autopkgtest.ubuntu.com/packages/ubuntu-advantage-tools15:55
ahasenackLaney: but is there a current result?15:55
LaneyI dunno, britney should show that if there is15:56
ahasenackmaybe I should trigger it again, then the previous run will be this current one, and then it can show me something?15:56
ahasenackswitched the lander signoff to failed and back to approved15:57
Laneyhow long has it been since it ran?15:57
ahasenackLaney: I queued it at 14:51utc15:57
Laneyfrom the timestamp in https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty-ci-train-ppa-service-3830/trusty/amd64/u/ubuntu-advantage-tools/20191023_151338_fe98b@/log.gz I'm thinkning you should be a little bit more patient15:57
ahasenackwhen it actually started I don't know15:57
=== ricab|bbl is now known as ricab
Laneyyou can do some URL hacks though15:59
Laneye.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty-ci-train-ppa-service-3830/?format=plain&prefix=trusty/15:59
Laneyleads you to https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty-ci-train-ppa-service-3830/trusty/arm64/u/ubuntu-advantage-tools/20191023_153416_fe98b@/log.gz15:59
ahasenackso arm64 is done and green15:59
Laneylooks like it16:00
Laneybut proposed-migration will get that next time16:00
ahasenackok, thanks16:02
LocutusOfBorgcpaelzer, TBH there is also a 5.2.34 in unapproved queue16:03
LocutusOfBorgor here16:04
blackboxswok, figured out the schroot bind mount problem  on my end. I was using mk-sbuild to create the schroot which sources /etc/schroot/sbuild/fstab config to setup mounts within the schroot instead of the typical /etc/schroot/default/fstab. Adding proper bind mount fstab declarations in /etc/schroot/sbuild/fstab got me the proper bind mounted /data dir in the sbuild-created schroot.16:11
doko#if !defined(X86) && !defined(X86_64)16:20
doko#   if defined(__x86_64__) || defined(__x86_64)16:20
doko#       define X86_6416:20
doko#   elif defined(__i386__) || defined(__i386) || defined(_M_I86) || defined(_M_IX86)16:20
doko#       define I38616:20
doko#   else16:20
doko#       error Unrecognized architecture!16:20
doko#   endif16:20
dokoso 2019 ...16:20
xnoxfollowed by inefficient assembly ?16:28
coreycbcpaelzer: python-tornado 6.0.3-1 package runs py38 tests successfully on focal without the missing dependency python-sphinxcontrib.asyncio. I'll check with Julien to see if he knows if that package is in the works.17:55
coreycbdoko: are there any plans for backporting python 3.8 to bionic?17:59
dokocoreycb: yes, see #1835737. but the interpreter only. and I'm currently busy with the archive opening18:14
dokojamespage also asked for it18:14
coreycbdoko: thanks in advance, that'll be very helpful. he'd mentioned it briefly. and no rush.18:20
kyrofaHey folks, quick question about rmadison: if it says "bionic/universe" it's pretty obvious that's in universe. Can someone confirm that if it just says "bionic" that means it's main? Any other component will be <repo>/<component>?18:23
infinitykyrofa: Indeed, no component is main, all others will list one.  See, eg: nvidia-driver-430 in focal/restricted.18:56
infinitykyrofa: This mirrors what you find in "Section" in the Packages headers (ie: apt-cache show $foo | grep ^Section), where main just shows the section, and others show component/section.18:57
infinityI've been tempted to change rmadison to be explicit about main (not the first time this has been asked :P), but I'm pretty sure that would break any number of home-grown scripts I don't know about, so best not to.18:58
infinitykyrofa: Arguably, this makes a lot more sense in Debian, where "main" is "basically everything" and "contrib" and "non-free" are "some bits we don't really care about because ew, licenses". :P19:00
infinityBut we use the same tools, and I don't think it occurred to any of us that the presentation should be different for Ubuntu until it was too late to change it.19:01
kyrofainfinity, makes total sense, thank you!19:03
mwhudsonxnox, doko: so um, it turns out numpy builds have been ignoring test suite results for years, both in debian and ubuntu :/20:56
mwhudsoni guess it's reportbug -B debian time20:57
mwhudsonafter coffee and meeting20:57
dokoplease both numpy and python-numpy20:57
mwhudsonah yeah20:58
dokopython-numpy (1:1.9.2~rc1-1) experimental; urgency=medium20:58
doko  * debian/rules20:59
doko    - don't ignore failures when running unittests; Closes: #72110020:59
mwhudsonlet's say i'm not convinced that is true21:04
xnoxmwhudson:  yes, but this one is very bad =)22:24
mwhudsonxnox: indeed22:24
xnoxmwhudson:  as in there clearly is s390x regression there. I did open a bug about it.22:25
xnoxmwhudson:  you find it, right?22:25
mwhudsonxnox: yes22:25
xnoxthat's all there is for now =)22:25
mwhudsonwell the report yes, bug no22:25
mwhudson    x2 = np.array([0.0, 1.0, 2.0], ndmin=2)22:26
mwhudsonE   ValueError: ndmin bigger than allowable number of dimensions NPY_MAXDIMS (=32)22:26
mwhudsonat least if it's that simple to reproduce it shouldn't be too hard to diagnose, surely22:27
xnoxclearly 2 is miss-endianed22:32
xnoxor something else inside22:32
xnoxgit bisect would be nice here22:33
LocutusOfBorgmitya57, how is the bootstrap going? looks like idle?22:41
mwhudson-    int ndmin = 0, nd;22:42
mwhudson+    int nd;22:42
mwhudson+    npy_intp ndmin = 0;22:42
mwhudsoni presume npy_intp is going to turn out to not be an int22:42
mwhudsonwe can pass a long pointer to something expecting an int* right? it'll be fiiiine22:43
sarnold"oh that compiler warning doesn't mean anything go ahead and ignore that"22:43
mwhudsonwell luckily this is all passed to a variadic function22:44
mwhudsonso no pesky compiler warnings at all!!22:44
sarnoldooh clever way to Improve Development Velocity!22:46
mwhudsonyeah npy_intp ends up being intptr_t22:48
mwhudsonhey hey guess what the offending commit message is!22:49
mwhudson"MAINT: Minor fixes and cleanups"22:49
sarnoldwell discovered :)22:52
mwhudsonupstream bug https://github.com/numpy/numpy/issues/1476723:08
mwhudsontesting patch in my ppa now23:15

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