/srv/irclogs.ubuntu.com/2021/06/01/#snappy.txt

mborzeckimorning05:48
mardymborzecki: hi!06:02
mborzeckimardy: hey06:02
mborzeckimvo: hey06:50
mvogood morning mborzecki 06:51
zyga-mbpgood morning06:53
mvogood morning zyga-mbp 06:58
mvofwiw, 10287 needs a second review06:59
pstolowskimorning07:03
mvogood morning pstolowski !07:07
zyga-mbppstolowski nice work!07:07
zyga-mbpoh wait, that was actually ian!07:08
zyga-mbpsorry ian and pawel07:08
zyga-mbpI'm a bit sleepy still07:08
pstolowskihey zyga-mbp  :)07:08
mborzeckimvo: reviewed, there seems to be some race in the test, google:centos-8-64:tests/main/snap-quota-groups failed and there's more than 1 task in the cgroup07:08
mborzeckipstolowski: zyga-mbp: hey07:08
mvomborzecki: oh, interessting, thanks, looking07:10
mvomborzecki: I think I do a followup, this is strange07:21
mborzeckimvo: that's fine, let's land it and we can tweak the test later07:22
mborzeckiat least the whole feature will progress07:22
mvo10329 should now also be unblocked07:32
mborzeckianother one merged, we're down to 65 PRs07:51
mborzeckimvo: i've added some comments to https://github.com/snapcore/snapd/pull/10329 i can address those once i push out an rfc with serial & remodel, unless you want to have a go at it first08:12
mvomborzecki: go wild, I'm looking at spread things right now08:13
pedronismborzecki: does it mean the task count is always 0 on centos ?08:24
mborzeckipedronis: it's not, https://paste.ubuntu.com/p/R487f3RGRy/, disabling TasksAccounting makes system not create a group for the slice under the pids controller 08:29
mborzeckipedronis: at least that what i determined through experimentation08:29
mborzeckipedronis: oh and when there's no cgroup, that's the current tasks count i get: TasksCurrent=18446744073709551615 so fun again08:30
mborzeckiotoh, the value of MemoryCurrent is 0, so not sure what's really happening there08:31
pedronismborzecki: I suspect we shoild just not support this there for now, it seems need a lot of attention and we don't really know what other bugs might hide there08:32
mborzeckiit's only high when there's no memory controller at all, i.e. no memory limit set for given slice08:32
mborzeckiwhere high == exabytes ian saw08:32
pstolowskimvo, pedronis there's an interesting old comment from zyga-mbp on a download gettng stuck bug here: https://bugs.launchpad.net/snapd/+bug/1891618/comments/208:37
pedronismborzecki: mvo: it sounds like we would need a lot spread tests to be sure things actually work08:38
pedronismborzecki: mvo: anyway I don't think it makes sense to block the chain of PRs on this, it's probably best to not support these systems and reconsider later08:39
mvopstolowski: that is interessting indeed08:39
mvopedronis: +1 for not supporting these old systemds08:39
zyga-mbpmvo is it possible to move snapd to latest go?08:39
mborzeckipedronis: mvo: added one more comment with more explanation and a pastebin08:39
mborzeckipedronis: postponing support for older systems sounds like a good call, we can always revisit this once we've done more experiments08:42
mborzeckiwondering if systemd somehow reports that memory controller is available at all08:43
pedroniszyga-mbp: we plan to move to 1.13 but not latest08:43
mborzeckizyga-mbp: do you recall anything like that in systemd? ^^08:43
zyga-mbpmborzecki like what exactly?08:43
mborzeckizyga-mbp: whether it's possible to find out if memory controller is even available08:44
zyga-mbphmmm08:44
zyga-mbpisn't that visible in mountinfo in v1?08:44
mborzeckiiirc it doesn't need to be mounted if memory accounting is disabled globally, and then you can always disable it in the kernel08:45
zyga-mbp(in v2 you have to consult what's enabled in the part you belong to08:45
mborzeckizyga-mbp: it is ;) but i'm more into poking systemd to know if that's doable08:45
zyga-mbpI see08:45
zyga-mbpI don't recall _but_ systemd has extensive dbus apis08:45
zyga-mbpperhaps it's somewhere there08:45
zyga-mbpI'd have to look08:45
mborzeckizyga-mbp: hm yeah, i should take a quick look08:46
zyga-mbpthere is a property 08:47
zyga-mbpMemoryAccounting08:47
zyga-mbpbool 08:47
zyga-mbpon org.freedesktop.systemd1.Service 08:47
zyga-mbpbut I'd double check how it is implemented to know it is what you want08:47
zyga-mbpmborzecki https://github.com/systemd/systemd/blob/7dbc38db509f153256d3a3bfe6cbb26e2731c741/man/systemd.resource-control.xml#L26908:50
mborzeckizyga-mbp: mhm, thanks, looking at it08:52
=== doko_ is now known as doko
mardypstolowski: does this line look totally correct to you? https://github.com/snapcore/snapd/blob/master/overlord/servicestate/service_control_test.go#L29510:21
mardyshouldn't the action name be "test-snap.foo"?10:21
pstolowskilooking10:22
pstolowskimardy: correct. it works because makeControlChange test helper creates apps out of it and current implementation of servicestate.Control() doesn't care about inst.Names anymore and uses apps. So it's confusing but test-only issue afaict10:31
mardypstolowski: good! Then I guess it's fine if I make a small change to makeControlChange and to the tests, to use the fill names, right?10:32
mardys/fill/full/10:32
pstolowskimardy: yes, sounds fine10:33
mborzeckipedronis: opened https://github.com/snapcore/snapd/pull/10330 with the check for serial assertion in remodel, need to sort out the spread tests still10:46
pedronismborzecki: thx, I will look in a bit10:47
mborzeckithanks11:00
mborzeckihm i think i got the tests runnig now11:29
pstolowskimborzecki: do you have some time for a 2nd review of https://github.com/snapcore/snapd/pull/10261 ?12:01
mborzeckipstolowski: yes, i can take a look in a bit12:02
pstolowskithx12:03
mborzeckimeh the remodel spread tests12:36
mborzeckipedronis: quick questions, even if i don't put my account & account key assertions in the seed, will they be automatically pulled from the store?13:38
pedronismborzecki: they are needed for first seeding, prepare-image puts them there for you, but  I don't know what the test does13:39
pedronismborzecki: without first seeding can't validate the model13:39
mborzeckipedronis: ok, i need to drop them there then13:39
mborzeckipedronis: the remodel tests, clean all of state from /var/lib/snapd and kick off first boot again13:40
GunnarHjpedronis: Hi Samuele! Apparmor fixes are needed to make fcitx5 (bug #1928360) and to some extent ibus (bug #1890905) work as expected in the snaps. (The fcitx5 task is higher priority.) Any chance you can take it on?13:45
GunnarHjhttps://launchpad.net/bugs/192836013:46
GunnarHjhttps://launchpad.net/bugs/189090513:46
mardypedronis: I forgot to ask you to put https://github.com/snapcore/snapd/pull/10282 back into your review queue :-)13:53
ijohnsonGunnarHj: you might want to also try pinging jamesh about such issues those bugs smell very desktopy to me13:55
pedronisGunnarHj: apparmor fixes in which sense? fixes to apparmor or to our apparmor rules?13:56
GunnarHjpedronis: The fcitx5 issue is about our apparmor rules, but the ibus one is about improving apparmor itself to start with.13:59
GunnarHjijohnson: Thanks for the tip. Yeah, the bugs are indeed desktop'ish.14:00
mborzeckidumped the assertions into a single file, wondering if that will work14:08
mborzeckiwooo, remodel-base workd14:15
mborzeckiand pushed, remodel spread tests should work again15:03
mvomborzecki: \o/15:10
ijohnsonmvo: pedronis: can you land https://github.com/snapcore/snapd/pull/10099 ? the failure on debian-10 are unrelated15:50
ijohnsonmvo: also I noticed you cherry picked https://github.com/snapcore/snapd/pull/10324 to release/2.51, so I added the cherry-picked label to that PR for you15:55
pedronisijohnson: I think mvo beat me to it16:01
ijohnsonyeah, no worries thanks for checking on it though16:01
mvoijohnson: thanks! I keep forgetting this16:09
ijohnsonit will become habit and save us much time in the future :-)16:09
mvoyeah, it's good!16:16
=== ijohnson is now known as ijohnson|lunch
=== ijohnson|lunch is now known as ijohnson
ijohnsonpedronis: can you merge 10331 then ? I will open up our two alternatives after that so you can decide in the AM what direction we want to go 18:12
ogradid anyone tak to iemeyer yet about mup ? 18:12
ogra(i see it re-connecting in a 30sec loop in the old channel ... FWIW)18:13
ijohnsonogra: I thought mvo did already, I assume Gustavo's been a bit busy lately to move it over18:14
pedronisijohnson: how can you open the alternatives if we don't have spread tests about current memory usage?18:14
ograijohnson, ah18:14
pedronisijohnson: we probably want to fix the CLI first18:14
ijohnsonpedronis: well now that the daemon is reporting memory usage, regardless of whether the CLI displays it, if there are problems the CLI dies18:15
pedronisijohnson: yes, but not dying is not a criteria enough to decide on the workarounds18:15
ijohnsonI mean yeah I guess if you want to do the CLI changes first then we can, but we can't really measure the memory usage specifically in the spread test18:17
ijohnsonthe spread test update I had in the CLI change PR just sees that there are numbers in the output, it doesn't actually confirm that the numbers make sense18:17
ijohnsonit would be hard to check that the numbers make sense given that memory usage is not predictable in exact terms, I guess I could compare to make sure the number is under 100 megabytes or something obvious like that18:18
pedronisijohnson: there's probably a min and max that can be applied18:18
ijohnsonI guess in other words, I'm just not sure what the threshold is to decide on the workaround18:19
ijohnsonalright I guess I can write a min/max detection snippet for the functional spread test18:19
pedronisijohnson: do we have a test where we see processes hit the OOM ?18:22
ijohnsonyes that's `tests/main/snap-quota-groups`18:22
pedronisI see one where they don't start, it that the OOM or something else?18:22
ijohnsonyes that's checking the OOM18:22
ijohnsonwell indirectly checking that the service fails due to oom18:22
ijohnsonwe check that the service starts properly with a large limit, then we check that it doesn't start with a small limit18:22
pedronisit seems interfaces-packagekit-control has started failing consistently on arch18:26
pedronisijohnson: I merged that PR, please consider my comment in the next, anyway I still think we want to fix the CLI first thing, before considering the corner case distros18:27
ijohnsonpedronis: ok yes I have that change implemented in the CLI PR, which I will open shortly after adding this min / max logic to the snap-quota-groups spread test for that PR18:28
ijohnsonpedronis: also yeah I saw that test has started to fail, I will try to have a look this afternoon, if I don't get to it, I left a comment about it with logs in the SU doc for someone to look at18:29
pedronisijohnson: I suppose it might be something for Maciej to look at18:29
ijohnsonyeah nothing obvious came up when I looked at it18:30
ijohnsonto me at least18:30
=== axino is now known as ux
=== ux is now known as axino
* cachio afk19:04

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