=== popey2 is now known as popey [03:05] PR snapd#10780 opened: tests: manually umount devices during reset to prevent invariant error [05:18] morning [05:43] mborzecki: hi! [05:57] mardy: heya [06:28] eh 21.10 spread tests are in a sad state right now [06:49] i think we need to land the gdb shims fix first [07:05] morning [07:21] pstolowski: hey [07:21] pstolowski: quick question, when preseeding do we run the snapd binary inside the mount ns of the image? [07:22] mborzecki: no, we just chroot and run snapd [07:23] pstolowski: ok, but the binary is started after chrooting? [07:24] mborzecki: yes [07:24] pstolowski: hm so bad news is that in 21.10 spread test this no longer works :) [07:28] mborzecki: because we build snapd on older ubu? [07:30] pstolowski: there's a problem with glibc version, but one thing i don't understand, in theory we preseed the image that matches the host, so why would there be a problem? [07:31] unless the image we download is older :/ [07:31] mborzecki: yes exactly. 21.10 might be in flux [08:20] mvo: can you land https://github.com/snapcore/snapd/pull/10778 ? the previous run was more successful, this one failed because of store and archive sync [08:20] PR #10778: cmd: build gdb shims as static binaries [08:46] pstolowski: heh, the cloud image we download for preseeding 21.10 is outdated and has an older glibc [08:46] mborzecki: yeaaah [08:47] mborzecki: thanks for chasing this [09:16] PR snapd#10778 closed: cmd: build gdb shims as static binaries [09:23] miguelpires: I added a small suggestion to 10756, hope it's helpful and I'm not missing something [09:25] mvo: mardy: another batch of tirivial fixes for 21.10 https://github.com/snapcore/snapd/pull/10781 [09:25] PR #10781: tests: fix tests for 21.10 [09:26] PR snapd#10781 opened: tests: fix tests for 21.10 [09:28] mborzecki: \o/ [09:35] also https://github.com/snapcore/snapd/pull/10703 needs a 2nd review [09:35] PR #10703: tests/main/security-device-cgroups-strict-enforced: demonstrate device cgroup being enforced [09:37] PR snapd#10782 opened: o/ifacestate: do not create stray task in batchConnectTasks if there are no connections [09:41] mvo, yes, definitely, it's much better. Thanks [10:10] * pstolowski lunch+errand, bbl [10:51] looks like some of the remodel unit tesst could use longer timeouts, as they failed on armhf and s390 during lp builds [11:12] PR snapd#10615 closed: Revert "cgroup-support: allow to hide cgroupv2 warning via ENV" [12:59] mborzecki: are all the other failures in 10781 unrelated? also why are things so unhappy currently? [13:00] PR snapd#10783 opened: [RFC, draft] tests: report stray tasks in spread test restore <â›” Blocked> [13:10] PR snapd#10784 opened: o/snapstate: add ChangeID to conflict error [13:56] re [14:07] this code here, does it actually send the same request to all user sessions in the system? https://github.com/snapcore/snapd/blob/master/usersession/client/client.go#L97-L154 [14:22] the store is still a bit unhappy [14:23] cachio: thanks for updating the images, can i rerun the tests now? [14:43] mborzecki, yes [14:43] yaw [14:46] * cachio_ afk [15:29] ijohnson[m]: hey, would you take a look at https://github.com/snapcore/snapd/pull/10782 ? [15:29] PR #10782: o/ifacestate: do not create stray task in batchConnectTasks if there are no connections [15:29] sure [15:30] ty [15:31] PR snapd#10785 opened: tests: add test for store.SnapAction() request timeout [15:32] mardy: hey this is that test you fixed before right? it seems odd to me that actually the test takes more than the 30 minute allowance??? https://pastebin.ubuntu.com/p/ZG4tYn7Nmp/ [15:32] is it possible that during this test there is a timesync or something ? [15:34] cachio_: have you seen this failure on debian-sid before? https://pastebin.ubuntu.com/p/J2Hpk6n89C/ [15:34] I seem to see it frequently these days, is there some flag we could call dpkg with that would wait for the lock to be released instead of just failing like this? [15:34] see https://github.com/snapcore/snapd/runs/3611010453?check_suite_focus=true for example of where it happened twice [16:21] ijohnson[m], no [16:21] there is code in ubuntu images to prevent it [16:22] let me check debian-sid [16:22] ijohnson[m], in debian we dont have that code [16:22] so far was not needed [16:23] I'll check in the image if the issue is that same that we had in ubuntu a time ago [16:26] thanks cachio_ [16:33] ijohnson[m], I'll update the debian sid images [16:34] cachio_: thanks that works too [17:41] PR snapd#10786 opened: tests: print user sessions info on debug-each [19:01] PR snapd#10787 opened: tests: add a local snap variant to testing prepare-image gating support [19:06] PR snapd#10731 closed: sysconfig/cloudinit: add cloudDatasourcesInUseForDir [19:26] PR snapd#10788 opened: many: rename systemd.Kind to Backend for a bit more clarity [21:07] PR snapd#10789 opened: tests: new test invariant to check no systemd user units running [21:12] PR snapd#10790 opened: gadget: add VolumeName to Volume and VolumeStructure [21:32] PR snapd#10791 opened: gadget/gadget.go: LaidOutSystemVolumeFromGadget -> LaidOutVolumesFromGadget [21:46] PR snapcraft#3580 opened: environment-setup-local: do not build rust [22:31] cachio_: have you seen this one https://pastebin.ubuntu.com/p/cRPHmRQPZV/ ? [23:02] PR snapd#10792 opened: packaging: backports of golang-go 1.13 are good enough