/srv/irclogs.ubuntu.com/2020/11/20/#ubuntu-release.txt

vorlonis pyyaml built against python3-dev instead of python3-all-dev?00:02
vorlonwe might want to fix that for future proofing00:03
vorlon(that would also let pyyaml migrate now without python3-defaults, and make things less horrible)00:03
vorlonhmm it already build-depends on python3-all-dev and should be installable, but the -proposed version with python3.9 support hasn't migrated yet00:06
-queuebot:#ubuntu-release- New binary: libmatio [s390x] (hirsute-proposed/universe) [1.5.19-2] (no packageset)00:27
-queuebot:#ubuntu-release- New: accepted libmatio [amd64] (hirsute-proposed) [1.5.19-2]00:35
-queuebot:#ubuntu-release- New: accepted libmatio [riscv64] (hirsute-proposed) [1.5.19-2]00:35
-queuebot:#ubuntu-release- New: accepted libmatio [ppc64el] (hirsute-proposed) [1.5.19-2]00:35
-queuebot:#ubuntu-release- New: accepted libmatio [s390x] (hirsute-proposed) [1.5.19-2]00:35
-queuebot:#ubuntu-release- New binary: nvidia-cuda-toolkit [ppc64el] (hirsute-proposed/multiverse) [11.1.1-2] (no packageset)01:22
-queuebot:#ubuntu-release- New binary: vtk9 [amd64] (hirsute-proposed/universe) [9.0.1+dfsg1-1] (no packageset)01:54
-queuebot:#ubuntu-release- New binary: vtk9 [s390x] (hirsute-proposed/universe) [9.0.1+dfsg1-1] (no packageset)02:32
vorlonghc migrated \o/02:35
vorlon(that's a thousand less packages for britney to nag me about)02:35
mwhudsonyay02:46
mwhudsonscipy still looks pretty unhappy02:48
mwhudsonmaybe that's a job for monday02:48
-queuebot:#ubuntu-release- New binary: vtk9 [ppc64el] (hirsute-proposed/universe) [9.0.1+dfsg1-1] (no packageset)02:55
-queuebot:#ubuntu-release- New: accepted vtk9 [ppc64el] (hirsute-proposed) [9.0.1+dfsg1-1]03:57
-queuebot:#ubuntu-release- New: accepted vtk9 [s390x] (hirsute-proposed) [9.0.1+dfsg1-1]03:57
-queuebot:#ubuntu-release- New: accepted nvidia-cuda-toolkit [ppc64el] (hirsute-proposed) [11.1.1-2]03:57
-queuebot:#ubuntu-release- New: accepted vtk9 [amd64] (hirsute-proposed) [9.0.1+dfsg1-1]03:57
-queuebot:#ubuntu-release- New binary: libpgm [s390x] (hirsute-proposed/universe) [5.3.128~dfsg-2] (i386-whitelist, kubuntu)04:40
-queuebot:#ubuntu-release- New binary: libpgm [amd64] (hirsute-proposed/universe) [5.3.128~dfsg-2] (i386-whitelist, kubuntu)04:40
-queuebot:#ubuntu-release- New binary: libpgm [ppc64el] (hirsute-proposed/universe) [5.3.128~dfsg-2] (i386-whitelist, kubuntu)04:40
-queuebot:#ubuntu-release- New binary: libpgm [i386] (hirsute-proposed/universe) [5.3.128~dfsg-2] (i386-whitelist, kubuntu)04:40
-queuebot:#ubuntu-release- New binary: libpgm [riscv64] (hirsute-proposed/universe) [5.3.128~dfsg-2] (i386-whitelist, kubuntu)04:59
-queuebot:#ubuntu-release- New: accepted libpgm [amd64] (hirsute-proposed) [5.3.128~dfsg-2]05:37
-queuebot:#ubuntu-release- New: accepted libpgm [ppc64el] (hirsute-proposed) [5.3.128~dfsg-2]05:37
-queuebot:#ubuntu-release- New: accepted libpgm [s390x] (hirsute-proposed) [5.3.128~dfsg-2]05:38
-queuebot:#ubuntu-release- New: accepted libpgm [i386] (hirsute-proposed) [5.3.128~dfsg-2]05:38
-queuebot:#ubuntu-release- New: accepted libpgm [riscv64] (hirsute-proposed) [5.3.128~dfsg-2]05:38
cpaelzerHi doko, could the recent https://launchpad.net/ubuntu/+source/python3-defaults/3.9.0-3 cause "Missing build dependencies: python3 (< 3.9)" due to indirect dependency breakage?06:43
tumbleweedsounds like something that needs a rebuild against python3.9 as default06:44
cpaelzeryeah, but the package that broke for me has no python* in deps - so it must be one of the base set of common build dependencies06:45
cpaelzerI'm checking which one it is and if a rebuild might already be in progress06:45
cpaelzerBD -> sssd-common -> python3-sss it is06:48
cpaelzer python3-sss : Depends: python3 (< 3.9) but 3.9.0-3 is to be installed06:48
rbalintplusone doing +1 today, too, for a few hours because i lost a few hours on wednesday in my shift to regular work06:49
cpaelzerhi rbalint06:49
rbalintcpaelzer, o/06:50
cpaelzerusually the one driving the transition is doing the rebuilds against the new version - I'm not interfering by triggering an sssd rebuild now as something might not yet be ready06:50
rbalintmwhudson, scipy looks just a hint away from release pocket, that's not bad :-)06:54
rbalintmwhudson, hm, no, it is failing dask, indeed06:59
rbalintplusone looking at r-base07:09
dokoyes, but builders in a very bad shape07:10
dokocpaelzer: sssd requires samba ...07:19
cpaelzerlife is a circle .. of bugs07:22
cpaelzersergiodj: ^^ FYI07:23
cpaelzerdoko: even the rebuild of sssd needs samba?07:23
dokoaccording to the transition tracker, yes07:23
cpaelzer / sigh07:23
dokosergiodj: tdb/s390x ftbfs would need investigation first07:32
dokooSoMoN: I'm not uploading LO for python 3.9 before the datacenter move07:46
dokotdb/s390x succeeded on retry07:51
=== Guest16270 is now known as _hc
dokoLaney: is britney happily running for 4h?09:49
dokoLaney, juliank: are the ppc64el autopkg testers alive?09:50
LocutusOfBorga new run just started09:50
julianklet's look09:50
Laneydoko: just for information, you can see the same logs as me https://people.canonical.com/~ubuntu-archive/proposed-migration/log/hirsute/2020-11-20/09:50
LaneyI can't look, on a call, will check later09:51
juliankdoko: ppc64el workers are running, yes09:51
juliankthe bos02 ones09:51
juliank20 workers09:52
juliankthat's all we have atm, normally we have 20 more workers in bos0109:54
dokoLaney: ahh, ok so the 7am run timed out with urllib.error.URLError: <urlopen error _ssl.c:629: The handshake operation timed out>09:55
dokoand the current one still running09:55
Laneyright09:56
Laneyand that code already has retries, so ...09:57
Laneymaybe there was downtime ?09:58
-queuebot:#ubuntu-release- New binary: linux-signed-azure-4.15 [amd64] (bionic-proposed/main) [4.15.0-1100.111] (no packageset)09:58
dokoat least buildd outage, that's why I was asking about the autopkg testers as well09:58
Laneydifferent DC AFAIK10:00
-queuebot:#ubuntu-release- New: accepted linux-signed-azure-4.15 [amd64] (bionic-proposed) [4.15.0-1100.111]10:25
Laneyjust thought11:03
Laneythe email policy should catch that exception and just warn shouldn't it11:04
Laneyrather than crashing the whole run, failing to be able to send an email isn't that bad11:04
-queuebot:#ubuntu-release- New binary: php-gettext [amd64] (hirsute-proposed/none) [1.0.12-1] (no packageset)11:20
Laneyah since pyyaml migrated, I guess I can retry those /unknown results ?11:32
Laneydoko: ^ right?11:32
dokoLaney: why was pyyaml needed?11:36
Laneyubuntu-minimal transitively depends on it11:36
Laneyvia netplan possibly, I didn't look11:36
dokosure, I think I only gave back a handful of unknown's this morning11:37
Laneyok, I have some code here to add a --only-unknown to retry-autopkgtest-regressions11:37
LaneyI'll push that11:38
juliankLaney: we should force-skiptest dbus-python/1.2.16-4 so it can migrate? software-properties doesn't seem to work on armhf right now, and we need the new dbus-python to unbreak aptdaemon in release pocket11:48
juliankFor completeness: aptdaemon has python3.9 shebangs, but dbus-python in release pocket is not built for 3.9 yet, causing it to fail11:49
juliankaptdaemon needs to run some extra debhelper that does the shebang rewriting11:50
juliankso future versions get unversioned shebangs11:50
juliankI think11:51
juliankI thought dh_python3 did that11:51
juliankconfusing11:52
Laneyhttps://autopkgtest.ubuntu.com/packages/s/software-properties/hirsute/armhf11:53
Laneywhy did everyone just spam retry on that multiple times11:53
Laneyjuliank: feels like a reset-test or badtest for s-p/armhf?11:54
juliankLaney: maybe, but it looks like launchpad issues today and I don't want to make a general call on that11:54
Laneydon't understand what you mean there11:55
rbalintLaney, i triggered r-bioc-sva/ppc64el and it may have lost11:55
rbalintLaney, you said that i should not retry in those cases, could you please take a look?11:56
cjwatsonjuliank: What do Launchpad issues have to do with autopkgtests?11:56
rbalintLaney, the trigger was hello11:56
cjwatsonOh right, 403s from ppa.launchpad.net11:57
juliankYeah, 403s I think and some timeouts11:57
juliankI haven't looked at all of them11:57
rbalintweren't those proxy issues?11:57
cjwatsonNot so much Launchpad issues per se, but there's been GS2 network maintenance this morning11:57
cjwatsonAlmost certainly that11:57
juliankI don't know, but possible11:57
cjwatsonIt's supposed to be over for the time being, but it's part of preparing for the Boston datacentre move11:58
Laneyrbalint: I don't believe you did trigger that11:59
juliankso Laney what I meant is that I did not look at the other issues and I think it might be temporary, so i was thinking about only getting that urgent dbus-python fix so aptdaemon works again11:59
juliankbecause I think the others did not cause that crazy regressions likely :D11:59
juliankbut yeah, force-reset-test I guess would work12:00
Laneyrbalint: The only mention of that package name in access.log is a s390x from bing which we 403ed12:01
Laneythanks very much bing12:01
Laneyjuliank: reset-test feels good, I will do that12:01
rbalintLaney, thanks, interesting12:05
rbalintLaney, oh, it was yesterday12:06
rbalintLaney, i triggered r-bioc-sva/s390x that went through12:07
Laneyright, there's no 'hello' request from yesterday either12:08
Laneyubuntu@juju-prod-ues-proposed-migration-machine-2:~$ egrep request.*ppc64el.*r-bioc-sva.*hello /var/log/apache2/access.log.112:08
Laneyubuntu@juju-prod-ues-proposed-migration-machine-2:~$12:08
Laneybut your other three(!) requests are all in the log12:09
rbalintLaney, interesting, thanks12:13
Laneyrbalint: btw, you should know about retry-autopkgtest-regressions --no-proposed I guess, instead of using 'hello12:25
Laney'12:25
Laneyok retried all the unknowns12:28
rbalintLaney, thanks, but hello works for packages in proposed12:33
Laneyright12:39
Laneyare you planning to automate this or do it regularly?12:40
rbalintLaney, no, i just use it to mass trigger a range of failures, usually in combination with --log-regex  or with  | grep package=...12:44
Laneyright, I'm worried you are implementing baseline retesting from the outside12:45
dokoEickmeyer[m]: https://launchpadlibrarian.net/507846803/buildlog_ubuntu-hirsute-amd64.agordejo_0.1.1-0ubuntu2_BUILDING.txt.gz12:45
Laneyif not then ok12:45
rbalintLaney, could you please check https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/394180 for rbase and others?13:23
rbalintLaney, also https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/39420913:23
slyonMay I bring this i386-whitelist change request to any AAs attention? https://bugs.launchpad.net/ubuntu/+source/pycryptodome/+bug/190498713:55
ubot5Ubuntu bug 1904987 in pycryptodome (Ubuntu) "Please add this package to i386-whitelist" [Undecided,New]13:55
rbalintsil2100, could you please check the merges i pinged Laney with?14:26
rbalintplusone r-base should be ready to migrate after the hints are merged14:28
rbalintcpaelzer, retried cyrus-imapd/amd64 because is was still sad14:46
sil2100rbalint: looking in a moment14:46
sil2100slyon: and here as well14:46
slyonsil2100: thanks o/ AFAIU a no-change rebuild is needed after the package is accepted into the whitelist. Debdiff is attached to the bug14:48
-queuebot:#ubuntu-release- Unapproved: s390-tools (xenial-proposed/main) [1.34.0-0ubuntu8.10 => 1.34.0-0ubuntu8.11] (no packageset)15:14
rbalintsil2100, added more hints15:17
cjwatsons390x builders are going down shortly for the DC move - I've put them all on manual15:18
Laneyrbalint: sorry, I'm on a call15:18
Laneybut yes, I should do that with autopkgtest workers too15:19
sil2100rbalint: ok, looking at it now anyway15:19
sil2100slyon: will sponsor in a moment!15:20
Laneyok, s390x autopkgtesters off too15:21
sil2100rbalint: and what's up with ganeti? I don't see it having any i386 binaries?15:24
sergiodjdoko: would it be possible to file bugs for what you want me to do?  I'm very busy with other stuff right now, but taking care of samba & sssd are definitely at the top of my TODO list15:30
rbalintsil2100, test is still listed as regressing for ganet/proposed15:31
dokosergiodj: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/190504815:33
ubot5Ubuntu bug 1905048 in samba (Ubuntu) "samba ftbfs in hirsute, needs merge" [High,Confirmed]15:33
vorlonhowever, --no-proposed fails if the package being triggered has a version in -proposed15:35
vorlonLaney, rbalint: ^^15:35
Laneyyeah, the doc string notes that15:36
Laneymigration-reference/0!15:36
rbalint+115:36
rbalintuntil then hello is good enough15:36
* vorlon nods15:48
=== Laney changed the topic of #ubuntu-release to: Released: Groovy 20.10, Focal 20.04.1, Bionic 18.04.5 | Archive: Open but no s390x | Highlight ubuntu-archive for archive admin help | Hirsute Release Coordination | We accept payment in cash, cheque or gin | melius malum quod cognoscis
-queuebot:#ubuntu-release- Packageset: Removed confuse from i386-whitelist in hirsute16:20
-queuebot:#ubuntu-release- Packageset: Removed ruby-setup from i386-whitelist in hirsute16:20
-queuebot:#ubuntu-release- Packageset: Added fonts-noto to i386-whitelist in hirsute16:20
-queuebot:#ubuntu-release- Packageset: Added fonts-noto-color-emoji to i386-whitelist in hirsute16:20
-queuebot:#ubuntu-release- Packageset: Added pycryptodome to i386-whitelist in hirsute16:20
-queuebot:#ubuntu-release- Packageset: Added sphinx-autoapi to i386-whitelist in hirsute16:20
-queuebot:#ubuntu-release- Packageset: Added unidecode to i386-whitelist in hirsute16:20
cpaelzerrbalint: the cyrus issue this adressed was only ppc6416:25
cpaelzerrbalint: I haven't looked at its amd64 results - might be a different issue there16:25
cpaelzerbut at least in the PKG that got me to cyrus only ppc64 failed, all other arches were ok16:25
dokoLaney, vorlon: are transition tracker updates running?16:41
rbalintsil2100, vorlon please merge to let us retry petsc4py https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/39420916:43
rbalintsil2100, vorlon Laney  i pressed retry, please merge before the package hits the workers16:45
rbalintis was queued anyway for python3-defaults16:45
dokoI call it a week ...16:45
Laneydoko: should be, I'll look in a minute, maybe something got stuck since there were network outages earlier16:46
sergiodjdoko: thanks16:47
Laneyrbalint: why press retry before it's merged? you'll just get it not run on a large instance.16:47
Laneyas just happened16:47
Laney:(16:47
rbalintLaney, i thought the mapping happens when it is picked from the queue16:51
Laneyit does16:51
rbalinti see no info on http://autopkgtest.ubuntu.com/running about queued items being mapped16:51
rbalintto length of vm sizes16:52
Laneybut now it's running16:52
Laneyand the thing is not merged16:52
rbalintLaney, could you please merge it?16:52
Laneyin a minute16:53
rbalintLaney, thanks16:53
Laneybut still, don't press the button until you get the merge in future please16:53
rbalintLaney, ok, but please merge quicker16:53
Laneyrbalint: didn't one of your earlier changes here fail to fix a failure? iirc16:53
* Laney shrugs16:53
Laneyif that's right, can you revert it please? having too many of these large tgests can be painful16:54
Laneythey take up 4x as much of our quota than regular ones16:54
rbalintLaney, that was a different package16:54
Laneywhich?16:55
rbalintLaney, cross-toolchain-base, checking16:56
Eickmeyer[m]doko: That means there was a fundamental change in Python between when I submitted the package (over two weeks ago!) and now. I'll let uptream know.16:59
Eickmeyer[m]THIS is why we need more efficiency for package reviews.16:59
rbalintLaney, i'd like to wait for a successful run of cross-toolchain-base because it passed after ~8 hours when using the small vm and this is a very significant delay in migration17:00
rbalintLaney, let's see how much time it needs to pass on a big vm17:01
Laneydelaying 3 other tests for the whole length of the run should also weigh into your reasoning17:02
Laneybut ok, if it is a significant gain then it could be justified17:03
Laneyrbalint: right, I see a ton of failures before your changes and a ton after, including a screenful of parallel large tests 😱 so I think you just managed to fail a *little* bit faster17:19
rbalintLaney, regarding failures my proposal is LP :#190391317:19
rbalintLaney, regarding failures my proposal is LP: #190391317:20
ubot5Launchpad bug 1903913 in Auto Package Testing "Don't run tests that never pass (or don't run tests with force-badtest)" [Undecided,New] https://launchpad.net/bugs/190391317:20
Laneyif it's forced, why are you bothered about retrying it?17:20
rbalintLaney, running on big vms will help with successful runs17:20
rbalintLaney, it got forced later17:21
Laneyrbalint: ok, since your bug there is not addressed atm I'm going to remove it from big_packages and once it is fixed and verified on arm64 e.g. using Canonistack please ping me back and we can look to re-add it then17:22
* rbalint shrugs17:23
Laneyif you've followed the logs and saw 'quota exceeded' as much as I have you'd also be concerned about controlling resource usage :-)17:24
Laneys/you've/you'd/17:24
rbalintLaney, then don't run the failing tests?17:26
rbalintLaney, i do care about making the most out of the quota but plaing with the big package list does not help as did not enough in the past years either17:27
rbalintLaney, what really helps is not running tests with no signal and pushing out excess tests to clouds17:27
Laneyyeah thanks, one thing is a task I can do in 5 seconds, the other takes thinking about, planning, testing and doing so they're not equivalent17:28
rbalintLaney, does not make the obsolete 5s task worth doing it17:28
Laneyit's not obsolete, not sure why you would say that17:29
Laneyanyway this feels like it's getting close to an argument, so I think we should both step away17:29
rbalintLaney, ok, the 5s task has a tiny tiny impact17:30
=== ijohnson is now known as ijohnson|lunch
rbalintLaney, sorry, just would like to improve the testing infra significally, let's discuss the bigger tasks at the next +1 meeting18:14
cjwatsonEickmeyer[m]: It would just show up in a test rebuild anyway, or maybe surprise you when you least expect it and you're trying to fix something else small - better to find out earlier :)19:42
-queuebot:#ubuntu-release- Unapproved: pcl (xenial-proposed/universe) [1.7.2-14build1 => 1.7.2-14build1.1] (no packageset)19:43
Eickmeyer[m]cjwatson: Agreed, but I still could've been on it sooner. Turns out upstream runs Arch which is still on Python 3.8 (ironically).19:43
mdeslaurhello SRU team, could someone please approve pcl in the xenial upload queue into -proposed, it's the second part of bug 157323419:44
ubot5bug 1573234 in pcl (Ubuntu Xenial) "unable to link: cannot find libvtkproj4" [Medium,Confirmed] https://launchpad.net/bugs/157323419:44
vorlondoko: what is the addition of libgtop2 for in update-i386-whitelist?19:46
vorlonmdeslaur: this is not a very reproducible test case20:01
vorlonmdeslaur: I shouldn't have to chase down build-dependencies one-by-one to reproduce the failure20:01
vorlon(and I'm taking a close look at this one because the idea of no-change SRU rebuilds magically fixing things makes me uneasy)20:02
LocutusOfBorgarm64/armhf/ppc64el jobs are failing with no logs20:04
LocutusOfBorgretrying doesn't help20:04
vorlonpossibly related to the datacenter move happening this weekend.  Those bits aren't scheduled to be moved yet but there could be transient network misconfigurations etc20:09
vorloncjwatson, wgrant: ^^ can you speak to the state of ARM/ppc64el builders in LP?20:09
vorlonmdeslaur: git clone of the referenced perception_pcl project, followed by manually futzing with build-deps, and then 'cmake pcl_conversions', gives me a makefile with an empty 'all' target.  I'm not willing to advance this without a cleaner test case20:13
=== ijohnson|lunch is now known as ijohnson
cjwatsonvorlon: Not specifically.  I can see logs that suggest network issues but don't know exactly what, and I'm also EOW - best ask IS20:26
cjwatsonBut it's all somewhat at risk at the moment due to network changes being made to prepare for the move20:28
vorlonright, thanks20:29
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.664.8 => 2.664.9] (desktop-core, i386-whitelist)20:39
mdeslaurvorlon: ok, thanks, I'll let the reporter know20:48
kyrofamdeslaur, vorlon: please take another look at the test case on bug 1573234, it's been greatly simplified and hopefully makes more sense21:00
ubot5bug 1573234 in pcl (Ubuntu Xenial) "unable to link: cannot find libvtkproj4" [Medium,Confirmed] https://launchpad.net/bugs/157323421:00
kyrofavorlon, note that the no-change rebuild propogates the dependency fix to properly use the system libproj instead of the vtk-vendored version, which isn't actually used by vtk at all21:02
kyrofavorlon, but pcl ended up with the vendored lib in its cmake config files21:02
kyrofavorlon, so the situation in Xenial right now is that vtk is built against the system libproj, but anyone linking against it tries to link against its vendored version21:10
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.61 => 2.408.62] (desktop-core)21:31
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.47 => 2.525.48] (desktop-core)21:34
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.61 => 2.408.63] (desktop-core)21:57
-queuebot:#ubuntu-release- Unapproved: ubuntustudio-menu (groovy-proposed/universe) [0.49 => 0.50~20.10.1] (ubuntustudio)22:57
Eickmeyer[m]^ SRU bug 190506122:57
ubot5bug 1905061 in ubuntustudio-menu (Ubuntu Groovy) "[SRU] Media Playback menu is overpopulated" [High,In progress] https://launchpad.net/bugs/190506122:57

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