=== chihchun_afk is now known as chihchun [04:19] PR snapcraft#2353 closed: tests: remove dependency on snapcraft for integration tests === cpaelzer_ is now known as cpaelzer [05:11] morning [05:13] ugh, travis jobs unhappy again [05:43] good morning [05:43] mborzecki: the dreaded accounts service test [05:43] zyga: hey [05:44] yeah, not repeating in isolation :/ [05:44] I reproduced it but didn't noice and closed the session [05:44] ayy [05:44] PR snapd#5990 opened: tests: do not run degraded test in autopkgtest env [05:45] hey zyga [05:45] and hey mborzecki [05:45] mvo: hey [05:45] hey mvo [05:45] good morning [05:45] I haven't seen infinity yet [05:45] zyga: I just asked him in #ubuntu-release [05:45] I kicked off main again, I will try to hunt the accounts service failure [05:45] thanks! [05:46] hm maybe it's something about gce being slow or sth, that online accounts service is dbus activated, isn't it? [05:46] zyga: thank you - all autopkgtest are good except for the degraded one [05:46] zyga: I do the proper release now (without the umount fix sadly) [05:54] mborzecki: unlikely, bus activated services get the socket from systemd, right? [05:54] mborzecki: so you'd race with systemd [05:54] well - we shall see really [06:12] PR snapd#5966 closed: snap: overhaul validation error messages [06:16] PR snapd#5991 opened: release: 2.35.5 [06:21] PR snapd#5992 opened: release: merge 2.35.5 changes into the 2.36 branch [06:24] https://blogs.gnome.org/tbernard/2018/10/15/restyling-apps-at-scale/ <- interesting for theming [06:46] heh pushed a commit with some additional debug to the PR that failed consistntly due to interfaces-accounts-service, and it's failing no more [06:46] why am i even suprised [06:48] brb [06:48] mborzecki: it's just an ordering issue [06:57] zyga: i'm not so sure, the testt that executed before this one do not seem reelvant [07:01] mborzecki: I sent a trivial PR, we'll see [07:02] zyga: are debug sections meged together? [07:02] PR snapd#5993 opened: tests: show list of processes when ifaces-accounts-service fails [07:03] mornings [07:03] pstolowski: hey [07:09] Oh! No [07:14] pulled logs from 6 failed runs, dropped into python to check if there's a test common to all failed jobs that ran before, seems there's no connection there [07:15] maybe we shuld just switch this test to manual to unblock prs [07:23] zyga: this is what i'm trying with here https://paste.ubuntu.com/p/Ktcj47ZDqh/ [07:29] PR snapd#5991 closed: release: 2.35.5 [07:31] PR snapd#5990 closed: tests: do not run degraded test in autopkgtest env [07:45] mborzecki: the failure mode of that test look like the are different services that provide similar but different apis for something, it's quite weird [07:55] PR snapd#5994 opened: tests/main/interfaces-accounts-service: more debugging [08:04] https://www.reddit.com/r/linux/comments/9oddtb/flatpaks_sandboxes_and_security/ another *pak & sandbox thread [08:10] PR snapd#5984 closed: ifacestate/hooks: only create interface hook tasks if hooks exist (2.36) [08:10] woot, that's great [08:10] thank you again pstolowski [08:10] I will try to optimise apparmor use next week [08:10] zyga: sounds awesome! [08:17] man, reading reddit is a waste of time [08:18] zyga: heh, usual bs in the comments [08:18] BS is one thing, I really cannot stand people that claim to know something but are clearly clueless about it [08:23] btw. on the topic of desktop themes, anyone running kde? do gtk apps from snaps have breeze properly applied to them? [08:24] mborzecki: sorry, I'm on gnome usually [08:24] but on the bright side, we will always have Adwaita [08:29] eh [08:29] not a great morning [08:30] sil2100: bad news, probert seems to be still crashing, I have a theory (only tested on my pi3-64) [08:30] question, what is probers? [08:30] probert [08:40] we need a "this topic provides no added value" thing for the forum :-| [08:40] * zyga hugs Chipaca [08:41] what topic is that? [08:41] zyga: today, it's https://forum.snapcraft.io/t/gnome-calendar-is-not-in-spanish/7866/11 [08:41] if it were a support ticket, i wouldn't mind [08:43] also, ps, spanish is not a regional language :) [08:45] mvo: oh no [08:45] Let me check if the right version has been pulled in [08:46] Yeah, it looks like it [08:46] mvo: so it's still crashing at the same place in console-conf? On startup? [08:48] zyga: has anything reached master since yesterday? [08:48] not that I know of :/ [08:48] let me look [08:49] Chipaca: actually, I'm mistaken [08:49] 063f83e687d1fa2d339bc123ff5c37a2030afb50 landed [08:49] zyga: hello mistaken, i'm Chipaca [08:49] I'm Zygmunt if I'm not mistaken [08:49] ;-) [08:49] (or both, knowing me) [08:50] mborzecki: does 'gdbus monitor' work withouot --dest? [08:51] $ gdbus monitor --session [08:51] Error: Destination is not specified [08:51] zyga: did you try a new image on your dragonboard? [08:51] mborzecki: go with dbus-monitor --session [08:51] sil2100: I only have the image from Friday [08:52] shall I re-download http://people.canonical.com/~lzemczak/dragonboard.img.xz ? [08:53] PR snapd#5995 opened: tests/main/interfaces-accounts-service: switch to manual while we debug the test [08:54] Chipaca: see #5994 [08:54] PR #5994: tests/main/interfaces-accounts-service: more debugging <⛔ Blocked> [08:55] mborzecki: better :) [08:55] mborzecki: or was it always like that, and I'm in need of more coffee? [08:55] meh, now travis is not doing much [08:55] ohhh coffee [08:55] Chipaca: no, i mistyped it, had it `dbus monitor` before [08:55] I could use that [08:55] hah, even more fun [08:56] did eavesdrop need to be expliclitly enabled for session bus? [08:57] not that I recall [08:59] mborzecki: what about checking the package version of accountsservice? [09:00] Chipaca: that should be the same as if you spin up the test image [09:01] hm, tru [09:01] e [09:03] Chipaca: gnome-online-accounts 3.18.3-1ubuntu2 [09:07] btw. pushed a repo with a minimal spread setup i use to spin up images, faster and smaller than doing the same from snapd tree https://github.com/bboozzoo/spread-mini === chihchun is now known as chihchun_afk === cpaelzer_ is now known as cpaelzer [09:12] mborzecki: also: gdbus introspect --session --dest=org.gnome.OnlineAccounts --object-path=/org/gnome/OnlineAccounts/Manager === chihchun_afk is now known as chihchun [09:35] WTF, travis [09:43] mborzecki: zyga: as travis is kinda stuck, would you mind merging #5994 and #5993 into a single one? [09:43] PR #5994: tests/main/interfaces-accounts-service: more debugging <⛔ Blocked> [09:43] PR #5993: tests: show list of processes when ifaces-accounts-service fails [09:43] hahah [09:43] oh wait one of them is already running [09:44] ¯\_(ツ)_/¯ [09:48] ok, hm last time we were debugging this test the observation was that the signature returned as 'expected' is correct and matches that of AddAccount [09:49] zyga: I'll rebuild it in a moment [09:49] (the image) [09:49] sil2100: ok [09:49] looking at my notes i was digging into gdbus to see if there's some parsing error [09:49] I'm on the release sprint right now and we need to fix ubiquity first [09:49] sure [09:54] sil2100: sorry for the delay, had a call - my mistake, console-conf is working! [09:57] mborzecki: ISTR gdbus was funny about how it interpreted arguments [09:57] Chipaca: i switched to busctl now, will push a commit in a minute [09:57] mborzecki: but you can specify the type [09:57] at least this one is explicit about the types [09:58] mborzecki: ah, good [10:06] mborzecki: what is the chance that with more debugging it will no longer fail ;-) ? [10:07] zyga: high :) [10:07] still, I'd love to merge it [10:07] to see what is wrong [10:08] I'm wary of merging your branch with extra kills and what not just because we don't know the problem yet [10:08] the upside is we'll know more the next time it appears [10:08] yes, exactly [10:08] zyga: i'll drop pkills [10:15] mvo: \o/ [10:15] mvo: sweet! [10:16] I'll prep a quick image for zyga in a moment for the db and upload it somewhere, since I'm at the office it should be a fast upload [10:16] cool [10:18] zyga: while pipe2 instead of socketpair in your pr? [10:18] no preference really [10:19] also no need to use sockets :-) [10:20] zyga: Chipaca: please take a look at #5994 [10:20] PR #5994: tests/main/interfaces-accounts-service: more debugging <⛔ Blocked> [10:21] what is in dbus.env? [10:22] zyga: when you dbus-launch it spits some stuff you can eval in the shell to set the environment variables, now it's dumped to a file in case i need to use it in debug section [10:24] right [10:24] I know that, [10:24] what is there in practice :) [10:24] is it just a variable definition? [10:24] DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-QvYL1sZnrl,guid=78c09efa6f3ce976cbffb0a35bc5bc72'; [10:24] export DBUS_SESSION_BUS_ADDRESS; [10:24] DBUS_SESSION_BUS_PID=25966; [10:24] DBUS_SESSION_BUS_WINDOWID=119537665; [10:25] zyga: https://paste.ubuntu.com/p/TTh392C3Bb/ [10:25] aha, I see [10:25] thanks! [10:25] oh, windowid? [10:25] wonder why i don't have it [10:26] mborzecki: probably because I did it from within X and you didn't [10:26] mborzecki: my PR passed [10:26] let's merge it [10:26] man, I knew this would happen [10:27] Chipaca: hm did it in tmux, which was in turn started by systemd user session, maybe that's why [10:27] sil2100: flashing now [10:27] an extra downside of this accounts service silliness is that it took me a day to see a trivial bug in my shutdown pr [10:28] now let's reproduce the f*r [10:28] PR snapd#5993 closed: tests: show list of processes when ifaces-accounts-service fails [10:28] zyga: thanks! Fingers crossed it's all resolved here as well [10:30] we will know soon [10:33] PR snapd#5996 opened: [RFC] daemon: support `snap logs snapd` to get snapd logs [10:35] cachio: good morning! new snapd 2.35.5 in beta - sorry for yet another dot release :/ [10:35] cachio: but .4 is fine, this is just yet another fix on top [10:37] PR snapd#5997 opened: ifacestate: simplify task chaining in ifacestate.Connect [10:38] mborzecki: ^ the simplification you suggested in previous PRs [10:38] *PR [10:38] nice pstolowski :) [10:38] pstolowski: nice [10:40] sil2100, mvo: booting ... [10:40] fingers crossed [10:43] sil2100, mvo: no more crashes! [10:43] woot [10:43] zyga: yay [10:43] sil2100: what was the issue? [10:47] sil2100, mvo: although it does not crash I cannot actually connect to wifi [10:47] it times out all the time [10:47] (wifi dit not change) [10:47] zyga: same for me on my pi3-64 [10:47] sil2100: -^ [10:48] bor0en [10:48] or just broken === prime is now known as Guest4938 [10:51] mvo: want me to give the appInfosFor a stab? I'm blocked waiting for spread otherwise :-) [10:51] bah, i've got other things i could do [10:52] like lunhc [10:52] lunch [10:52] but that's boring [10:57] sil2100: do you need that reported? [10:59] PR snapd#5998 opened: osutil: tweak handling of error adduser errors [11:01] Chipaca: app infos for as in 5996? [11:01] mvo: ah, yes :-) [11:02] Chipaca: I would not mind - but note its still an RFC PR that needs approval from gustavo [11:03] mvo: actually we could expose a pseudo-snap 'snapd' in /v2/snaps [11:04] Chipaca: that works for me [11:04] Chipaca: no strong opinion either way [11:04] mvo: snapInfosFor calls allLocalSnapInfos, if we make that one pseudo-snapd-aware, we get a consistent pseudo-snapd in the api (except you can't remove/refresh/etc it sometimes) [11:04] (the latter makes it awkward, i guess) [11:04] bah :) [11:05] it depends on what we want [11:05] i'll comment on the rfc [11:05] * mvo nods [11:05] thank you! [11:07] Chipaca: we have system and snapd (as pseudo but not quite things), should snap logs system do the same, do something? [11:07] all of this is cute but without a plan it will get messy [11:07] snap logs system giving just snapd logs feels weird though [11:08] yea, agreed [11:08] also snapd will be a snap [11:08] but without services [11:08] so all kinds of weirdness [11:09] zyga: yeah, not sure what's the reason for that not working, I think I also had wifi issues on my regular armhf rpi3 core18 last time [11:09] pedronis: zyga: FC on the RFC [11:09] Not sure if that got reported somewhere [11:09] I guess Paolo was looking at something like that? [11:10] Chipaca: my C is mostly that it probably needs a forum topic [11:16] sergiusens: what was the env var that dropped snap/snapcraft.yaml and manifest.yaml into the snap? [11:18] Chipaca: I think SNAPCRAFT_BUILD_INFO=1 from here: https://forum.snapcraft.io/t/notifications-for-out-of-date-stage-packages/5161 [11:18] thanks [11:27] Chipaca: I see you found it [11:28] sergiusens: yes, thanks [11:28] we're at the brink of opening 3rd page of PRs... would be good to land some [11:28] grep took me to the tests, and then samuele confirmed it :) [11:28] pstolowski: har har [11:29] Chipaca: hah, I thought you would have done a forum search first 😉 [11:29] pstolowski: dunno if you noticed but we've been fighting the spread tests since at least yesterday [11:30] pstolowski: well, stuff is blocked by travis atm [11:30] Chipaca: yes i'm aware [11:30] pstolowski: almost everything in the first page is red [11:30] hopefully we can land #5994 soon [11:30] so, i mean, sure it'd be nice to land stuff [11:30] PR #5994: tests/main/interfaces-accounts-service: more debugging <⛔ Blocked> [11:32] mborzecki: it failed in my PR [11:32] zyga: hm, which one? [11:32] https://www.irccloud.com/pastebin/OuTgkBZz/ [11:33] https://github.com/snapcore/snapd/pull/5988 [11:33] PR #5988: cmd: rename ns_group to mount_ns [11:33] zyga: is that goa using 100MB of mem/ [11:34] apparently [11:37] anyone willing to look at #5959 while we wait for PRs to be green again? [11:37] PR #5959: systemd: extend Status() to work for socket and timer units === juergh_ is now known as juergh [11:41] mborzecki: done [11:41] zyga: thanks! [11:44] mvo, hi [11:44] sure [11:44] mvo, I'll make a run [11:44] mborzecki: I pushed https://github.com/snapcore/snapd/pull/5999 [11:44] PR #5999: tests: ensure that goa-daemon is off [11:44] not sure if this is a red herring or real [11:44] mvo, should we promote 35.4 to stable? [11:45] PR snapd#5999 opened: tests: ensure that goa-daemon is off [11:47] Chipaca: #5961 gtg [11:47] PR #5961: snap/pack, snap/squashfs: use type to determine mksquashfs args [11:48] zyga: i'm not sure it's a problem though, the original error is Error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Type of message, '(ssssa{ss})', does not match expected type '(sssa{sv}a{ss})', so the expected type is correct and matches what busctl introspect shows [11:49] zyga: the mystery is why gdbus came up with (ssssa{ss}) [11:50] zyga: it's like it's treating '{}' as s instead ov a{..} [11:50] and only occasionally [11:51] off to pick up the kids [11:52] Hi everyone [11:53] hey [12:00] mvo, zyga: another good news - we seem to have everything for enabling core18 dailies, so I'll do that once we spin out latest RC images for cosmic [12:00] As I don't want to eat up precious resources before we're done with those [12:00] sil2100: ok let me know if you need any more testing [12:10] PR snapcraft#2355 closed: extensions: cleanup and generic tests [12:12] PR snapd#6000 opened: snap,client: use a different exit code for retryable errors [12:14] cachio: yeah, 2.35.4 can go to stable [12:14] mvo: do you need #5986 squashed? [12:14] PR #5986: data/systemd, wrappers: tweak system-shutdown helper for core18 <⚠ Critical> [12:15] sil2100: nice, thanks! [12:15] sil2100: did our 2.35.5 snapd upload from cosmisc-proposed made it? [12:15] also dunno what makes gdbus go ssssa{ss} instead of sssa{sv}a{ss} but it looks like it's over it for a bit [12:15] :-( [12:16] Chipaca: yes, please squash 5986 it will be needed for 2.36 [12:16] Chipaca: and thanks for this PR, nice job! [12:16] mvo: should i retarget it? (it's currently targetted to 2.35) [12:16] targeted* [12:16] Chipaca: yeah, I really really job we are done with 2.35 [12:16] :) [12:17] pedronis: I pushed a PR for the retryable errors, iirc field was askign for this in the context of auto-connect (just fyi) [12:18] ogra: I'm trying to rotate the HDMI display connected to my Pi 3B running Core edge (edge because I need the mir-kiosk snap). setting pi-config.display-rotate=1 and then rebooting seems to bog the system, it does not boot up at all anymore. Removing the option from config.txt (SD inserted into the reader on my main machine) allows proper boot again. This does not occur on Core stable. Is this known or should I open a forum thread? Couldn't find [12:18] anything there. [12:18] PR snapd#5986 closed: data/systemd, wrappers: tweak system-shutdown helper for core18 <⚠ Critical> [12:19] PR snapcraft#2356 opened: nodejs plugin: add support for bases [12:20] pstolowski: thanks for the review! I'll add a comment to Alike in a followup (but note it's only there for tests) [12:21] Chipaca: k, yes, i know it's for test [12:21] mvo: ah, I see, was confused for a second (too many problems with similar terms) [12:21] PR snapd#5961 closed: snap/pack, snap/squashfs: use type to determine mksquashfs args [12:29] mvo: hey, do you want a 2.36 branch for PR 5989? [12:29] error: cannot communicate with server: Post http://localhost/v2/snaps: write unix @->/run/snapd.socket: write: broken pipe [12:29] PR #5989: interfaces/system-key: add parser mtime and only discover features on write [12:29] man, my trivial PR is red for 40 hours over random stuff [12:29] zyga: hey, I know the feeling [12:29] yeah :| [12:30] "do I really want to fix that typo?" ;) [12:30] mvo: the graceful restart thing, is that a thing? [12:30] graceful restart breaking snap install (perhaps) https://www.irccloud.com/pastebin/6cblPVl4/ [12:31] jdstrand: "let's start with this simple PR" [12:32] zyga: "I'll just merge from trunk" [12:32] jdstrand: I actually tried to debug various failures [12:32] zyga: I see you are looking at the accounts-service ones. thanks! [12:32] but this is not the very best of Tuesdays [12:33] been seeing those a lot [12:35] jdstrand: yes please - 2.36 for 5989 [12:36] zyga: hm, the graceful stop breaks? or start? the log you pasted looks harmless? [12:36] re [12:36] snap install died on unix socket hangup [12:37] error: cannot communicate with server: Post http://localhost/v2/snaps: write unix @->/run/snapd.socket: write: broken pipe [12:37] zyga: oh? do you have more details? [12:37] zyga: got journactl of snapd? [12:37] doesn't look transparent [12:37] https://api.travis-ci.org/v3/job/441691823/log.txt [12:37] zyga: thanks, let me look [12:37] look for "error executing" please [12:37] save the log guys, I really want to land and iterate :/ [12:37] so I want to restart that job [12:37] just tell me when please [12:38] zyga: right, I see the error [12:40] mborzecki: ready? [12:40] zyga: yeah [12:40] restarting job [12:40] mvo: isn't that just snap (the client) polling and hitting /run/snapd.sock with some unfortunate timing? [12:41] mborzecki: the log looks odd, it looks like core got installed [12:41] mborzecki: and with a snap snapd should not go into stop mode [12:42] mborzecki: aha, no - just the core configureation, hm [12:42] mborzecki: maybe it is just unfortunate timing [12:42] mborzecki: which still sucks :/ [12:45] mvo: I'm more and more convinced we should do something with systemd to ensure we can shut down gracefully [12:45] (that is, pass the fd back and exit) [12:45] and then let systemd handle the grace period where we are going down [12:48] zyga: right, I'm not sure how to do that race-free yet, I am looking into a test to reproduce the current issue now [12:51] zyga: afaiu this is a remote end doing shutdown on a connection [12:56] niemeyer: mvo: hi, reminder that I have a conflict with the standup [12:57] mvo: did you look at sd_pid_notify_with_fds ? [12:57] pedronis: Ack, thanks [12:57] zyga: I did not [12:58] zyga: thank you, I have a look now [12:59] zyga: aha, neat, that looks interessting [13:01] https://github.com/snapcore/snapd/pull/5994 is green, land it? [13:01] PR #5994: tests/main/interfaces-accounts-service: more debugging <⛔ Blocked> [13:05] PR snapcraft#2357 opened: scons plugin: add support for bases [13:18] PR snapd#6001 opened: interfaces: typo 'allows' for consistency with other ifaces [13:29] PR snapd#5994 closed: tests/main/interfaces-accounts-service: more debugging [13:37] PR snapd#5988 closed: cmd: rename ns_group to mount_ns [13:42] https://paste.ubuntu.com/p/3D95h34pXs/ [13:44] heh, so i broke dbus/gdbus/goa https://paste.ubuntu.com/p/4bF95krMWf/ [13:47] PR snapd#5995 closed: tests/main/interfaces-accounts-service: switch to manual while we debug the test [13:48] PR snapd#6002 opened: interfaces/system-key: add parser mtime and only discover features on write - 2.36 [13:52] mborzecki: the dbus snakes are attacking [13:52] zyga: might be worth re-running the tests on 5170, they were last run 19 days ago [13:52] pstolowski: great point [13:53] pstolowski: they will fail on accounts service ;-) [13:53] :) [13:55] PR snapd#5998 closed: osutil: tweak handling of error adduser errors [14:05] mvo: fyi, https://github.com/snapcore/snapd/pull/6002/ [14:05] jdstrand: thank you! [14:05] PR #6002: interfaces/system-key: add parser mtime and only discover features on write - 2.36 [14:07] mvo: fyi, I'll let you decide on PR 5980, PR 5981 and PR 5982 for 2.36 (I'm not pushing for it-- might be nice to have more testing), but it would be nice if they were in trunk by SLC [14:07] PR #5980: interfaces/apparmor: conditionally add explicit deny rules for ptrace [14:07] PR #5981: interfaces/many: updates to support k8s worker nodes [14:07] PR #5982: interfaces/many: conditionally use 'unsafe' with docker-support change_profile rules [14:08] mvo: that's just an fyi for what I'm thinking about. I know you're busy, so whatever you decide [14:08] mvo: cachio are are your travis pull requests just stalled? A quick check on your PR run tells me so, our are too 😢 [14:11] sergiusens, we have several on the queue [14:11] but none are running right? just waiting? [14:11] 2 running [14:12] the rest waiting [14:12] 3 running [14:13] ah, I see, closer to the bottom https://travis-ci.org/snapcore/snapd/pull_requests [14:14] :) [14:26] mvo: what is the ETA for core16 coming to stable? Not rushing, just getting my ducks aligned 🙂 [14:26] Chipaca, mvo: shall we land the .po update? [14:28] zyga: I'm not sure I can +1 it at this point :) [14:28] sergiusens: thats a sil2100 question now :) [14:28] sergiusens: foundations works on this [14:28] zyga: yes [14:28] Chipaca: no? why not? [14:28] zyga: mvo: but I +1 the ones mvo committed [14:29] mvo: 5 commits, 4 by me [14:29] Chipaca: haha [14:29] Chipaca: ok [14:29] there, I +1'ed it :) [14:31] PR snapd#5935 closed: po: sync translations from launchpad [14:31] thanks zyga [14:31] hm i can reproduce the problem with dbus when goa-daemon is in the process of dying and a call is made, at least in that situation busctl delivers more meaningful error message [14:32] still, we do not kill goa-daemon in the test [14:32] mborzecki: nice [14:35] mborzecki: my PR has kills it [14:37] zyga: mvo: #5980 has two +1's (from you two), is green, but jdstrand said it was ready for re-review. Seems to me to be a quick one :) [14:37] PR #5980: interfaces/apparmor: conditionally add explicit deny rules for ptrace [14:38] mvo, sergiusens: aaaaa, for core16 it's well, not foundations as far as I know [14:38] mvo, sergiusens: since I don't have upload access for core16 in the store or even snap recipe access (AFAIK) [14:39] sil2100: for core16 it is - for "core" (without the 16) we are still in charge [14:39] mvo feels like it might still be your problem if only to transition correctly 😅 [14:39] sil2100: sounds like we need to fix the access :) [14:40] I could use reviews on #5957 (it unblocks #5955) [14:40] PR #5957: overlord/snapshotstate/backend: fall back on sudo when no runuser [14:40] PR #5955: cmd/snap, tests: snapshots for all <⛔ Blocked> [14:40] sil2100: snap recipe is here https://github.com/snapcore/core16 [14:41] sil2100: and you should have store access now :) [14:41] mvo: thank you! [14:42] sil2100: let me know if I can help, sorry if my earlier reply to sergiusens sounded strange, I think for core16 we need the same mechanisms as for core18, i.e. a watcher that scans for package changes and that then triggers a core16 build plus some (auto) testing [14:43] mvo: sure! The script for core18 is ready btw., just waiting for some time to poke Steve about a nice comfy place for it to be on [14:44] Hopefully I won't have to create a new instance for it, my mojo mojo is weak [14:44] sil2100: cool [14:44] sil2100: yeah, I had the same problem with my cnf-extractor-charm - fortunately I was rescued by IS [14:44] sil2100: speaking of this, thats something I need to talk to steve about as well :) [14:45] sil2100: anyway, none of your concerns (most likely) [14:56] hello! A question, what happens if a snap pre-refresh hook fails? Can it abort the refresh and continue with the existing installed version? [14:59] tomwardill: yes [14:59] tomwardill: it should work that way yes, are you experiencing something else? [15:00] Chipaca, pstolowski: We've not tried yet, was just checking if it worked that way [15:00] is it just a case of exit(1) from the hook? [15:01] tomwardill: yep [15:02] excellent, thanks. [15:02] at least that's what the integration test uses :-) [15:03] sergiusens: anyway, we weren't looking at core16 recently yet [15:03] sergiusens: so I guess it [15:03] argh, I guess it [15:03] (keyboard errors) [15:03] I guess it'll still take a bit [15:05] Since you mentioned it now, I'm doing an image test build to see what's the current state [15:14] PR snapd#6003 opened: cmd/snap: block 'snap help --all' === chihchun is now known as chihchun_afk [16:09] hmm, hmm, snap refresh --offline [16:13] Chipaca: what would that do ? [16:13] pedronis: remember apt-zip? [16:14] no [16:14] https://wiki.debian.org/AptZip [16:14] I see [16:18] pedronis: context is a person in the forum in 'the heart of africa' (says their profile), 3rd world with intermittent energy and connectivity, wanting to only talk to the store once and get everything for multiple devices [16:18] pedronis: I tagged you in one of the topics on this, there's a second (linked to that one) [16:19] anyway, i'm off for a bit [16:20] PR snapd#6004 opened: cmd/snap-confine: reduce verbosity of debug and error messages [16:20] mvo: I think this is what sergiusens may have been reporting. it looks like my 5981, 5989 and 6002 PRs are 'stuck'. 'Details' show all green for 5981, shows spread at 6 minutes for 5989 (did that restart?) and show nothing started for 6002 [16:21] mvo: let me know if I should do something [16:36] dpkg-deb: error: from tar -cf subprocess was killed by signal (Illegal instruction), core dumped [16:36] that's a new error === chihchun_afk is now known as chihchun [17:11] PR snapd#5992 closed: release: merge 2.35.5 changes into the 2.36 branch [17:21] jdstrand: sorry for the slow reply - "stuck> not sure what we can do, I poke around a bit [17:22] hey mvo [17:22] back from sports? [17:22] zyga: yes [17:22] mvo: I wonder if I can and 6001 today [17:24] mvo: there's a deadlock in one of the tests: https://api.travis-ci.org/v3/job/442145572/log.txt [17:24] zyga: urgh [17:24] look for PC=0x5626a1bf1aa1 [17:26] zyga: hrm, hrm, its not even clear where it hangs [17:35] mvo: no worries. let me know if I need to mash any buttons or anything [18:01] mvo: if still here can I land 5999 [18:02] jdstrand: I know there are other priority things on your plate but gentle ping about the oldest open PR: https://github.com/snapcore/snapd/pull/5170 [18:02] PR #5170: interfaces/builtin: add adb interface [18:02] PR snapcraft#2357 closed: scons plugin: add support for bases [18:02] yes. it seems like it, but it isn't forgotten [18:02] that's great, I'll try to review your PRs tomorrow [18:04] jdstrand: I sent a rewording PR for snap-confine but it's just about making the debug and error messages more consistent so I didn't request your review on anything [18:04] there's a 2nd PR about IPC tweak (upgrading eventfd to a full pipe) so that the helper can do more [18:04] I don't think this is security critical either but if you want I can request your review [18:05] though I'd rather not really since it's just the start and I have more after that and it would probably not land this week [18:05] zyga: are they all static messages or is there string handling in the debug/error messages that changed? [18:05] s/is there/are there/ [18:05] nothing new [18:05] just changing existing strings [18:05] no more string manipulation [18:05] (actually less, I remove some of the repeating arguments we keep saying over and over, like snap name) [18:06] In general I tried to make it more terse and more useful [18:13] PR snapd#5980 closed: interfaces/apparmor: conditionally add explicit deny rules for ptrace [18:13] jdstrand: can you please merge master into 5982 [18:14] mvo: FYI: another PR had a deadlock in cmd/snap, something to be wary of === chihchun is now known as chihchun_afk [18:16] jdstrand: and 5981 please [18:16] ok, I gotta go [18:16] promised to watch Han Solo with my son :) [18:16] ttyl [18:19] zyga: nice, thanks! :) [18:19] zyga: enjoy :) [18:32] * jdstrand wonders why 5981 is showing changes to master that were merged in 5980 [18:32] after merging master [18:36] oh, it idn't have it yet [18:36] weird [18:44] PR snapcraft#2358 opened: dotnet plugin: add support for bases [19:10] zyga: same package the deadlock? [19:10] zyga: might be worth running it with go test -count 1000 [19:11] zyga: deadlock? [19:11] ah [19:11] han solo wins [20:25] Hey, my 10 snaps games are published for a while. Only two of them appear in the listing of snapcraft.io [22:35] PR snapd#6005 opened: snap/pack, snap/squashfs: remove extra copy before mksquashfs [23:10] PR snapd#6006 opened: tests: move spread-shellcheck to run-checks --static [23:27] PR snapcraft#2359 opened: [WIP] extensions: add glib