=== tianon- is now known as tianon [06:45] morning [07:55] hi mborzecki [08:02] morning [08:28] good morning pstolowski [09:46] PR snapd#11252 opened: snap: cpu quota support through --cpu, --cpu-set and --thread [10:46] PR snapd#11253 opened: packaging,tests: fix running autopkgtest [10:56] mmm... the code coverage report clearly has some issues. This function is actually fully covered by existing unit tests, yet it shows up as red: https://app.codecov.io/gh/snapcore/snapd/compare/11248/diff#D3L54 [11:17] PR snapd#11254 opened: spread-shellcheck: use safe_load rather than load with a loder [12:06] reviews for pr#11253 would be supernice, with that I can SRU again and fix the autopkgtest failures we got in the most recent upload [12:07] PR snapd#11255 opened: Transactional installs/removes/refreshes [12:22] PR snapd#11243 closed: tests/main/snap-info: use yaml.safe_load rather than yaml.load [12:22] PR snapd#11249 closed: cmd/snap: rm unnecessary validation [12:32] PR snapd#11231 closed: cmd/snap: setup tracking cgroup when invoking a service directly as a user [12:42] PR snapd#11208 closed: interfaces: allow access to new at-spi socket location in desktop-legacy [12:52] meh, so git add -f refuses to add a file named pc-boot.img since we have a matching pattern in gitignore [12:52] even though i used -f [12:57] PR snapd#11256 opened: Minor changes ensuring unset SNAPD_DEBG to avoid test failures when r… [13:02] PR snapd#11254 closed: spread-shellcheck: use safe_load rather than load with a loder [13:14] mborzecki: weird... what's the error message? [13:15] mardy: found the culprint, we had *.img in spread.yaml, so it was in git, but miraculously disappeared the source tree on gce [13:15] i mean we had *.img in exclude in spread.yaml 🙂 [13:29] ah, tricky! [13:43] bboozzoo: hey for the core20-remodel nested spread test, do you think this line should be done in a loop? is it racing with snapd trying to write that file? https://github.com/snapcore/snapd/blob/116fa26916a32c582066340c73025f50ca5601d4/tests/nested/manual/core20-remodel/task.yaml#L47 [13:44] I saw that test fail because that file was not present, but all the logs from snapd in the VM suggests that the remodel was in fact successful [13:50] ijohnson: sec, let me see [13:51] ijohnson: hmm no by the time it runs the label should be there already, unless hmm it ran around midnight maybe? [13:56] bboozzoo: haha [13:56] 2022-01-14 00:03:51 Debug output for google-nested:ubuntu-20.04-64:tests/nested/manual/core20-remodel (jan132315-799582) : [13:57] 4 minutes after midnight [13:57] hahah [13:57] got link? [13:57] https://github.com/snapcore/snapd/runs/4810553343?check_suite_focus=true [13:57] ijohnson: i suspect the base label is 20220113, but the remodel started after midnight already 🙂 [13:57] (or at least the label was created at that time) [13:58] yeah [13:58] hm maybe i should buy some lottery tickets [13:58] 🙂 [14:07] ijohnson: so afaiu, the image ran was creaated before midnight, thus the recovery system label was 20220113, but the test then ran after midnight already so it assumed that the label is 20220114 and expected 20220114-1 to appear next [14:23] PR snapcraft#3623 opened: feat: add source_recurse_submodules [14:27] bboozzoo: that makes sense, any idea how we could prevent that sort of thing from happening? could we make the check more loose to check for the current date or the previous date? [14:29] ijohnson[m]: hi! The new custom-device interface, it will be available only on the UC devices, right? [14:31] mardy: that is the main consumer yes since it will require a gadget snap, but we have had on occasion some enablements where they have a classic gadget, so if at all possible we should not assume that it will only be used on ubuntu core [14:53] PR snapd#11199 closed: tests: fix uses of fakestore new-snap-declaration [14:55] super duper simple PR for anyone with 30 seconds 🙂 https://github.com/snapcore/snapd/pull/11257 [14:55] PR #11257: gadget: fix typo with filesystem message [14:58] PR snapd#11257 opened: gadget: fix typo with filesystem message [15:04] ijohnson: or maybe just tweak the error message: https://github.com/snapcore/snapd/pull/11257/commits/46ee01f8f3d803d19b5e6b673f0de86f751a349d#r784914495 [15:04] PR #11257: gadget: fix typo with filesystem message [15:04] oh no it's not super duper simple! 🙂 [15:04] bboozzoo: also I opened https://github.com/snapcore/snapd/pull/11258 too [15:04] PR #11258: tests/nested/manual/core20-remodel: try to work around midnight problem [15:08] PR snapd#11258 opened: tests/nested/manual/core20-remodel: try to work around midnight problem [15:33] PR snapd#11230 closed: gadget: misc helper fixes for implicit system-data role handling [16:11] mvo: when do you think we can get user-daemons enabled by default? [16:28] PR snapd#11257 closed: gadget: fix typo with filesystem message [17:18] PR snapd#11259 opened: tests/nested/manual/minimal-smoke: bump mem to 512 for unencrypted case too [17:18] PR snapd#11260 opened: tests/nested/manual/minimal-smoke: revert back to 384M for unencrypted case <⛔ Blocked> [17:23] PR snapcraft#3624 opened: Fix npm plugin permission denied [23:05] PR snapd#9536 closed: RFC: bootloader ping/pong protocol <:birthday:> [23:25] PR snapd#11261 opened: tests/lib/nested.sh: add debug kernel command line parameters