[02:28] @ogra: thanks, it's nice to know how things are populated! [05:28] morning [05:33] brb, new kernel [05:35] re === pstolowski|afk is now known as pstolowski [07:07] morning [07:07] pstolowski: hey [07:08] pstolowski: great that you're around, can you take a look at the lastest patches in https://github.com/snapcore/snapd/pull/7195 ? [07:08] PR #7195: many: fix unit tests getting stuck [07:08] pstolowski: the unit tests job was green 6 times in a row [07:08] sure, excellent! [07:23] yay, #7092 is green \o/ [07:23] PR #7092: packaging: use snapd type and snapcraft 3.x (2/4) <ā›” Blocked> [07:24] hm and so is #7195 :) [07:24] PR #7195: many: fix unit tests getting stuck [07:42] pstolowski: glad --destructive-mode solved your problem [07:49] jamesh: thanks, also for the latest remark re snapd base; we special-case snapd snaps not to pull any prerequisites (base) so it has no effect on snapd. but yes, this is unfortunate, build-base would be better. let's see what what pedronis and mvo think when they are back. thanks again! [07:59] i'll actually go ahead and try to fix it in snapcraft [08:07] and merged [08:08] PR snapd#7195 closed: many: fix unit tests getting stuck [08:08] quick errand, back in 30 or sth [08:44] Chipaca: hey! do you have a moment to discuss an aspect of https://forum.snapcraft.io/t/behavior-change-risk-only-channel-specifications-will-not-switch-track/11769 in a HO? [09:23] re [09:23] stray dogs are fun, idk why they keep coming to us [09:39] pstolowski: yes, sorry i didn't see your message [09:40] Chipaca: np; standup HO? [09:40] sure [09:49] hm, i guess rob is at toronto as well? [10:06] PR snapd#7199 opened: overlord/snapstate: keep current track if only risk is specified [10:09] Chipaca: ^ [10:09] ack [10:37] PR snapcraft#2650 opened: store: send snapcraft-started-at in push requests [10:53] Hey there [10:58] hey zyga, how are you? how is the sprint going? [10:58] Hey, Iā€™m doing good [10:59] The sprint is halfway there. There are some small changes but nothing major yet [10:59] We are doing goodI think [11:00] Look at the roadmap document [11:00] If you have any questions please let me know [11:24] Chipaca: one small annoyance with snap switch & #7199, added a comment, wdyt? [11:24] PR #7199: overlord/snapstate: keep current track if only risk is specified [11:31] pstolowski: 'snap' asks the api for the current snap and shows the channel from there [11:31] pstolowski: see showDone in cmd_snap_op.go [11:31] pstolowski: the same codepath for switch and refresh should it should be the same [11:31] pstolowski: have you tested this IRL [11:31] * Chipaca reaches for his clue-by-four [11:34] Chipaca: nice, missed that. showDone is not currently used by "switch". yep, tested IRL [11:35] pstolowski: switch does _not_ use showDonw? [11:35] that's a bug :-) [11:35] dang [11:36] pstolowski: anyway, switch should either use showDone or call List to look up the current state... ĀÆ\_(惄)_/ĀÆ [11:36] * Chipaca whistles innocently and hides the cluebat [11:38] Chipaca: yep, sounds good, especially as we do that for others. And yes, switch doesn't use showDone yet :) [11:38] Chipaca: ty [11:38] pstolowski: seriously, sorry for the snark [11:38] i need to do better than that [11:39] maybe lunch will help [11:39] * Chipaca takes a break [11:57] this still still comes up occasionally https://paste.ubuntu.com/p/K6PPJnGTpS/ === morphis5 is now known as morphis [12:28] Chipaca: no worries :) [12:32] zyga: investigating #7198 because only logs from rebooting ubuntu-* machines are present, none from ubuntu-core, turns out, the test does not execute on ubuntu-core [12:32] PR #7198: tests: reboot the node when restoring after a test involving lxd [12:34] zyga: ubuntu-core is listed in systems anyway, heh [13:41] sergiusens: did anything change wrt --destructive-mode flag in snapcraft with latest release? [13:59] ijohnson: so.. apparently --destructive-mode changed somehow (or got dropped / broken), it's not recognized anymore, also confirmed by #7092 spread test, which now fails. snapcraft just had new updates in all channels on Jul 30/31. i cannot spot anything about that in changelog/release notes though [13:59] PR #7092: packaging: use snapd type and snapcraft 3.x [14:04] pstolowski, have you tried SNAPCRAFT_BUILD_ENVIRONMENT=host instead ? [14:04] (thats what i typically use in my lxd based builds) [14:05] ogra: i didn't know it, let me try [14:07] ogra: it seems to make snapcraft go into "legacy" v2 mode... and i need v3 feature [14:08] it works fine if you use a base keywrd [14:08] *keyword [14:08] either base: core or base: core18 [14:08] then it will use v3 features [14:12] ogra: ahh, right, that, forgot about it again! [14:12] ogra: ahh, and this is actually what affects --destructive-mode flag [14:12] thanks... so confusing [14:12] heh [14:13] in fact i was playing with base:, removed it for a moment [14:14] sergiusens: nvm [14:14] also ijohnson: mistery solved [14:15] thanks ogra [14:16] np [14:22] glad you figured it out pstolowski [14:59] mborzecki: hey [14:59] mborzecki: do you need me to look at something? [15:00] zyga: updated the list of tests that fail with cgroupsv2 on fedora 30 https://forum.snapcraft.io/t/snapd-with-unified-cgroup-hierarchy/12528/2?u=mborzecki [15:01] zyga: and i'm open to ideas on why reboot via spread fails on 16.04 only https://github.com/snapcore/snapd/pull/7198 [15:01] PR #7198: tests: reboot the node when restoring after a test involving lxd [15:05] hey Chipaca, do you know what units the snapshot sizes from `snap saved` are in? is it megabytes (i.e. 10^6) or mebibytes (i.e. 2^20)? [15:05] ijohnson: where? [15:05] ijohnson: snap saved prints the units [15:06] right it says `1.71MB` [15:06] ah, sorry, now i read you [15:06] but is MB megabyte or is it mebibyte [15:06] marshmellow blobs ... [15:07] mborzecki: Iā€™m in another meeting but I will try to inspe that [15:07] ijohnson: mebibytes [15:07] etc [15:07] i think [15:07] * Chipaca goes to check [15:07] * Chipaca is terrible at context switching today [15:08] ijohnson: it uses 1000s, not 1024s [15:08] ijohnson: so, MB, not MiB [15:08] * Chipaca relaxes [15:08] Chipaca: got it thanks! [15:10] I prefer MH (Mega Hugs) [15:11] although I wouldn't be averse to MiH (Mega binary Hugs) over the innernets [15:22] https://linux.slashdot.org/story/19/07/31/1348226/linus-torvalds-prepares-to-wave-goodbye-to-linux [15:23] robert_ancell: hiya. I'd like to dig into how snapd-glib does the channels ops today, at some point [15:23] robert_ancell: we're doing some slight shifts in semantics and are hoping we can do them without creating more work [15:24] robert_ancell: maybe next week :) [15:24] that permalink gave me the entirely wrong perception of what the content was gonna be about [15:24] diddledan: I might have done that intentionally, had I been evil [15:25] Chipaca, I'm in Toronto right now so this week is probably better overlap than next week when I am home. [15:25] robert_ancell: I imagined you'd be busy and jet lagged this week [15:26] robert_ancell: but, sure. Is your calendar up-to-date such that i could throw a meeting on there? [15:26] robert_ancell: or would you rather do it? [15:26] Chipaca, we just finished the main desktop part so should be less busy for the rest of the week. [15:26] robert_ancell: ah, good [15:26] Chipaca, yes, calendar should be up-to-date [15:28] there's a law that states anything that can be done in javascript eventually will be done in javascript. I think that can be adapted to anything that can run software will eventually be used to mine crypto currencies: https://www.phoronix.com/scan.php?page=news_item&px=Monero-Blackbird-Crypto-Mining [15:28] robert_ancell: sent [15:32] Chipaca, ................accepted! [15:33] shocking [15:35] * Chipaca goes for some tea and something to nom === pstolowski is now known as pstolowski|afk [17:24] * Chipaca out [17:50] PR core-build#49 closed: initramfs: check keypress in run mode [19:56] PR snapd#7200 opened: recovery: update to latest fde-utils === Greyztar- is now known as Greyztar [21:37] PR snapd#7201 opened: GitHub not Github [21:46] PR snapd#7202 opened: tests: sync journal log before start the test