/srv/irclogs.ubuntu.com/2020/07/22/#snappy.txt

mborzeckimorning05:20
zygare07:45
zyga30 min07:46
zygatill meds07:46
zygathank you for moving the call07:47
zygauh, lots of pain07:48
mborzeckipedronis: hi, wondering maybe we should try to cherry-pick to 2.45 the commits that tweak spread.yaml so that we get the caching behavior from master08:14
mupPR snapd#9042 opened: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>08:19
pedronismborzecki: yes, possibly, I'm still trying to land #9012 first08:22
mupPR #9012: release/2.45: merge 2.45.2 release <Created by mvo5> <https://github.com/snapcore/snapd/pull/9012>08:22
mupPR snapd#9043 opened: daemon: decompose access check into smaller primitive access checkers <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9043>08:40
mupPR snapd#9044 opened: github: cherry-pick gh-action fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>08:45
mborzeckipedronis: ^^ let's see how far that PR will run08:45
zyga-x240okay, so this is much more lucid now09:16
mborzeckizyga-x240: https://github.com/snapcore/snapd/pull/9042 apparmor cherrypicks09:16
mupPR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>09:16
mborzeckizyga-x240: and https://github.com/snapcore/snapd/pull/9044 that's the gh actins caching tweaks09:16
mupPR #9044: github: cherry-pick gh-action fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>09:16
mborzeckiand it's red (unsurprisingly?)09:16
ogra_hmm, does command-chain only work for nondaemon apps ?09:18
zyga-x240ogra_: it should not matter09:18
ogra_(it does nto seem to get executed for me )09:18
ogra_*not09:18
ogra_weird09:19
zyga-x240looking at the failures09:19
ogra_oh !09:19
ogra_seems snapcraft ignores changes in snap/local (where my script lives) 😛09:20
zyga-x240just preseed failures09:20
* ogra_ manually cleans the part 09:20
zyga-x240well, in 19.10 - more failures elsewhere09:20
zyga-x240shellcheck issues09:21
zyga-x240pain slowly going away09:45
mborzeckipedronis: i've left a note about failures in https://github.com/snapcore/snapd/pull/9012 i think we should just force merge and i'll start cherry-picking the obvious things (cc zyga-x240)09:59
mupPR #9012: release/2.45: merge 2.45.2 release <Created by mvo5> <https://github.com/snapcore/snapd/pull/9012>09:59
zyga-x240looking10:00
zyga-x240I've ran the unit tests test alone and it passed10:01
zyga-x240so maybe random as well10:01
zyga-x240ah drat, wrong branch10:01
pedronismborzecki: thx, other emergency maybe solved10:01
pedroniswe'll see10:01
zyga-x240I agree we should merge10:01
zyga-x240and iterate10:01
pedronisI'look in a bit10:01
pedroniszyga-x240: mborzecki: merged10:07
pedronismborzecki: it seems most thing you mentioned worth cherry picking are kind of small?10:07
pedronismborzecki: maybe worth doing one PRs with them, most of them?10:07
pedronisto 2.45?10:07
mborzeckipedronis: yes, i'll do it10:08
mborzeckipedronis: thanks for merging the branch10:08
mupPR snapd#9012 closed: release/2.45: merge 2.45.2 release <Created by mvo5> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/9012>10:10
zyga-x240we have this 41d38c4b7f7554bdef88d567608241930a237cd910:12
zyga-x240let me check if that is in the release branch10:13
zyga-x240(nfs fix)10:13
mborzeckizyga-x240: ah, cool10:14
zyga-x240one sec10:15
mupPR snapd#9039 closed: cmd/snap-seccomp/syscalls: add faccessat2 (2.45) <Simple 😃> <⛔ Blocked> <Created by bboozzoo> <Closed by pedronis> <https://github.com/snapcore/snapd/pull/9039>10:15
zyga-x240https://github.com/snapcore/snapd/pull/904510:16
mupPR #9045: Disable part of the nfs-support test that checks udp proto on debian-… <Created by zyga> <https://github.com/snapcore/snapd/pull/9045>10:16
zyga-x240now about https://github.com/snapcore/snapd/pull/904410:17
mupPR #9044: github: cherry-pick gh-action fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>10:17
* zyga-x240 looks at failures10:17
mborzeckizyga-x240: looked at failures already, i'll stat pushing cherry-picks there10:17
mborzeckizyga-x240: also, will pick 904510:17
zyga-x240ok10:17
mupPR snapd#9045 opened: Disable part of the nfs-support test that checks udp proto on debian-… <Created by zyga> <https://github.com/snapcore/snapd/pull/9045>10:20
mborzeckizyga-x240: pushed most to #9044, i need to look at the PR with preseed tests, either pick everything from it or just https://github.com/snapcore/snapd/commit/0a9a25f1b4c3a711a96874a1d14933d01a97e0e810:23
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>10:23
zyga-x240mborzecki: shall I push there directly?10:28
mborzeckizyga-x240: hmm, yes, but maybe let's wait for spread jobs to run through10:30
zyga-x240ok10:30
mborzeckizyga-x240: btw. tests/main/lxd has changed quite a bit, one from 2.45 branch is failing spread-shellcheck locally here: https://paste.ubuntu.com/p/W9htPXc3bx/10:33
mborzeckizyga-x240: hm fixes are trivial, so i'll just fix it rather than picking even more patches :/10:35
zyga-x240eh, silly shellcheck10:37
zyga-x240ok10:37
* zyga-x240 backported preseed fixes, testing now10:48
* zyga-x240 looks at go10:52
zyga-x240https://github.com/snapcore/snapd/pull/9046 has the preseed changes, it should be merged into https://github.com/snapcore/snapd/pull/9044 when another round of tests passes11:03
mupPR #9046: tests: backport preseed test fixes to 2.45 <Created by zyga> <https://github.com/snapcore/snapd/pull/9046>11:03
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>11:03
mborzeckizyga-x240: thanks11:04
mborzeckiwow, commits form april11:05
mborzeckifrom11:05
zyga-x240we should release 2.4611:05
zyga-x240even if it's not in stable11:05
zyga-x240just try to iterate11:05
mupPR snapd#9046 opened: tests: backport preseed test fixes to 2.45 <Created by zyga> <https://github.com/snapcore/snapd/pull/9046>11:05
mborzeckizyga-x240: hm maybe i should just cherry-pick everything from 9046 to 904411:06
zyga-x240yes11:06
zyga-x240git merge it11:06
mborzeckimhm11:06
zyga-x240I opened it separately to see how it behaves11:06
mborzeckiwill do11:06
mborzeckizyga-x240: one more cherry-pick i didn't notice before: https://github.com/snapcore/snapd/commit/6c09de0f3f11:14
zyga-x240ah11:14
zyga-x240put it directly into your fixes branch11:15
mborzeckiyup11:23
pedronismborzecki: the plan is to land only 9044?11:37
mborzeckipedronis: yes, i plan to push necessary fixes to 9044, land it, and then rebase #9042 on top11:39
mupPR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>11:39
mborzeckipedronis: the good part is that most changes, if not all are in tests11:40
pedronismborzecki: sounds good11:41
zyga-x240hmmm11:44
zyga-x240is there anything in go that guarantees errno is set to zero before C calls?11:44
zyga-x240because if not then user/ is buggy11:44
zyga-x240ijohnson: around?11:55
zyga-x240mborzecki: maybe cherry pick the travis test away as well :D11:55
pedroniszyga-x240: go in general does it own syscall handling, it not following C conventions11:56
ijohnsonzyga, not quite yet still having breakfast but I'll be into the office in 30 min or so11:57
pedronisI suspect cgo does the right thing11:57
pedronisbut would need to dig11:57
zyga-x240mmm11:57
zyga-x240ijohnson: ok11:57
zyga-x240talk to you later11:57
* zyga-x240 reviewed https://github.com/snapcore/snapd/pull/9041#pullrequestreview-45324689311:58
mupPR #9041: osutil/group.go: treat all non-nil errs from user.Lookup{Group,} as Unknown* <Bug> <Preseeding 🍞> <⚠ Critical> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9041>11:58
mborzeckizyga-x240: all of it now https://github.com/snapcore/snapd/pull/9044 hopefully we can land it once the spread jobs finish11:58
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>11:58
zyga-x240 brb11:58
paul424I try to modfiy the file : /snap/opendungeons/27/etc/opendungeons/plugins.cfg  ; I get non-writable file system. What should I do to modfiy the aforementioned file ? :)12:03
mborzeckipaul424: is this fil expected to be modified by the end users?12:05
mborzeckiheh, we have `var osutilFindGid = osutil.FindGid` in journal.go which does not appear to be used?12:06
paul424well yes and no, the friend of mine created ad hoc solution of packaging the OD into snap; usually the user is expected to modfiy the file plugins.cfg in Ogre3d game engine for example : to set the proper path of the rendering plugins12:06
mborzeckipedronis: all patches (sans apparmor backports) are now in https://github.com/snapcore/snapd/pull/9044 if you want to take a look12:07
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>12:07
paul424so... but I remember I somehow by-passed this and run succesfully OD .... problem is I don't remember how...12:07
mborzeckipaul424: as those plugins something the user is expected to be able to add later?12:07
mborzeckis/as/are/12:08
paul424mborzecki: the rendering plugins comes with Ogre3d engine hmm ....12:08
paul424PluginFolder=/usr/lib/OGRE12:09
paul424cause troubles, also shoudn't that be reassigned to diffrent path if it is running under snap ? That is to the path of Snap's Ogre library ?12:10
paul424the snap ogre lib is in :  /snap/ogre/151/lib/12:13
paul424Does snapper create a virtual executable envoierment or something ?12:13
zyga-x240paul424: snaps are immutable filesysytems, they cannot be modified at all12:14
paul424great12:14
zyga-x240paul424: snap author should arrage for files that need to be modified to live in other places12:14
zyga-x240paul424: like $SNAP_DATA or $SNAP_USER_DATA12:14
zyga-x240paul424: there are ways to make this work but it requires some cooperation with the snap author12:14
mborzeckizyga-x240: in this case it sounds like ogre (the engine) is expected to be a content snap?12:14
* zyga-x240 doesn't want to jump into details 12:15
paul424thanks for enlighting me :D12:16
zyga-x240mborzecki: https://github.com/snapcore/snapd/pull/9044 looks optimistic12:34
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>12:34
* ijohnson is back12:34
mborzeckizyga-x240: yup12:34
* ijohnson or maybe here for first time today12:34
zyga-x240ijohnson: +1 on the error checking for user lookup PR12:34
ijohnsonthanks12:34
zyga-x240I had a look through go and meh12:34
mborzeckiijohnson: o hi, fun stuff with user lookup :/12:35
zyga-x240too much inconsistency12:35
ijohnsonyeah it's a bit disappointing, but then again the man page for getgrpnam_r does kinda say it's impossible anyways12:35
ijohnsonmborzecki: oh? what more fun stuff ?12:35
zyga-x240ijohnson: but I would expect _some_ level of consistency12:35
zyga-x240between the various backends12:35
zyga-x240but no, that's not the case12:35
ijohnsonyeah12:36
pedroniszyga-x240: regarding your errno question, go in general seems to do it's own syscall handling, about cgo afaict it works as expected because th c code gets its own tls stuff, but this is as usual slightly hard to follow in the go code12:37
zyga-x240pedronis: right, I was only curious because some calls do not reset errno12:37
zyga-x240and I was wondering if cgo explicitly sets errno = 0 ahead of all calls12:37
zyga-x240the real bug is in the higher layer in go12:38
* zyga-x240 starts a test and takes that break 12:38
=== nottrobin_ is now known as nottrobin
pedroniszyga-x240: anyway cgo itself seems to emit "errno = 0" in some cases12:40
pedroniszyga-x240: see cmd/cgo/out.go in go itself12:42
* zyga-x240 looks12:43
mborzeckiijohnson: while you're around, can you take a look at https://github.com/snapcore/snapd/pull/9030 ? :)12:49
mupPR #9030: bootloader/assets: helpers for registering per-edition snippets, register snippets for grub <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9030>12:49
zyga-x240mborzecki: tests are failing on ...12:49
zyga-x240 2020-07-22T12:22:24.0548501Z        /tmp/sanity-squashfs-830795014: no space left on device12:49
zyga-x2402020-07-22T12:22:24.0542897Z ##[error]2020-07-22 12:22:24 Error executing google:ubuntu-19.10-64:tests/main/install-store-laaaarge (jul221201-927192) :12:50
mborzeckipfffff12:50
ijohnsonmborzecki: ah so sorry yes I will submit it now, I wrote all the comments and it seems I forgot to submit it :-)12:50
zyga-x240another failed on EOF from reboot12:50
zyga-x2402020-07-22T12:42:59.1435778Z ##[error]2020-07-22 12:42:59 Error executing google:ubuntu-core-16-64:tests/core/reboot (jul221201-861200) : kill-timeout reached after jul221201-861200 (google:ubuntu-core-16-64:tests/core/reboot) reboot request12:50
mborzeckiheh, gdoc does not like firefox12:51
zyga-x240one failed on preparing due to purge12:51
mborzeckizyga-x240: lxd?12:51
zyga-x240no, just prepare up front12:51
ijohnsonmborzecki: submitted12:51
zyga-x240one more is in progress12:51
mborzeckizyga-x240: 8883 is still waiting12:51
mborzeckiijohnson: thanks12:52
zyga-x240I'd restart the three to see if they can land cleanly12:52
zyga-x240but I'd be fine with override as well12:52
ijohnsonmborzecki: but did you see my question in IRC earlier? was there something else to know about the user stuff ?12:52
mborzeckiijohnson: probably missed it, what was the question?12:52
ijohnsonmborzecki: oh you just said there was more fun, and I wasn't sure if you were just referring to the situation in general or something else that you found after looking at the PR12:53
zyga-x240mborzecki: 640GB should be enough for a google doc12:53
mborzeckiijohnson: ah, nah just the general state of things around that area12:54
ijohnsonyeah rather sad12:54
ijohnsonbut good that we debugged it in MM some more and it sounds like CPC has a way forward in the meantime while waiting for the fix12:54
mborzeckizyga-x240: that failure in prepare is 888313:01
pedronisijohnson: standup?13:01
ijohnsonyes13:01
ijohnsoncachio: SU?13:02
mborzeckizyga-x240: restarted the spread job in https://github.com/snapcore/snapd/pull/904413:16
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>13:16
zyga-x240ok13:16
zyga-x240ahh13:27
zyga-x240there's one thing I didn't do that jamie surely did13:27
zyga-x240run this as user!13:27
mborzeckizyga-x240: the caching behavior in #9044 is such a nice improvement now that i restarted the ci job13:27
mupPR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>13:27
zyga-x240:D13:27
zyga-x240why do we even bother with hangouts on non-mobile devices, mobile experience is just so much better13:43
pedroniszyga-x240: mborzecki: we can close 9045 and 9046 right?13:44
zyga-x240checking13:44
zyga-x240yes13:44
zyga-x240they are now in the big PR13:44
ijohnsonpedronis: ok, so looking again the ones that are blocking things are these PR's: 8890, 8612, 8854, 8652, and 879513:45
mborzeckipedronis: zyga-x240: closed them now13:45
ijohnsonpedronis: the only ones that are not strictly snap-bootstrap related are the _writable-defaults thing, and a cloud-init related thing that needs to land with the _writable_defaults, otherwise the _writable-defaults PR as-is will undo the cloud-init fix13:45
ijohnsonpedronis: if you like I can prepare a backport PR with all of those after 9044 lands cleanly13:46
mupPR snapd#9045 closed: Disable part of the nfs-support test that checks udp proto on debian-… <Created by zyga> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/9045>13:46
mupPR snapd#9046 closed: tests: backport preseed test fixes to 2.45 <Created by zyga> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/9046>13:46
mborzeckipedronis: ijohnson: for preseeding we may want https://github.com/snapcore/snapd/pull/9015 and https://github.com/snapcore/snapd/pull/9018 in .45 right?13:47
mupPR #9015: cmd/snap-preseed: handle relative chroot path <Bug> <Preseeding 🍞> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9015>13:47
mupPR #9018: cmd/snap-preseed: check that target path exists and is a directory on --reset <Preseeding 🍞> <Simple 😃> <Created by stolowski> <Merged by anonymouse64> <https://github.com/snapcore/snapd/pull/9018>13:47
ijohnsonmborzecki: yes to 8015, 9018 is nice to have but not necessary, it is just better error handling13:48
mborzeckiack13:48
zyga-x240break14:04
mborzeckipedronis: zyga-x240: so 9044 is looking good, the failure on 19.10 is probably related to user session fixes in tests that are done in master, but were not cherry-picked14:12
* pedronis in meeting14:16
zyga-x240mborzecki: looking14:19
zyga-x240hmm14:20
zyga-x2402020-07-22T13:47:54.7315113Z Failed to connect to bus: Connection refused14:20
zyga-x240yeah I think that's ok to merge14:20
zyga-x240+1 and let's rebase the rest14:20
mborzeckiyup, doing so now14:20
zyga-x240ok14:20
mupPR snapd#9044 closed: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>14:21
mborzeckizyga-x240: rebased https://github.com/snapcore/snapd/pull/9042 please take a look14:24
mupPR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>14:24
mupPR snapd#9047 opened: cmd/snap-preseed: backport fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9047>14:36
mborzeckiijohnson: can you take a look ^^ ?14:37
ijohnsonmborzecki: sure14:38
mborzeckiijohnson: thanks14:38
ijohnsonI updated the getgrnam_r PR, but some of the code I changed has to do with sudo, so I would like some extra eyes on it14:38
ijohnsoncachio: so regarding #9027, I think it is actually pretty unfortunate but I don't think we have another option right now, because there doesn't seem to be a way for us to identify the case where we have a real bug in snapd vs this bug in qemu where the system gets rebooted randomly in the middle of the test14:51
mupPR #9027: tests: refresh/revert snapd in uc20 <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9027>14:51
ijohnsoncachio: I think we need to just merge it with the changes you have and expect that the test is very flaky / fail often due to this qemu bug14:51
cachioijohnson,15:01
cachiook15:01
cachioI'll try a new change with the gce platform to see if it improves15:01
mborzeckiok, the ci jobs are running, seems like the most problematic bits of 2.45.3 are done, need to run some errands now, but i'll check in on the PRs later15:01
ijohnsonthanks mborzecki !15:02
=== King_InuYasha is now known as Conan_Kudo
=== Conan_Kudo is now known as King_InuYasha
zyga-x240ijohnson: https://github.com/snapcore/snapd/pull/9041#pullrequestreview-45343832315:40
mupPR #9041: osutil/group.go: treat all non-nil errs from user.Lookup{Group,} as Unknown* <Bug> <Needs security review> <Preseeding 🍞> <⚠ Critical> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9041>15:40
ijohnsonthanks zyga-x24015:40
* cachio lunch15:42
pedronisijohnson: I need a break and then I'll try to go over that least of UC20 PRs16:14
ijohnsonpedronis: k, sounds good16:14
mupPR snapd#8980 closed: tests: backport preseed test fixes to 2.45 <Test Robustness> <Created by stolowski> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/8980>16:17
pedronismmh, I forgot about that one, that's bit the issue with long lived PRs16:21
ijohnsonwhich one ?16:22
pedronisthe backport pawel did16:22
pedronisalready16:22
pedronis898016:23
ijohnsonah yes16:23
ijohnsonwell for that one I think pawel made changes there that weren't on master so it would have been a bit tricky to merge the release branch back to master when time came to actually finalize the release16:24
mupPR snapd#9048 opened: .github/workflows/snap-build.yaml: build the snapd snap via GH Actions too <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9048>16:37
* ijohnson may have opened a new PR, but also closed an old one, so net PR count change is 016:38
* ijohnson goes back to actual productive things16:39
mupPR snapd#8143 closed: github: add github workflow <⛔ Blocked> <Created by sd-hd> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/8143>16:42
pedronisijohnson: that list of UC20-related PRs seems fine, the questions I suppose is whether they backport cleanly?16:56
ijohnsonpedronis: not sure, but I can check16:56
ijohnsonpedronis: if they backport cleanly shall I open a PR with them included ?16:57
* ijohnson is about to break for lunch16:57
pedronisijohnson: yes, but needs to be on top of the two things we want to land16:57
pedronisijohnson: so maybe wait a bit?16:57
ijohnsonpedronis: which ones, mborzecki already landed one of them I think16:57
pedronis#9042 and #9047 ?16:58
mupPR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>16:58
mupPR #9047: cmd/snap-preseed: backport fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9047>16:58
ijohnsonah ok16:58
pedronisunless I'm confused, which can be, I'm slightly exhausted atm16:58
ijohnsonpedronis: it's okay I know what to do, I can land these PR's in my PM if they are green, I will do a double-check on 9042, but the other one is aleady approved16:59
=== ijohnson is now known as ijohnson|lunch
zygare17:02
zygaback after painkillers17:02
zygasorry the overlap hours are not great17:02
zygaijohnson|lunch: https://github.com/snapcore/snapd/pull/9048#pullrequestreview-45351539917:06
mupPR #9048: .github/workflows/snap-build.yaml: build the snapd snap via GH Actions too <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9048>17:06
ijohnson|lunchzyga, we may be able to leverage that in the builds themselves, I haven't looked into it too much I really just copied what joedborg did for the microk8s snap GitHub actions :-P17:16
cmatsuokabuild queue blocked again?17:16
zygalook at the time 16 minutes!17:16
zygathat's 16 less in each of the re-execing systems17:16
zygacmatsuoka: let me check17:17
zyganot stuck - processing loads of jobs17:18
cmatsuokaah ok, thanks17:18
zygamany are close to 40 minute CPU time17:18
zygathis is usually when they end17:18
zygabtw, if anyone has decent home network17:19
zygaand a spare laptop17:19
zygaI we can grow the pool17:19
zygaanyway17:20
cmatsuokawhat kind of access is needed? I have a machine here but it's only accessible via ipv617:20
zygaonly private IPv4 address17:21
zygaa machine behind lan is ok17:21
zygait reaches out to github17:21
zygaI don't think ipv6 is supported in practice17:22
cmatsuokaI have ipv4 but it's behind a nat, if that's ok I can set up a couple of nodes here to see what happens17:23
cmatsuokajust send me the directions17:23
zygasure17:23
zygalet me find the repo17:24
zygahmmm, where is it?17:27
zygaactually17:29
zygacmatsuoka: do you know things like ansible or other "magic" frameworks for deployment>17:30
zygamy instructions work but are really manual17:30
cmatsuokazyga: I know that they exist, but never used them17:30
cmatsuokamanual is good, we learn a lot doing things by hand17:31
cmatsuokaas long as I don't have to do it multiple times17:31
zygacmatsuoka: let's do this some other time - the real version that would allow snapd to benefit requires admin access to the repo17:35
zygacmatsuoka: I can recommend two things17:35
zygacmatsuoka: I'll share the doc I wrote17:35
zygaand the scripts17:35
zygaand I'd recommend deploying that for a personal repo17:36
cmatsuokaok17:36
zygayou will learn the process17:36
zygaand improve it as well17:36
cmatsuokasounds good17:36
zygacmatsuoka: my recommendation is to do this on a focal system with focal containers17:40
zygadrat, I'm terrible at google docs17:40
zygaI know for a fact there's a gdoc17:40
zygalet me try on my phone17:40
zygagoogle is the worst UX company on this planet17:41
zygaborland docs would be better17:41
cmatsuokafinding stuff in gdocs is hard, these guys should learn something about searching17:41
cmatsuokaoh wait17:41
zygahaha17:41
zygaright?17:41
zygainstalling the app17:44
* zyga searches gmail17:50
zygaI'm lost17:51
zygasorry, I wonder where that is17:51
cmatsuokasomeday you'll find it, and then you tell me17:52
* pedronis admits to have made a gdoc with links to other gdocs18:14
=== ijohnson|lunch is now known as ijohnson
mupPR snapd#9024 closed: sysconfig/cloudinit: add RestrictCloudInit <Created by mvo5> <Merged by anonymouse64> <https://github.com/snapcore/snapd/pull/9024>18:37
* cachio kinesiologist18:46
ijohnsonzyga: https://github.com/snapcore/snapd/pull/9048#issuecomment-66262588418:52
mupPR #9048: .github/workflows/snap-build.yaml: build the snapd snap via GH Actions too <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9048>18:52
zygajdstrand: I found one more bug in my implementation of the reproducer of the bug you found19:14
zygajdstrand: testing it now, fingers crossed that it finally shows something19:14
zygatesting that now19:34
ijohnsonuggh why do we have to have infinite amounts of conflicts in cmd_initramfs_mounts.go19:41
* ijohnson cries a little a lot on the inside19:42
* zyga hugs ijohnson virtually19:43
ijohnsonhaha19:43
zygaI had to deconflict some of those snapstate.go things19:43
zygaI learned how to tell my editor "yeah, you can use this much memory"19:44
ijohnsonhaha so true19:44
ijohnsonbefore pstolowski split up that snapstate_test.go file, a conflict there was sure to crash my editor19:44
zygajdstrand: no luck, I wrote a much more elaborate test that really mimics what you experienced except there's no failure yet :|20:04
jdstrandweird. I took my system out of it and did it in a vm in the bug...20:04
zygaI will try with your snap verbatim20:05
zygaI must have missed something20:05
zygaI pushed the updated (non failing) test to fix/lp-188830520:06
zygahttps://github.com/zyga/snapd/commit/db5c7c98b666ad3022d67a771706d11291f24da820:07
zygaif you could eyeball that and spot any obviously wrong things I'd love to know20:07
zygaotherwise I will run with your snap in a VM tomorrow20:08
mupPR snapd#9049 opened: release/2.45: backport of uc20 PR's <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9049>20:13
jdstrandzyga: I think those experimental feature can be removed. I didn't carry those into the vm20:13
zygaOK20:13
zygaI will do one more round with a long running process20:13
jdstrandzyga: something that I don't see in this (maybe I missed it?) is that I have a long running process20:15
zygaright20:15
zygaI didn't do that because it should not be a factor20:15
jdstrandzyga: specifically, I have an app indicator that is long running20:15
jdstrandhmm20:16
zygaI though that it is caused by skew in snapd tools as snapd revisions change20:16
jdstrandzyga: are you sure? if there is a process running, isn't there different behavior for mount namespace updates?20:16
zygano because snapd does not trigger mount namespace updates in our model20:16
jdstrandzyga: note that I could always resolve the issue by stopping and starting the indicator20:17
zygathat made me add the "observe" mode20:17
zygaas I realized that may matter20:17
zygastarted one more round with the process running20:18
zygathat is interesting bit of information as well actually20:18
zygait suggests that indeed the namespace "turns stale" somehow20:18
zygaand that starting a process is enough to fix it20:19
zygabut that's unusual as we must have done something to choose to update the namespace20:19
zygaand snapd, again, is not a factor20:19
zygaunless mount profiles changed somehow?20:19
zygajdstrand: no change with running process20:40
pedronisijohnson: I landed 9025, I suppose #9026 need a master merged now20:43
mupPR #9026: tests/nested/manual: add spread tests for cloud-init vuln <Run nested> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9026>20:43
mupPR snapd#9025 closed: overlord,o/devicestate: restrict cloud-init on Ubuntu Core <Created by mvo5> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/9025>20:43
ijohnsonpedronis thanks yes I think so20:45
* zyga EODs20:52
zygao/20:52
mupPR snapd#9040 closed: spread: add opensuse 15.2 and tumbleweed for qemu <Simple 😃> <Created by jdstrand> <Merged by cmatsuoka> <https://github.com/snapcore/snapd/pull/9040>23:14

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!