[05:43] morning [06:10] good morning [06:14] zyga-mbp: hi! [06:14] hey mardy [06:15] I'm looking at bunch of random spread reboot failures, where after reboot stuff fails to connect inside Go's ssh library, apparently due to lack of compression support [06:15] have you guys seen this at all? this is always against the qemu target [06:16] all I have so far is https://go.googlesource.com/crypto/+/master/ssh/mux.go#328 this line [06:25] zyga-mbp: not that I know of (I actually never tried to use qemu with the spread) [06:26] I don't think it's specific to qemu [06:26] feels like a bug in go's ssh implementation [06:26] googling for that error text makes is clear this is a widespread issue [06:26] I really wonder why it happens with increased frequency now [06:27] my tests run against hirsute [06:27] perhaps something got updated [06:36] thunderbird snap... is there a documentation where thunderbird stores all its mails, calendar data and so on? [06:38] zyga-mbp: mardy: hey [06:38] PR snapd#10922 closed: none: dummy commit [06:39] hey mborzecki :) [06:40] dust, snaps typically store their data somewhere under ~/snap//common or ~/snap//current ... take a look there [06:40] mborzecki: hi! [06:48] ogra, thanks [07:07] morning [07:10] hey pstolowski [07:27] pstolowski: hi! [08:24] PR snapd#10932 closed: tests/nested/core/core20-create-recovery: fix passing of data to curl [08:28] congratulations on shipping impish :) [08:34] PR snapd#10931 closed: interface/modem-manager: add accept for MBIM/QMI proxy clients [08:39] PR snapd#10926 closed: tests: remove extra-snaps-assertions test [08:44] PR snapd#10904 closed: osutil/disks, many: switch to defining Partitions directly for MockDiskMapping [08:49] Bug #1947563 opened: snapd execs /usr/lib/snapd/snap-seccomp despite libexecdir set to /usr/libexec [08:49] PR snapd#10873 closed: interfaces/builtin: Add '/com/canonical/dbusmenu' path access to 'unity7' interface [08:49] PR snapd#10927 closed: interfaces/builtin/hardware-observer: add /proc/bus/input/devices too [09:59] PR snapd#10917 closed: many: mv MockDeviceNameDisksToPartitionMapping -> MockDeviceNameToDiskMapping [09:59] PR snapd#10938 opened: tests: skip connection of netlink interface on older systems [10:06] Hey. I'm having some trouble running some of the spread tests, maybe I'm missing something obvious . The suite prepare fails on `snap install --edge core error: cannot perform the following tasks: - Copy snap "core" data (no state entry for key)` [10:08] The full output is here https://pastebin.canonical.com/p/GtTX58pWFN/ [10:10] If someone has any idea what the issue could be, I'd appreciate the help :] [10:16] miguelpires: is this on your branch with snap folder changes? [10:21] miguelpires: unfortunately "no state entry for key" is one of the least helpful errors we have :( unless decorated with additional info. i'd start with looking at doCopySnapData() and add extra debug around all err handling there [10:21] Yes, I guess "core" isn't supposed to have state [10:21] ? [10:21] * zyga-mbp miguelpires it's a sign of missing error handling [10:21] miguelpires: no, this error is about a st.Get("...") not finding a requested key (can be snapstste.Get(..) for example) [10:21] * zyga-mbp it's the error that should never surface higher [10:22] * zyga-mbp yeah, pstolowski is right, calls like that are guarded against no state usually [10:22] I see, thanks! [10:25] miguelpires: we often explicitly handle such error by checking if err is state.ErrNoState [12:01] pstolowski: thanks for the review on https://github.com/snapcore/snapd/pull/10938, but I'd need another one since I had to change it considerably :-) [12:01] PR #10938: tests: skip connection of netlink interface on older systems [12:15] PR snapd#10847 closed: cmd/snap-confine: die when snap process is outside of snap specific cgroup [12:19] mardy: oh indeed, i think you should change "tests: " prefix and it may need security review [12:48] pstolowski: I don't think we need to involve security, since this PR is restricting the access [12:48] mardy: right, indeed [12:55] PR snapd#10939 opened: tests: spread test for validation sets enforcing [13:35] mardy: so which specific test /variant is it that was failing? [14:05] ijohnson[m]: the issue I was talking about in the standup is on ubuntu-core-18 (maybe also UC 20, but I'm not sure). The PR is https://github.com/snapcore/snapd/pull/10935 [14:05] PR #10935: tests: wait for snapd to be fully setup before installing snaps [14:06] ijohnson[m]: the service unit seems correct, it has Requires and After: https://paste.ubuntu.com/p/gGVwCtrXYj/ [14:07] * ijohnson[m] looks [15:36] PR snapd#10940 opened: tests: force 16.04 packaging when doing test snapd-snap build [16:14] miguelpires: hey just FYI when we ask for more information on bugs like in https://bugs.launchpad.net/snapd/+bug/1946996, we set the status to "Incomplete" [16:14] Bug #1946996: snapd: slice bounds out of range [16:27] ijohnson[m]: ok, I'll do that now :] thanks [16:46] PR snapd#10930 closed: secboot: revert move to new version (revert #10715) <âš  Critical> [16:53] miguelpires, note that incomplete bugs expire automatically after 60 days though [16:53] (i.e. if you want to keep it around even after that and without user reply, pick another status) [16:56] PR snapd#10929 closed: tests/nested/manual: add regression test with old/existing initrd and new snapd <â›” Blocked> [17:37] ogra, I see, thanks for the heads up