[01:41] -queuebot:#ubuntu-release- Unapproved: golang-1.13 (xenial-proposed/universe) [1.13.8-1ubuntu1~16.04.2 => 1.13.8-1ubuntu1~16.04.3] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: golang-github-alecthomas-chroma [amd64] (hirsute-proposed/universe) [0.8.2-2] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: golang-github-alecthomas-chroma [ppc64el] (hirsute-proposed/universe) [0.8.2-2] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: golang-github-alecthomas-chroma [s390x] (hirsute-proposed/universe) [0.8.2-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: golang-github-alecthomas-chroma [arm64] (hirsute-proposed/universe) [0.8.2-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: golang-github-alecthomas-chroma [armhf] (hirsute-proposed/universe) [0.8.2-2] (no packageset)
[05:39] -queuebot:#ubuntu-release- New binary: golang-github-alecthomas-chroma [riscv64] (hirsute-proposed/universe) [0.8.2-2] (no packageset)
[07:16] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Focal 20.04.2.0] (20210208) has been added
[07:56] <sigv> sergiodj: Good morning from Europe - looks like my SRU did not get pushed yesterday afternoon. Guessing your additional SRU is still in the works. Today a better day?
[08:08] -queuebot:#ubuntu-release- New: accepted golang-github-alecthomas-chroma [amd64] (hirsute-proposed) [0.8.2-2]
[08:08] -queuebot:#ubuntu-release- New: accepted golang-github-alecthomas-chroma [armhf] (hirsute-proposed) [0.8.2-2]
[08:08] -queuebot:#ubuntu-release- New: accepted golang-github-alecthomas-chroma [riscv64] (hirsute-proposed) [0.8.2-2]
[08:08] -queuebot:#ubuntu-release- New: accepted golang-github-alecthomas-chroma [arm64] (hirsute-proposed) [0.8.2-2]
[08:08] -queuebot:#ubuntu-release- New: accepted golang-github-alecthomas-chroma [s390x] (hirsute-proposed) [0.8.2-2]
[08:08] -queuebot:#ubuntu-release- New: accepted golang-github-alecthomas-chroma [ppc64el] (hirsute-proposed) [0.8.2-2]
[10:20] -queuebot:#ubuntu-release- New binary: emscripten [amd64] (hirsute-proposed/universe) [2.0.12~dfsg-1ubuntu1] (no packageset)
[12:21] <juliank> ⚠ wiki.ubuntu.com will be offline shortly for brief hardware maintenance
[12:27] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (groovy-proposed) [5.8.0-1023.24]
[12:27] -queuebot:#ubuntu-release- New: accepted linux-signed-kvm [amd64] (groovy-proposed) [5.8.0-1019.21]
[12:35] <Laney> sil2100: I guess we're mainly waiting for iso testing now?
[12:47] <juliank> wiki is back
[12:52] <sil2100> Laney: yeah, as much testing as possible
[12:53] <sil2100> Already poked jibel and did some testing too
[12:58] <jibel> Laney, we cannot cover oem stuff more than you can. I can only test in VMs
[12:58] <jibel> s/we/I
[12:59] <Laney> yeah
[12:59] <Laney> timing is pretty bad for that
[13:24] <sil2100> Yeah
[13:30] <rbalint> Laney, how did the systemd tests go?
[13:30] <coreycb> sil2100: hello, if you have any sru cycles, we'd like to see if we can get cinder (bionic->groovy unapproved queues) reviewed.
[13:31] <Laney> ongoing
[13:31] <Laney> rbalint: I'm running a few times, it still seems flaky to me on m1.large though, but wait a bit
[13:32] <rbalint> Laney, flaky sounds better, it has been failing pretty consistently :-
[14:10] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (groovy-proposed/main) [5.8.0-1023.25] (core, kernel)
[14:10] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (groovy-proposed/main) [5.8.0-1021.22] (core, kernel)
[14:11] -queuebot:#ubuntu-release- New binary: linux-signed-azure-4.15 [amd64] (bionic-proposed/main) [4.15.0-1108.120] (no packageset)
[14:25]  * sil2100 runs some test installs of flavors
[14:46] <Laney> rbalint: umm
[14:52] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (groovy-proposed) [5.8.0-1023.25]
[14:52] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (groovy-proposed) [5.8.0-1021.22]
[14:52] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-4.15 [amd64] (bionic-proposed) [4.15.0-1108.120]
[14:54] <sergiodj> sigv: hey, yeah, I'm finishing the tests here, since I'm joining 2 SRUs in the same upload.  but it should be done today
[14:55] <sigv> sergiodj: awesome - depending on the time they get uploaded, should be able to do verification either today or tomorrow.
[14:56] <sergiodj> sigv: the upload is the first step, then it will depend on how long it will take for the SRU team to process it, and then you can do the verification.  so maybe it'll take a few days :)
[14:56] <sigv> sergiodj: oh, ohh. got it - well, will do verification.. in the near future then :)
[14:56] <sergiodj> sigv: awesome :)
[14:59] -queuebot:#ubuntu-release- Unapproved: cinnamon-screensaver (focal-proposed/universe) [4.4.1-3 => 4.4.1-3ubuntu0.1] (no packageset)
[14:59] -queuebot:#ubuntu-release- Unapproved: cinnamon-screensaver (groovy-proposed/universe) [4.6.0-2 => 4.6.0-2ubuntu0.1] (no packageset)
[14:59] -queuebot:#ubuntu-release- Unapproved: cinnamon (focal-proposed/universe) [4.4.8-4ubuntu0.1 => 4.4.8-4ubuntu0.2] (no packageset)
[14:59] -queuebot:#ubuntu-release- Unapproved: cinnamon (groovy-proposed/universe) [4.6.7-1ubuntu1 => 4.6.7-1ubuntu1.1] (no packageset)
[15:06] -queuebot:#ubuntu-release- Unapproved: wireguard-linux-compat (bionic-proposed/universe) [1.0.20201112-1~18.04.1 => 1.0.20201112-1~18.04.2] (kernel-dkms)
[15:18] <sil2100> Laney, jibel: did any of you manage to run some more testing on at least some mocked OEM-enabled devices? I'm doing a quick sanity run of studio now
[15:21] <Laney> sil2100: I did a bunch yeah, didn't find any problems but I don't feel like they are too much like real systems without faking other bits too
[15:21] <Laney> and I have one real XPS certified system that I installed in various ways too
[15:21] <Laney> that's non nvidia though
[15:22] <Laney> maybe I should have followed the ISO tracker testcases and I could have logged results, sorrrrrrrrrrrrrrrrrrrryyyyy
[15:28] <jibel> sil2100, not more than I already did this morning and make sense to run in VMs.
[15:29] <sil2100> Laney: we'll work in the nearest time on adding some OEM presence to the isotracker, might make things easier
[15:29] <sil2100> jibel, Laney: thanks
[15:29] <sil2100> I guess there's only this much we can do now
[15:29] <sil2100> I'll poke the flavors for status updates and I guess that's it
[15:29] <Laney> We could ask the original reporter to re-verify I guess
[15:31] <Laney> although they probably don't want to reinstall their system after spending 2 days fixing it ¬_¬
[15:31] <Laney> ok scratch that idea
[15:34] <jibel> sil2100, it'd be better to add tests to the testsuite of ubiquity.
[15:34] <jibel> than manual tests to the tracker
[15:34] <Eickmeyer> sil2100: Doing a sanity run of Studio myself.
[15:34]  * Eickmeyer is moving, so somewhat incommunicado
[15:35] <sil2100> jibel: +1 on that, I didn't recommend that as I have no knowledge of the test suite for ubiquity, how it works and what testing it performs
[15:36] <sil2100> We anyway would like to have something on the ISO tracker for the case when certification is able to perform all the testing on real hardware
[15:37] <sil2100> Since until we have automated testing on the actual hardware, we'll still need cert to do manual testing on those, since the VM mocks are just like a sanity test
[15:43] <xnox> sil2100:  can https://launchpad.net/ubuntu/+source/s390-tools/2.15.1-1ubuntu1 be please approved in the unapproved queue in hirsute?
[15:47] <sigv> sergiodj: did you decide whether you are doing a Bionic upload for LP: #1908065 in the end?
[15:47] <ubot5> Launchpad bug 1908065 in sssd (Ubuntu Hirsute) "Invalid SYSLOG_PID for (systemd) journal messages" [Low,Triaged] https://launchpad.net/bugs/1908065
[15:47] <sil2100> xnox: looking
[15:47] <sergiodj> sigv: I'll talk to one of the SRU team members soon about this
[15:47] <sigv> ok
[15:47] <sil2100> xnox: done o/
[15:48] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (hirsute-proposed) [2.15.1-1ubuntu1]
[15:49] <LocutusOfBorg> also please accept emscripten
=== _lucasmoura is now known as lucasmoura
[16:34] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.2.0] has been marked as ready
[16:34] <Eickmeyer> sil2100: ^ I'm good with it.
[16:34] <sil2100> \o/
=== cpaelzer__ is now known as cpaelzer
[16:43] <juliank> Laney: I think we talked once about adding more diskspace to autopkgtest-lxd-worker such that we can have more workers on there?
[16:43] <juliank> like cloud worker we mounted a huge thingy for additional space
[16:44] <Laney> juliank: yeah
[16:44] <Laney> you can either kill all the in progress jobs and do it now
[16:45] <Laney> or wait until it's empty ish and do it then
[16:45] <Laney> stg-proposed-migration does this automatically from the juju bundle :>
[16:45] <juliank> there are 2500 jobs in the queue still, that's why people are annoyed :)
[16:45] <juliank> because they want more armhf workers :D
[16:45] <juliank> which needs that space :)
[16:46] <Laney> well feel free to do it if you want
[16:46] <Laney> I wouldn't expect miracles though, you're just adding more to the same underlying hosts in the end
[16:46] <Laney> and e.g. network I/O is a significant factor and that is just fixed
[16:47] <Laney> until we can have multiple controllers :>
[16:48] <doko> aren't arm64 and armhf using the same underlying hosts?
[16:48] <Laney> they are
[16:49] <doko> so why is it more I/O?
[16:49] <Laney> from the controller to the systems running the tests
[16:49] <Laney> uploading and downloading the source, binaries if builds are needed
[16:49] <juliank> But like cloud worker does all other archs shouldn't it have far more I/O issues?
[16:49] <Laney> it does sometimes
[16:50] <doko> network I/O, not disk I/O for the tests itself
[16:50] <juliank> I must say I don't know how to add a second disk to the lxd-worker
[16:50] <Laney> using cinder, create a volume matching the other one
[16:50] <Laney> attach it to the instance, mount it at /tmp
[16:51] <juliank> I'll go play
[17:08] <juliank> Laney: I think it can't talk to the sockets now and restarting them doesn't help, should I just reboot the lxd-worker controller?
[17:08] <juliank> instead of figuring out what else to restart..
[17:09] <Laney> what?
[17:09] <Laney> hang on
[17:09] <juliank> I don't know the autopkgtest-lxd-socat@.service are all failing
[17:10] <Laney> did you break this?
[17:10] <Laney> or was it broken when you got there
[17:11] <juliank> I'm not sure
[17:12] <Laney> I see a /tmp mount
[17:12] <Laney> but I guess everything wasn't stopped before that got inserted
[17:12] <Laney> so the sockets are gone
[17:13] <juliank> But restarting the autopkgtest-lxd-socat you'd expect that to fix
[17:13] <Laney> it's probably failing in the ExecStop or something
[17:14] <Laney> just wait, let me fix it
[17:14] <Laney> stop everything, clear the underlying /tmp, mount the new one, start things back up
[17:14] <juliank> Right I stopped autopkgtest@ only I guess
[17:14] <Laney> yeah and the sockets are in /tmp
[17:14] <Laney> so you ripped them out :>
[17:19] <juliank> Laney: remotes fixed? the worker processes are still stopped, becuase I stopped them because they produced errors, but I also noticed we have too many of them
[17:19] <juliank> we have leftover workers that are not valid lxd remotes
[17:19] <juliank> that's why we get failures from them
[17:21] <Laney> juliank: I don't see them, I ran reset-failed though, maybe that zapped things
[17:21] <juliank> whee, seems good now
[17:22] <juliank> time to add more workers :D
[17:23] <Laney> hope it stops these angry people
[17:23] <Laney> maybe they could get a kitten too
[17:23] <Laney> best thing is going to be when these new machines get turned on
[17:24] <Laney> juliank: btw the wiki says you can use focal, that is lies, make sure to use bionic (get IMAGE= from the history)
[17:24] <Laney> I did fix that in the new branch too :-)
[17:28] <juliank> Laney: How many workers do we want?
[17:28] <juliank> 3, 6?
[17:28] <Laney> 2 more machines?
[17:29] <juliank> hmm that's only 16% more
[17:30] <juliank> 3 arm64 workers ~ 1 armhf lxd remote?
[17:30] <Laney> I would swap the arches there to make it make sense (to me)
[17:31] <Laney> 1 VM -> 3 concurrent tests
[17:31] <juliank> right, if I add two more armhf remotes, I need to disable 3 arm64 workers
[17:31] <juliank> is what I mean
[17:31] <Laney> oh I see
[17:32] <juliank> need to add that to the wiki
[17:32] <Laney> it's not perfect, doesn't account for large tests
[17:32] <Laney> but yeah
[17:33] <juliank> also flavor is cpu4-ram8-disk50 these days not m1.large :D
[17:34] <rbalint> ubuntu-archive i've accidentally uploaded google-osconfig-agent/20210209.00-1 with the wrong version number, could you please delete it?
[17:34] <rbalint> i'd roll it back to -0ubuntu1
[17:35] <juliank> eww ERROR: Quota exceeded for cores, instances, ram: Requested 4, 1, 8192, but already used 52, 13, 106496 of 52, 13, 106496 cores, instances, ram (HTTP 403) (Request-ID: req-c9b6c0d8-8d59-4a32-aa04-e661623f04fe)
[17:36] <juliank> I got one more lxd remote though, that's good
[17:43] <Laney> It'll probably go better if you stop the arm64 first, to free up the quota
[17:45] <juliank> Laney: i did
[17:45] <juliank> I should check again
[17:48] <juliank> they reappeared
[17:49] <juliank> or I suck at reading :D
[17:49] -queuebot:#ubuntu-release- New: accepted emscripten [amd64] (hirsute-proposed) [2.0.12~dfsg-1ubuntu1]
[17:49] <juliank> we have 22 running tests
[17:49] <juliank> / instances
[17:50] <juliank> + 13 armhf nodes
[17:50] <juliank> s/nodes/lxd remote VMs/
[17:50] <juliank> Before we had 30 arm64 workers, I reduced that limit to 24
[17:53] <juliank> So yeah, I freed up 9216 MB RAM, 120GB disk, and 6 CPUs
[17:54] <juliank> And added 4 CPUs, 50GB disk, 8 GB RAM
[17:54] <juliank> So I should have free 1 GB RAM, 4 CPUs, 70 GB disk?
[17:54] <Laney> keep an eye on the slope on https://ubuntu-release.kpi.ubuntu.com/d/yIC34LpGk/ubuntu-metrics?viewPanel=4&orgId=1&from=now-7d&to=now
[17:54] <Laney> see if you made a difference!
[17:55] <juliank> Still building lxd images atm
[17:56] <juliank> Ah, but I can only have 13 instances anyway so trying to add a 14th one is futile
[18:01] <Laney> the cloud masters have decreed it
[18:01] <Laney> maybe bos01 instances would just work, not sure
[18:03] <vorlon> rbalint: google-osconfig-agent removed from -proposed
[18:07] <sil2100> jibel, Laney: just a final touch-base with you guys, do you think we go all the tests we can possibly do in the situation done for .2.0?
[18:07] <sil2100> If yes, I'll start the release in the nearest 1 hour
[18:09] <Laney> sil2100: I don't like it but I think I have done as much as I can here
[18:12] <juliank> Laney: the new lxd remote seems to be running now, juju did not automatically add the lxd remotes and worker services though, but I'm too tired to dig further
[18:12] <juliank> juju set should have enabled that automatically
[18:13] <Laney> that juju hook is flaky
[18:13] <Laney> do it manually, there's some stuff in shell history
[18:13] <Laney> ctrl-r for 'systemctl enable', you should find one for socat and one for the workers
[18:13] <juliank> I enabled them already yes
[18:13] <Laney> ok good 👍
[18:14] <Laney> did you put 3 arm64 back if you couldn't use them?
[18:14] <juliank> not yet
[18:14] <sil2100> Laney: ok, marking desktop as ready to proceed with the release
[18:15]  * Laney winces
[18:15] <Laney> I really hope this is it
[18:15] <juliank> back now
[18:16] <sil2100> I know it's stupid, but at least if it's worse than .2 we can always revert to .2
[18:16] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Focal 20.04.2.0] has been marked as ready
[18:16] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Focal 20.04.2.0] has been marked as ready
[18:16] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.2.0] has been marked as ready
[18:16] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.2.0] has been marked as ready
[18:16] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Focal 20.04.2.0] has been marked as ready
[18:16] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.2.0] has been marked as ready
[18:25] <Laney> I'm not worried about it being worse particularly
[18:25] <Laney> rather finding something else like this 😬
[18:27] <sil2100> I'll wait a bit maybe, discuss a bit more with cert, meditate about it etc. etc.
[18:28] <sil2100> I can always do the publish during the night
=== mfo_ is now known as mfo
[18:34]  * Laney releases 100 kittens into the room with sil2100 
=== mfo_ is now known as mfo
=== mfo_ is now known as mfo
[19:02] <sil2100> The kittens have helped!
[19:15] -queuebot:#ubuntu-release- Unapproved: update-manager (groovy-proposed/main) [1:20.10.4 => 1:20.10.5] (core)
[19:20] <sil2100> Ok, 20.04.2.0 should be out-ish
=== mfo_ is now known as mfo
[20:27] -queuebot:#ubuntu-release- Unapproved: sssd (groovy-proposed/main) [2.3.1-3ubuntu3 => 2.3.1-3ubuntu4] (ubuntu-desktop, ubuntu-server)
=== mfo_ is now known as mfo
[20:41] -queuebot:#ubuntu-release- Unapproved: sssd (focal-proposed/main) [2.2.3-3ubuntu0.3 => 2.2.3-3ubuntu0.4] (ubuntu-desktop, ubuntu-server)
[20:48] <sergiodj> sigv: everything uploaded.
[20:52] <sigv> sergiodj: thank you! Any idea what can be expected from the timeline, when these are in -proposed for verification?
[20:53] <sergiodj> sigv: it depends on the SRU team now.  perhaps someone will be able to look tomorrow; if not, I'd say early next week is a good estimate
[20:53] <sigv> sergiodj: just trying to figure out what to expect - thank you very much. hope you have a nice evening!
[20:54] <sergiodj> sigv: thank you for driving the bug until its completion!  have a great weekend as well :)
[21:16] -queuebot:#ubuntu-release- Unapproved: knockd (groovy-proposed/universe) [0.7-1ubuntu3 => 0.7-1ubuntu3.20.10.1] (no packageset)
[21:17] -queuebot:#ubuntu-release- Unapproved: knockd (focal-proposed/universe) [0.7-1ubuntu3 => 0.7-1ubuntu3.20.04.1] (no packageset)
[21:18] -queuebot:#ubuntu-release- Unapproved: knockd (bionic-proposed/universe) [0.7-1ubuntu1.18.04.2 => 0.7-1ubuntu1.18.04.3] (no packageset)
[21:28] -queuebot:#ubuntu-release- Unapproved: lxc (groovy-proposed/universe) [1:4.0.4-0ubuntu3 => 1:4.0.6-0ubuntu1] (ubuntu-server)
[21:30] -queuebot:#ubuntu-release- Unapproved: rejected lxc [source] (groovy-proposed) [1:4.0.6-0ubuntu1]
[22:01] <Laney> sil2100: thanks for taking care of this one
[22:17] <LocutusOfBorg> vorlon, https://launchpad.net/ubuntu/+source/libmaxminddb/1.5.0-3/+build/21014220
[22:17] <LocutusOfBorg> please lowdown?
[22:54] <vorlon> LocutusOfBorg: done https://launchpad.net/ubuntu/+source/lowdown/0.8.1-1/+build/21014404
[23:16] -queuebot:#ubuntu-release- Packageset: Removed gnome-icon-theme from i386-whitelist in hirsute
[23:16] -queuebot:#ubuntu-release- Packageset: Removed sisu-guice from i386-whitelist in hirsute
[23:16] -queuebot:#ubuntu-release- Packageset: Removed sisu-ioc from i386-whitelist in hirsute
[23:16] -queuebot:#ubuntu-release- Packageset: Removed yelp-tools from i386-whitelist in hirsute
[23:16] -queuebot:#ubuntu-release- Packageset: Removed yelp-xsl from i386-whitelist in hirsute
[23:16] -queuebot:#ubuntu-release- Packageset: Added lowdown to i386-whitelist in hirsute
[23:21] -queuebot:#ubuntu-release- New sync: wiipdf (hirsute-proposed/primary) [1.4-3]
[23:23] <LocutusOfBorg> thanks!
[23:25] -queuebot:#ubuntu-release- New sync: rust-png (hirsute-proposed/primary) [0.15.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted rust-png [sync] (hirsute-proposed) [0.15.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted wiipdf [sync] (hirsute-proposed) [1.4-3]
[23:52] -queuebot:#ubuntu-release- Unapproved: bind9 (focal-proposed/main) [1:9.16.1-0ubuntu2.4 => 1:9.16.1-0ubuntu2.5] (core, i386-whitelist)