[06:28] mborzecki: 'morning! How did you get this nice graph here? https://paste.ubuntu.com/p/y7tQtxQScq/ [06:31] PR snapd#11108 closed: tests: disable flacky test snapd-failover [06:58] morning [06:58] mardy: silly pastebin requires me to log in 😕 just a sec [06:59] mardy: i used this tool: https://github.com/KyleBanks/depth [07:15] mborzecki: cool, thanks! [08:03] morning [08:28] pstolowski: hi! [08:29] heya [11:02] morning folks [11:12] ijohnson[m]: hi! [11:13] o/ [11:17] PR snapd#11169 opened: o/snapstate: migrate to hidden dir on refresh/install [11:23] mardy: it seems like https://github.com/snapcore/snapd/pull/11080 is ready to land no? is it waiting on anyone or anything else ? [11:23] PR #11080: builtin/interfaces: add shared memory interface [11:32] PR snapd#11170 opened: snap: squashfs library to read squashfs images [11:44] ijohnson[m]: yes, it can be merged, but I lack permissions to force it through the CI [11:44] mardy: ack just checking I can ask pedronis to merge it [11:45] ijohnson[m]: oh, wait a second, I want to squash the commits [11:45] we can just tag it with squash merge [11:46] just update the PR description with what you want the commit message to be [11:48] ijohnson[m]: too late, I already rebased it :-D [11:49] ah ok, for reference that is what the squash-merge tag for PR's is for [11:58] ijohnson[m]: thanks, I actually knew it, but it's rare that I want to squash everything to a single commit, I often have 2-3 which I prefer to keep separate (though in this case, I could indeed have squashed them all) [12:00] mardy: sure that's fair, also the other thing I would mention is that I do typically prefer to not force push things after it's gotten reviews to ensure that it's clear to the reviewers that nothing changed in the force push. this does mean we end up with rather messy git history, but that is the decision we made a while ago; perhaps you could ask pedronis about this, I may have since forgotten all the justification why we did it that way [12:04] ijohnson[m]: no you are right, in github it's very hard to understand what changed from one force-push to the other (whereas gitlab is much better in this aspect); but I was told that after the approval, I could rearrange the commits, as long as the code is not changed [12:05] ah perhaps our policy has indeed changed, I remember discussing this when I joined the team and what I recall being told was that any force repushes would require new reviews [14:47] meh that bpf programs list is slightyl inconvenien to work with [17:39] PR snapd#11088 closed: tests: add tags to identify the tests that cover the basic functionalities of snapd <⛔ Blocked> [18:19] PR snapd#11171 opened: tests: tag spread tests with basic tag on core test suite [19:55] PR snapcraft#3606 opened: build(deps): bump lxml from 4.6.3 to 4.6.5 [20:59] hi all, any idea about why this error might be happening? /snap/bin/snapcraft: 3: exec: /snap/snapcraft/current/usr/bin/python3: not found [20:59] fwiw we're using a custom docker image that's essentially the same as https://github.com/snapcore/snapcraft/blob/master/docker/Dockerfile [20:59] bandali: what's `snap list snapcraft` ? [21:00] oh nvm then, you won't have snapd then to actually install the snap [21:00] hmm. yeah we're just using that docker image [21:00] yeah that docker image doesn't actually install any snaps, it's a bit of a hack [21:01] right :/ any tips on how to go about debugging this? [21:01] bandali: you might try asking on the forum, not sure who's around, but someone may see the post on the forum in the morning in EU [21:01] ijohnson[m], aha okay i'll give that a shot, thanks! [21:01] np [21:10] PR snapd#11172 opened: tests: skip installing systemd-timesyncd in debian 10