/srv/irclogs.ubuntu.com/2017/12/19/#snappy.txt

mupIssue snapcraft#1816 opened: snapcraft update won't fetch from `SNAPCRAFT_PARTS_URI` <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/issue/1816>01:40
mborzeckimorning06:37
mborzeckimvo: hey06:46
mvohey mborzecki06:46
mvomborzecki: how are you?06:46
mvowhat did I miss06:47
mborzeckigood, thank you06:47
mborzeckihm the test infra is basically failing most of the time06:47
mvo:(06:47
mvosucks06:47
mvomborzecki: what about your matrix idea? was that discussed?06:47
mborzeckimaybe not infra, the travis jobs are mostly failing06:47
mvoany pattern emerging in the failures? or all random?06:48
mborzeckilooks mostly random, i've seen the bug when we try to rm -rf /var/lib/snapd and we get device or resoruce busy06:48
mborzeckialso the bug when we tar some content under /var/lib/snap (or /snap?) and tar complains that the contents got changed while it was working06:49
mvol,06:49
mvook06:49
mborzeckiand i've seen the fuse thing06:49
mborzeckii actually have a log somewhere, let me post that quickly06:49
mvohrm, hrm, sounds like a good focus for the rest of the week then, trying to stabelize things again. I'm also keen to discuss the matrix idea with gustavo06:50
mvo(your matrix idea for per-distro runs in travis)06:50
mborzeckiyeah, we can try that06:51
mborzeckiother than that, there was a silly thing with featured snaps in `snap search --section=database`, the output changed and the tests started failing, the test got fixed06:52
mvoheh06:53
mvothanks for fixing it06:53
mborzeckialso there was a thing with selinux on fedora, dbus silently dropping reply messages from polkit to snapd due to selinux policy, i have a PR open #4404, but i've restarted the travis job like 5 times already, no success06:53
mupPR #4404: data/selinux: allow messages from policykit <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4404>06:53
mborzeckithere's a PR from tyler, #4396 it'd be good to merge it once the tests are green06:55
mupPR #4396: snap: use the -no-fragments mksquashfs option <Created by tyhicks> <https://github.com/snapcore/snapd/pull/4396>06:55
mborzeckimvo: https://paste.ubuntu.com/26213459/ line 942007:01
mborzeckii think it's from your PR btw07:01
mvomborzecki: looking07:04
mvomborzecki: interessting, lots of PIDs hanging around, but that should give us some ideas for a fix hopefully, or at least how to debug further07:17
mvojdstrand: is 4406 something we should pull into the release/2.30 branch (in case there is a 2.30.1?)07:20
mvoelopio: hey, if you are around, do you have an idea about the regressions in http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#snapd for snapcraft? afaict it fails with snapcraft.internal.errors.SnapcraftPartConflictError: Parts 'python-part' and 'catkin-part' have the following file paths in common which have different contents"07:25
mvoelopio: but it passed on "2017-11-23 21:29:41 UTC" in autopkgtest. did the part change out-of-band? i.e. does it come from an external resource?07:26
mvokalikiana: maybe you have an idea -^ ?07:26
mupPR snapd#4406 closed: interfaces/dbus: adjust slot policy for listen, accept and accept4 syscalls <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4406>07:29
kalikianamorning07:45
kalikianamvo: leo is on hols. kyle knows about ros07:47
mvokalikiana: a bit of a meta question is if these parts change outside of the deb - I guess the answer is yes? which would explain why things worked ~4 weeks ago and stopped today(?)07:48
kalikianamvo: they pull in packages from pip, which might've changed07:51
* mvo nods07:53
mvomborzecki: can you have a look at 4408 please?08:05
mborzeckimvo: looking08:06
mvomborzecki: I guess the only interessting bit for you is the PKGBUILD change for arch08:09
mupPR snapd#4408 closed: release: snapd 2.30 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4408>08:16
mborzeckimvo: i'll add a bit more debugging to the fuse interfaces problem08:28
mvota08:29
mupPR snapd#4409 opened: tests/main/interfaces-fuse_support: dump more debugging information <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4409>08:39
mborzeckimvo: have you seen anything like this https://api.travis-ci.org/v3/job/317950947/log.txt ?08:48
mvomborzecki: you mean "internal error, please report: running "test-snapd-tools.echo" failed: cannot find installed snap "test-snapd-tools" at revision 6" ? and friends? I saw it this morning, have not seen it before. its slightly strange08:51
mvomborzecki: do you happen to know if this is reproducible ?08:52
mvomborzecki: or is it a one-off thing?08:52
mborzeckidon't know, i've restarted this build a couple of times already, each time it's failing with somethig, but i have not coollected the logs from each run08:53
mborzeckii'll try to run debian-sid-64 suite on linode manually, see what comes up08:54
mvomborzecki: sounds good08:54
mupPR snapd#4410 opened: tests: make journalctl check wait a bit for output <Created by mvo5> <https://github.com/snapcore/snapd/pull/4410>09:48
mborzeckimvo: looks like we were looking into the same snapd-reexec test10:01
mvomborzecki: yeah, my "fix" is very naive, but maybe it helps10:05
mborzeckimvo: i'm thinkgin we should probably disable all rate limit in journald as well10:06
mvomborzecki: +1 for that10:06
mvomborzecki: heh, my PR is breaking on interfaces-fuse_support10:12
mvomborzecki: two pids10:13
mborzeckihahah10:13
mborzeckiand #4409 has some extra debugs for that10:13
mupPR #4409: tests/main/interfaces-fuse_support: dump more debugging information <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4409>10:13
mvomborzecki: but you added some debug already, right? so I should probably just merge it10:13
mvomborzecki: aha, great10:13
* mvo waits to see what else fails10:13
sergiusensmvo that regression you mention in the tests is something kyrofa fixed/looked at, I don't recall right now though. It is not about pip, but ros uses its own archive10:24
* sergiusens waves10:24
mvosergiusens: thanks and good morning10:24
sergiusenskalikiana hey I assigned a new task for you10:24
mvosergiusens: the important part (to me) is that its not caused by snapd :) so I will ask the sru team to ignore this failure10:24
sergiusensmvo no it is not :-) You should only worry really bad if any of the ones using build-snaps or lxd/cleanbuild fail :-)10:25
sergiusensthere are also snapd tests in there where we install what we build10:25
sergiusensit would be great if we could add filters to adt depending on the rev dep being tested to only run what is relevant :-)10:26
kalikianasergiusens: Yup, saw it.  It's on my list10:26
mborzeckimvo: can you review #4409? the build is green, so we could merge it if the change is ok10:42
mupPR #4409: tests/main/interfaces-fuse_support: dump more debugging information <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4409>10:42
mvomborzecki: sure, nice to see its green10:43
mwhudsongnar gnar, something about reexec-ing breaks in a live session10:44
mupPR snapd#4409 closed: tests/main/interfaces-fuse_support: dump more debugging information <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4409>10:44
mborzeckimvo: thanks10:45
* kalikiana coffee break10:45
mwhudsondid a new core snap get released recently?10:49
mupPR snapd#4411 opened: tests/lib/prepare-restore: disable rate limiting in journald <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4411>10:50
mvomwhudson: not recently, why?11:01
mwhudsonmvo: ah, red herring i think11:02
mwhudsonit's late and i'm confused :)11:02
mvomwhudson: puh, ok :)11:02
* kalikiana starting at the same code for too long without finding the problem, going for a break11:49
mupPR snapd#4412 opened: tests/main/postrm-purge: stop snapd before purge and reinstall the package in restore <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4412>12:20
mborzeckimvo: ^^ think this test might have left the worker in a broken state12:22
niemeyerHellos!12:26
mborzeckiniemeyer: hey12:30
mupPR snapcraft#1817 opened: grammar: support strings <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1817>12:33
kalikianahey niemeyer12:37
sergiusensmvo is `environment` an ordered dict?12:37
sergiusenswondering if I can get away with that and not do variable replacements in snapcraft12:38
sergiusensit is not a big problem if it is not (aside from ordered it would need to apply the entries in a stepped manner too)12:38
jameshany comments on https://forum.snapcraft.io/t/interacting-with-dbus-daemons-app-container-feature/3245 would be appreciated12:38
niemeyerkalikiana: Hey12:44
niemeyerkalikiana: Happy to talk today after the meeting, or in the forum if you'd prefer that12:44
jdstrandmvo: if you're respinning it, sure. if you're not, it can wait if it has to12:45
jdstranddo you want me to create a 2.30 PR?12:46
kalikiananiemeyer: Cool! I'd say have a look at the forum first, and see if it's clear enough. If more context is needed we can have a quick hangout about it12:47
niemeyerkalikiana: Okay, let me look into the forum and respond first.. we can have a call later today if there's still a need12:49
kalikianaOkay. Thanks!12:49
mvomborzecki: oh, nice12:59
mvosergiusens: yeah, env should be ordered iirc13:00
mupPR snapd#4412 closed: tests/main/postrm-purge: stop snapd before purge and reinstall the package in restore <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/4412>13:11
kalikianasergiusens: FYI I added more details to snapcraft#1807 wrt patchelf; I'm running the tests locally to verify if test_container_builds also passes13:23
mupPR snapcraft#1807: tests: run test_cleanbuild in LXD on Travis <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1807>13:23
kalikianawill be going for lunch in ~10, let's see if the tests can pass before I leave13:24
* kalikiana will go have lunch, back in ~1 hour13:37
mupPR snapd#4413 opened: tests/main/postrm-purge: stop snapd before purge <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4413>13:38
sergiusensmvo but is each processed individually and applied? As in, if I have FOO=my-arch and the next entry is LD_LIBRARY_PATH=$SNAP/lib/$FOO, will that work?13:49
mborzeckimvo: https://paste.ubuntu.com/26215262/ empty cmdline?14:01
mvosergiusens: that should work14:01
mvosergiusens: I think there is even a test for this, I can look14:01
mvosergiusens: but it will only resolve things top-down14:01
sergiusensmvo oh, this is great news! I will try it out; probably next year as this year is running low on time14:01
mvoso FOO=my-arch\nBAR=$FOO/x will work but not the other way around14:01
mvomborzecki: that sounds like a race, I bet /proc/28456 does not exit anymore14:02
mvomborzecki: at the point this runs14:02
mborzeckior it's a kernel thread :/14:02
mborzeckibut that shouldn't match the regex14:03
mborzeckioh, w8, not, there's no such file or directory, uhh i'm staring at the logs for too long14:04
mvomborzecki: :)14:05
mvomborzecki: no worries14:05
mupPR snapd#4414 opened: tests/main/interfaces-fuse_support: workaround multiple matching processes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4414>14:27
cachio__mvo, I lost the machine where I reproduced the error, I'll trying to reproduce it again and share that to you14:38
mvocachio__: thank you14:39
kalikianare14:43
mupPR snapcraft#1818 opened: meta: create XDG_RUNTIME_DIR in wrappers <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1818>14:49
mupPR snapd#4391 closed: travis, run-checks: split travis job into build matrix <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/4391>15:12
mupPR snapd#4393 closed: travis: separate unit tests into separate build matrix jobs <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/4393>15:12
mborzeckimvo: can you take a look at #4413 and #4414 later on?15:20
mupPR #4413: tests/main/postrm-purge: stop snapd before purge <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4413>15:20
mupPR #4414: tests/main/interfaces-fuse_support: workaround multiple matching processes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4414>15:20
sergiusenssnappy-m-o autopkgtest 1815 xenial:armhf15:29
snappy-m-osergiusens: I've just triggered your test.15:29
mvomborzecki: ssure15:30
mupIssue snapcraft#1819 opened: Detect and clear executable stack binaries <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/issue/1819>15:46
niemeyermvo: Is there a way to install local .deb files with apt-get so it resolves dependencies?15:46
niemeyermvo: It was possible with apt-rpm, but I don't recall if that ever got ported over15:46
sergiusensniemeyer apt install ./<deb>15:46
sergiusensbut the deb has to be in cwd15:47
niemeyerSweet15:47
mvoniemeyer: what sergiusens said, it should not be needed to be in cwd, but apt expects an absolute path15:57
sergiusensmvo oh, abs path; I had issues with not working out of cwd in the past16:02
mvosergiusens: hm, that might be a bug, the rule is basicly it needs to look like a path so that it is distinguishable (in principle) from a deb from the archive16:04
mupPR snapcraft#1820 opened: Update test_lxd.py <Created by heesen3> <https://github.com/snapcore/snapcraft/pull/1820>16:19
niemeyermvo, sergiusens: Brilliant, it worked fine, thanks!16:29
kalikiananiemeyer: ping16:33
niemeyerkalikiana: pong16:34
kalikiananiemeyer: I'll be eod'ing in 30min - can we have a quick chat still about the arch stuff?16:39
niemeyerkalikiana: I'm having a call (or trying to) with JamieBennett right now, but soon maybe16:40
kalikianaok16:41
ikeybtw re: arch i believe nvidia stuff is wonky there16:41
ikeyim terrified that i might actually have to install arch16:41
ikey._.16:41
niemeyerkalikiana: Jamie is having network issues and I have 8 minutes before he's ready.. want to have a quick chat?16:43
kalikiananiemeyer: yes!16:44
kalikianaikey: I think we're talking about different things. I meant arch as in architecture( grammar in snapcraft)16:53
kalikianalike "on amd64 to armhf:" syntax16:54
ikeyi saw arch and twitched. :p16:55
kalikiana:-D16:59
* kalikiana wrapping up for eod in ~15min - trying to finish one more test case before heading out17:16
mupPR snapd#4415 opened: Set debian-sid-64 system as manual <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4415>17:20
kalikianaAlright, time to call it a day17:36
kalikianao/17:36
=== Guest9132 is now known as daniellimws
ikeyi broke delta service: https://hastebin.com/jixayuxoki.sql18:31
* ikey nukes deltas and uploads the old fashioned way18:31
kyrofaikey, yeah, how dare you remove the 1 required positional argument18:35
ikeyikr? lol18:36
sergiusensikey interesting19:00
sergiusensthomi whose in charge of deltas these days https://hastebin.com/jixayuxoki.sql (on one side I want to understand the error on the other update snapcraft to handle the error message better)19:01
thomisergiusens: blr is the person you want for upload deltas, but if it's an emergency I can probably do some digging for you19:04
thomidid this happen recently?19:04
sergiusensthomi not an emergency, happened today; I think, ikey can confirm20:13
ikeyyeah no emergency20:14
ikeyjust nuked the deltas and went full upload20:14
thomihmm, this is the second report of upload deltas breaking in the last week.20:17
thomiI know blr looked in to the last report, but I don't know what he found (he's on holiday ATM, so I can't ask him)20:18
mupPR snapcraft#1786 closed: lxd: always install squashfuse <bug> <Created by kalikiana> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1786>21:11
mupPR snapd#4415 closed: Set debian-sid-64 system as manual <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4415>22:00
sergiusenssnappy-m-o autopkgtest 1815 xenial:armhf22:26
snappy-m-osergiusens: I've just triggered your test.22:26

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