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

=== JanC_ is now known as JanC
nacchrm, i've been seeing some ProxyError's from the lp snap builders (worker earlier today and stopped for the last three): https://launchpadlibrarian.net/328378888/buildlog_snap_ubuntu_xenial_i386_git-ubuntu_BUILDING.txt.gz03:37
nacccjwatson: --^03:37
naccit seems to be a perm error when trying to get the core snap?03:37
mupPR snapd#3581 opened: Add polkit authorization support to /v2/login <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/3581>03:54
=== chihchun_afk is now known as chihchun
elopio!tryme06:13
baymax-elopioIt works !06:13
mupPR snapd#3579 closed: snap-seccomp: link libseccomp statically to snap-seccomp <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3579>06:25
elopio!tryme06:35
baymax-elopioIt works !06:35
zygagood morning08:02
pstolowskimorning!08:06
mupPR snapd#3582 opened: Merge release 2.26.9 back into master <Created by mvo5> <https://github.com/snapcore/snapd/pull/3582>08:56
* zyga hugs mvo08:57
mupPR snapd#3583 opened: tests: fix econnreset test in 2.26 (store urls changed) <Created by mvo5> <https://github.com/snapcore/snapd/pull/3583>08:57
* mvo hugs zyga08:58
mwhudsoner all my classic snap builds failed09:06
mwhudsondownloading the core snap failed with09:06
mwhudsonHTTPSConnectionPool(host='api.snapcraft.io', port=443): Max retries exceeded with url: /api/v1/snaps/download/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_2314.snap (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',)))09:06
* zyga fixes a typo in fedora build09:13
zyga(space exploding typo)09:14
zygaPharaoh_Atem: can you please allow me to push to https://github.com/snapcore/snapd/pull/357709:26
mupPR snapd#3577: packaging/fedora, tests: Fix build for snapd and enable a test for Fedora <Created by Conan-Kudo> <https://github.com/snapcore/snapd/pull/3577>09:26
* zyga -> quick breakfast09:27
zygamvo: I have a fixed fedora branch, if Pharaoh_Atem doesn't respond soon (it's early for US so I don't expect him to) we can just push that to a separate branch and close his PR09:27
zygamvo: together with your fix for econreset it should fix master09:27
mvozyga: sounds good09:27
zyga/home/gopath/src/github.com/snapcore/snapd/tests/lib/boot.sh: line 14: fw_printenv: command not found09:29
zygahmm09:29
cjwatsonnacc: Yes, see RT#10423009:30
cjwatsonmwhudson: ^- you too09:30
zygamvo: since I "care" more about it now, I will improve proxy support for qemu testing09:33
cjwatsonnacc,mwhudson,stokachu: classic snap builds should be fixed now; try again09:46
mupPR snapd#3577 closed: packaging/fedora, tests: Fix build for snapd and enable a test for Fedora <Created by Conan-Kudo> <Closed by zyga> <https://github.com/snapcore/snapd/pull/3577>09:48
mupPR snapd#3584 opened: packaging: fix Fedora support <Created by zyga> <https://github.com/snapcore/snapd/pull/3584>09:48
Son_Gokuzyga, you could have just asked for me to turn your ability to push on09:55
zygaSon_Goku: I did :)09:55
zygaSon_Goku: (earlier above)09:55
Son_Gokuyou asked the wrong me :)09:55
Son_Gokubut anyway, it's on09:55
zygaSon_Goku: I poked Pharaoh_Atem though, sorry about not realizing both of your accounts were on09:55
zygathanks!09:56
zygadid you turn it off before?09:56
zygaI wonder why it wasn't on in the first place09:56
Son_Gokuzyga: I turn it off by default because sometimes people rewrite commits without telling me09:56
zygaSon_Goku: aha, good09:56
zygaSon_Goku: I was just curious if some github default changed09:56
Son_Gokuand I really hate it when I'm attributed to things I didn't do :)09:56
zygaSon_Goku: I will have one more fedora improvement for testing in a moment09:56
Son_Gokuokay09:56
Son_Gokuwell, you can reopen my PR and push there09:57
zygathis one is already in progress (testing) so it would not be any diferent09:57
zygaall of your commits are there alreday :)09:57
zyga(unchanged)09:57
* Son_Goku shrugs09:58
Son_Gokuokay then09:58
mupPR snapd#3582 closed: Merge release 2.26.9 back into master <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3582>10:12
mupPR snapcraft#1403 opened: lxd: Only remove container if one exists <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1403>10:16
zygacurious10:26
zygamvo: so...10:27
zygamvo: I bet that fedora doesn't provide libseccomp.a10:27
zygamvo: ... :-(10:27
* zyga wants to start entertaining alcoholic addition10:27
mvozyga: right, we can link it dynamically there10:28
mvozyga: we really only need the static build on the core snap10:28
Son_Gokumvo: which is why I asked about it yesterday :)10:29
Son_Gokutechnically... libseccomp.a *does* exist, though10:29
zygaSon_Goku: it does? (my fedora box is not unpacked yet)10:30
zygaSon_Goku: which package is it in?10:30
Son_Gokuall static link libraries are separated out into -static subpackages10:30
zygaah10:30
zygaperfect10:30
zygaI'll make it happen then10:30
Son_Gokuugh10:30
zygaSon_Goku: for today that's the best way10:30
* Son_Goku groans10:30
Son_Gokufine10:30
zygaSon_Goku: we can expore build tags and dynamic linking but mvo needs to get this out10:30
Son_Gokuwait, are we going to have 2.27 today or something?10:31
zygaSon_Goku: I personally would love to drop libseccomp and just genrate bpf from go (because I'm a compiler addict)10:31
zygaSon_Goku: that's a question for mvo10:31
Son_Gokuplease don't make me cry10:31
Son_Gokugolang makes me sad10:31
Son_Gokuthe ecosystem is nuts10:31
ogra_great, aint it ? so you only need blots for functional apps ;)10:31
ogra_*bolts10:32
Son_GokuI've even heard from ex-Googlers that most Googlers hate golang10:32
zygaSon_Goku: why?10:32
Son_Gokuthe development experience is really bad10:33
zygaSon_Goku: (I really really like writing precise bpf programs from snapd directly)10:33
Son_Gokuand maintaining golang packages is obnoxious10:33
zygaSon_Goku: anyway, not arguing about golang being nice or not10:33
Son_Gokulike, as in with the way vendoring works and whatnot10:33
Son_Gokuat least one person told me there are more people who like D than there are who like golang10:33
Son_Gokuit's pretty much the domain of the borg group10:34
Son_Goku(which makes kubernetes)10:34
sil2100Hello! I have a question related to the snapcraft.yaml 'install:' bit that can be defined for a given part10:34
sil2100I can't find any documentation10:34
sil2100When is that run? At which step?10:35
* zyga doesn't get the vendoring argument (vendoring is a fact, how does golang make it different from python, ruby, C and others?)10:35
Son_Gokuthe problem is that golang vendoring works based exclusively off of git commits10:35
Son_Gokuwhich makes things way more brittle than you think10:35
Son_Gokuzyga, also, not having a debugger unless you use gccgo sucks ass10:37
zygaSon_Goku: debugger yeah, but then again golang behaves differently from other languages, I rarely use debugger in python (and when I did it was because C exploded)10:37
Son_Gokubut python provides tracebacks and repl capabilities10:38
zygaSon_Goku: golang has tracebacks as well10:38
Son_Gokugolang compiler failures are inscrutable, too10:38
Son_Gokuas we found out a couple of weeks ago10:38
zygaSon_Goku: ??!10:38
zygawell10:38
zygathose were very much not golang but gccgo and on unsupported arch, right?10:38
Son_Gokuzyga: we weren't using gccgo10:39
zygaSon_Goku: all I'm saying is that daily hacking on golang code is anything but bad10:39
* Son_Goku shrugs10:39
zygaSon_Goku: on ppc64 we were, I tink10:39
Son_GokuI've had to figure out failures on armv7hl before10:40
zygahl?10:40
zygaofftopic10:41
Son_Gokuarmv7l with hfp (hard-float)10:41
zygaah10:41
Son_Gokudebian calls it armhf10:41
zygahf in debian land10:41
zygaright10:41
Son_Gokubut the internal architecture name is armv7hl10:41
zygaofftopic: I found my warcraft 2 CD10:41
Son_Gokuooh nice10:41
zygaand it's slightly scratched :-(10:41
Son_GokuNooo :(10:41
zygaI'm playing the soundtrack10:41
zygabut some tracks (my fav) are not working10:41
Son_Gokuah, the days where games abused CDAudio for music :)10:42
zygayeah10:43
zygatack 2 and track 3 are very nice10:43
* zyga looks at fedora VM prep10:43
mvozyga, Son_Goku: you could simply sed aways the #cgo LDFLAGS: -Wl,-Bstatic via the spec file if you want to get rid of the static linking10:45
mvothat seems like the simplest option for now10:45
mupPR snapd#3585 opened: many: configure store from state, reconfigure store at runtime <Created by atomatt> <https://github.com/snapcore/snapd/pull/3585>10:46
Son_Gokuwelp, that's up to zyga now, I can't do anything anymore10:46
Son_Gokuhe closed my PR :)10:46
Son_Gokumvo: but at least, my spec compiled as of yesterday10:47
mvozyga, Son_Goku: re 2.27 - I want to discuss this today, my idea is to have a 2.27~rc1 today and see if it behaves well everywhere (it got more churn than usual). and if that looks ok a real 2.27 EOW maybe10:47
Son_Gokuokay10:47
mvoSon_Goku: \o/ for the spec work10:47
mvoSon_Goku: or maybe early next week, but definitely soon as its overdue10:47
zygamvo: sounds like a plan10:47
Son_Gokuyeah, it's a couple months overdue :P10:48
Son_GokuI was hoping for 2.27 to be in Fedora 2610:48
mvo*cough*10:51
davidcallesil2100: check out https://snapcraft.io/docs/build-snaps/scriptlets10:52
sil2100davidcalle: oh! Thanks! I see it there10:52
zygaugh10:54
zygawhy does my fedora VM use de keymap?10:54
zygawhy doesn't localectl change it :/10:54
Son_Gokubecause you're nuts and you have too much stuff10:54
zyga*V-M*10:54
Son_Gokuyou need to use set-keymap10:54
Son_Gokuwith localctl10:54
zygaI did10:55
zygabut I was foolish10:55
zygato assume "en" is sane10:55
zygaI wanted "us"10:55
zygaen is just the same as "de", just worse10:55
Son_Goku:/10:55
zygakeys are all over10:55
zygaus works, I can do what I wanted10:55
zygaeh, my wired network caps at 0.5MB/s10:56
zygabecause yeah, that's why10:56
Son_Gokumvo: well, I'll just ship it as an update10:57
Son_Gokuit's no biggie10:57
Son_Gokuit's not like it's a pain to ship updates :P10:57
zygayeah, that's true :-)10:57
zygalater today I'll try to put my fedora box up so I can have real hardware to work on10:58
zygaSon_Goku: so, where is libseccomp-devel-static?11:20
Son_Gokuit's just libseccomp-static11:20
zyga(took my a while but now I have a shell)11:20
zygaah11:20
zygathanks!11:21
Son_Goku"dnf repoquery *-static" will give you a list of them all11:21
zygaok, pushed to 358411:40
zygatests fine locally11:40
Son_Goku:/11:43
zygawhat's wrong?11:43
Son_Gokudo you know how to use "git rebase" with arbitrary remotes?11:45
zygaSon_Goku: yes11:45
zygaSon_Goku: first add the remote11:45
zygaSon_Goku: then fetch11:45
zygaSon_Goku: then just reabse against remote/branch11:45
Son_Gokuyep11:45
Son_GokuI'm a bit weirded out by the merge commit in PR#3584 then11:46
zygaSon_Goku: I didn't rebase, I merged master11:46
zygaSon_Goku: note that snap-seccomp is a part of snapd, not snap-confine11:46
Son_GokuI'm aware11:47
zygaSon_Goku: and the distinction is more less arbitrary now11:47
Son_Gokuyes, it's for my own sanity11:47
Son_Gokumeh, I don't care11:47
Son_GokuI'll resync everything later from Dist-Git11:47
zyganot sure I understand11:47
zygaok11:47
zygaI can move it around11:47
zygaI want to land this to unbreak fedora and then we can polish the layout11:47
Son_Gokuyeah, go ahead11:47
zygaso what is the layout you want?11:48
Son_GokuI prefer keeping security stuff together, and the C stuff typically lives in snap-confine11:48
Son_Gokubecause snapd is already insane enough as it is, I try to keep things separate in such a way I know which parts to touch every time something breaks11:49
fgimenezmvo: a test just failed on db http://paste.ubuntu.com/25074862/, other than that things are looking very good12:05
zyga oh12:13
zygahow did that happen?12:13
mvofgimenez: what is the output of /usr/lib/snapd/snap-seccomp there? and that is the revision of the core?12:15
fgimenezmvo: this was executed on testflinger, i don't have access to the testbed, the scenario is the basic beta image, core should be from beta without refreshes12:16
mvofgimenez: found it12:16
mvofgimenez: please re-run12:16
fgimenezmvo: sure on it12:17
zygageez, tests are sure slow today12:17
mvofgimenez: there was an error on snapcraft release for the arm64 revision, now its good12:17
fgimenezmvo: great thanks!12:17
zyga-susere12:21
mupPR snapd#3583 closed: tests: fix econnreset test in 2.26 (store urls changed) <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3583>12:22
zyga-susethanks!12:26
zyga-susea small observation, I patched spread to spawn 4 core VMs and this cut a good 3 minutes out of 15 minute run of fedora tests/main/help12:35
zyga-suses/15/18/12:35
zyga-suseso down from 18 minutes before to 15 minutes after12:35
=== mpontillo_ is now known as mpontillo
=== icey_ is now known as icey
=== nottrobin_ is now known as nottrobin
=== mariogrip_ is now known as mariogrip
=== tai271828__ is now known as tai271828_
=== mjl_ is now known as mjl
=== mup_ is now known as mup
=== cwayne_ is now known as cwayne
zyga-susemvo: bummer12:41
zyga-susemvo: time exceeded12:41
zyga-suseanother hour wasted12:42
zyga-suseon 358412:42
zyga-susemvo: please advise, do you want to merge it anyway or re-run12:43
mvozyga-suse: can we increase the workers or something? I would really like to not override this12:44
stokachucjwatson: thanks building now12:45
zyga-susemvo: let me check12:45
zyga-susepushed update with more workers12:45
mvota12:46
zyga-susethough what has failed seems to be ubuntu-16.04-6412:46
zyga-suseI think that one could use x10 workers (up from 4)12:46
zyga-suseI can try and see what we get12:46
zyga-suse(say up to 6)12:46
zyga-suse24 VMs for each git push12:47
zyga-susethat's $$$12:47
cachiozyga-suse, did you get a timeout for fedora?12:51
zyga-suseno12:52
zyga-susetravis 49 minute timeout12:52
cachiook, because it is not needed to increase the number of workers for suse and fedora if they they running one test12:53
cachiozyga-suse, do you have a link to see the timeout ?12:54
zyga-suseyes but I cannot paste it ... one sec12:55
zyga-susehttps://travis-ci.org/snapcore/snapd/builds/252773594?utm_source=github_status&utm_medium=notification12:55
=== didrocks1 is now known as didrocks
cachiozyga-suse, there was a problem with linode that caused the several machines were discarded12:59
cachiozyga-suse, that caused the delay on the execution13:00
cachiozyga-suse, I'll monitor that to see if it happen again13:00
zyga-susemvo: it passed!13:21
zygamvo: can you please review 358413:22
zygacachio, fgimenez: can you please review it from the POV of incresed worker count13:22
Son_Gokuzyga-suse: you dropped the increased capacity for fedora/opensuse :(13:23
zyga-suseSon_Goku: because cachio will increase it in his branch that unlocks +100 tests13:24
Son_Gokuah13:24
zyga-suseSon_Goku: he's already done this for Fedora, going through suse13:24
zyga-suseSon_Goku: this branch doesn't need the extra workers here (yet)13:24
zyga-susefgimenez, cachio, mvo: shall I decrement the workers back to 4?13:29
cachiocachio, I think so13:30
cachiozyga-suse,13:30
cachiozyga-suse, I'll try to see what is happening with those machines that are discarded13:31
cachiozyga-suse, but it seem to be a problem in linode13:32
fgimenezzyga-suse: sure on it13:33
* Son_Goku sighs13:33
Son_Gokuit works now, can't we just merge it?13:34
Chipacazyga-suse: I'm wondering where 'suse' fits in https://en.wikipedia.org/wiki/Japanese_honorifics13:36
zyga-suseoh :) ?13:37
zyga-suseheh :)13:37
zyga-suseChipaca, niemeyer: after you discuss the services API I'd like to know if the evolution of that idea has any impact on the interfaces api13:37
zyga-suseSon_Goku: I'd like to13:40
Son_Gokuthen hit the green button13:40
zyga-susemvo: can you make a call?13:40
* Son_Goku hypnotizes mvo to say 'yes'13:41
zyga-suseSon_Goku: I need more reviews13:41
zyga-suseSon_Goku: offtopic, in my language we often use "no" to indicate "yes" and "nie" to indicate "no"13:41
zyga-suseSon_Goku: we also have "tak" which is just "yes" but "no" is used very often13:41
* zyga-suse fetches tea13:48
cachiozyga-suse, just move the workers to 4 and push, you will have a green in 40 minutes13:49
cachiozyga-suse, otherwise we will be wasting resources for all the pushes13:51
zyga-susedone13:52
zyga-suselet's see13:52
mvozyga-suse: lets wait for another run, 2.27 is still in ~rc so things are not super urgent just yet13:55
zyga-susemvo: yep, sounds good13:57
zyga-suseif you can review the change it would accelerate the time to landing (once green)13:57
Chipacazyga-san, I don't think it impacts the interfaces api, at least in the short term14:09
Chipacazyga-san, there'll still be a /v2/apps/ endpoint with nice juicy appy stuff14:10
Chipacazyga-san, and a /v2/logs/ for all your woodworking needs14:10
zygaChipaca: aha, I see, thank you14:11
zygaChipaca: I see you are feeling honorific today :)14:12
Chipacazyga, you started :-p14:12
zygame?14:12
Chipaca“zyga-suse” :-)14:13
zygaChipaca: LOL :D14:13
* Pharaoh_Atem sighs14:17
Pharaoh_Atemback to the grind14:17
ogra_fgimenez, the dragonboard-kernel in edge is quite a bit behind the other channels, any objections to bumping it to the same version the others have ?14:21
fgimenezogra_: any at all , in fact we currently start using it at beta, hopefully will be watching edge changes for db soon, thanks!14:24
ogra_great, thanks !14:24
zygamvo: fedora fix merged14:26
mupPR snapd#3584 closed: packaging: fix Fedora support <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3584>14:27
Saviqcjwatson, hey, does LP reuse/cache instances it builds snaps on? alan_g's seeing weird behaviour after fixing snapcraft.yaml - it failed on 50% of arches... https://launchpad.net/~alan-griffiths/+snap/mircade-snap14:34
cjwatsonSaviq: there's no reuse, no14:38
Saviqwhy would we ever see "Skipping pull... (already ran)" then¿?14:39
cjwatsonSaviq: because LP runs snapcraft more than once14:39
sergiusensSaviq: because launchpad builders run each command14:40
Saviqah separately, ok14:40
sergiusensthey first run `snapcraft pull` and then the others14:40
sergiusensthis is from the time of only having network during pull14:40
cjwatsonyeah, it's slightly historical now, but meh14:40
Saviqthen there's a race of some kind...14:40
cjwatsonyeah, you're doing a parallel build so my money is on a bug in that build system14:41
cjwatsontry it in cleanbuild a few times maybe14:41
Saviqwell, "that build system" being snapcraft, as far I can tell...14:41
Saviqsince it tries to operate on a part directory it's not created yet14:42
sergiusensSaviq: install should be created. What is not is the leaf directory of `usr`14:44
Chipacazyga: are you (or is somebody) working on getting spread running on opensuse again?14:45
sergiusensSaviq: may I be so bold so ask you to look in your cmake given the `-j4` (you can disable parallel builds in the yaml)14:45
Saviqsergiusens, it fails on the games part, which uses the nil plugin14:46
Saviqand is just a dump stage-packages dump14:46
Saviqdumb, even14:46
sergiusensSaviq: oh, I am looking at https://launchpadlibrarian.net/328470482/buildlog_snap_ubuntu_xenial_i386_mircade-snap_BUILDING.txt.gz14:46
sergiusenswhat should I be looking at?14:46
Saviqsergiusens, yeah, that's it, [Errno 2] No such file or directory: '/build/mircade-snap/parts/games/install/usr'14:46
cachiozyga, we are doing "dnf -y -q upgrade" when we prepare the project on fedora and it could be skipped14:48
cachiozyga, is it right?14:48
cachiono need to refresh metadata if using dnf14:48
zyga-susecachio: not sure if, I think it might have been there for a reason14:48
Saviqsergiusens, oh and btw, cleanbuild --debug does not give me a shell after this failure :/14:48
zyga-susecachio: we do a similar "apt-get update"14:48
sergiusensSaviq: unfortunate :-/14:49
sergiusensSaviq: that failure however is from running the miral part (`games`)14:49
=== chihchun is now known as chihchun_afk
Saviqsergiusens, why would the miral part try and look in the "games" part's folder¿?14:50
cachiozyga-suse, the problem is that the dnf upgrade is not the than apt update14:50
cachioit is upgrading the system14:50
zyga-susePharaoh_Atem: ^ should we skip that?14:51
zyga-susecachio: let's try, once it starts failing we can make spread-cron do the updates14:51
fgimenezmvo: just got this error in the from-archive scenario on xenial http://paste.ubuntu.com/25075603/, in this case snapd is not built from branch, the deb package is installed from proposed and core is installed from beta (and not modified)14:53
fgimenezthe same scenario passed ok on trusty14:54
alan_gSaviq: retrying armhf worked, i386 didn't (retrying that now). So "racy build" seems plausible.14:55
Saviqsergiusens, ↑14:55
sergiusensSaviq: still, this is not the `games` part running, it is from the miral part14:56
Saviqsergiusens, even so, that would mean snapcraft's telling cmake the wrong install prefix/chroot/something?14:57
sergiusensI see no "Building games" message in those logs14:57
Saviqsergiusens, sure, just means the parts' env is leaking between parts?14:58
sergiusensSaviq: yes. Maybe. That could be it. This is there since the days of mvo and mterry caring for the code base. But I can check15:00
Saviqsergiusens, it reproduces here in cleanbuild on zesty15:00
sergiusensSaviq: on and off?15:01
sergiusensor always?15:01
Saviqsergiusens, I'd say more than 50%15:01
Pharaoh_Atemzyga-suse: dnf makecache is equivalent to apt update15:03
zyga-susePharaoh_Atem: intereting, thanks (I never ran that command myself)15:05
Pharaoh_Atemon a normal system, you don't need to15:06
Pharaoh_Atemthere's a systemd timer that takes care of it for you15:06
nacccjwatson: thanks! yes, my snap built fine overnight, it appears15:06
zyga-susejdstrand: hey, replied to the "using snap-update-ns from snap-confine" thread15:07
Pharaoh_Atemzyga-suse: if you need to force a metadata update independent of the actual action, that's how you do it15:07
Pharaoh_Atemnormally, you only care in the context of a system upgrade, so "--refresh" can be used as an option to force it15:08
zyga-susePharaoh_Atem: the goal is to accelerate test cycles, if we can not run "dnf update" that's all good15:08
Pharaoh_Atemdon't you run system upgrades before every test?15:08
Pharaoh_Atemfor ubuntu15:08
zyga-susePharaoh_Atem: I worry though that we'll hit stale cache issues sooner or later unless we do base image updates separately like every 12 hours15:08
zyga-susePharaoh_Atem: we don't15:08
Pharaoh_Atemwell, if the metadata is expired, dnf will fetch anyway15:09
Pharaoh_Atemyou don't need makecache normally15:09
zyga-susePharaoh_Atem: it was way to slow and it'd be better to just have fresh images updated out-of-band15:09
Pharaoh_Atemthen take it out entirely from suse and fedora spread runs15:09
Pharaoh_Atemboth of them do metadata refresh and system upgrade15:10
Pharaoh_Atemwell, zypper requires metadata refresh manually15:10
zyga-suseyep15:10
ahasenackhi, shouldn't I need root to install a (classic even) snap? http://pastebin.ubuntu.com/25075675/15:11
zyga-suseahasenack: no if you "sudo snap login"ed before15:11
ahasenackI see15:12
ahasenacknacc: ^15:12
naccahasenack: thanks15:12
ahasenackzyga-suse: the result of that login is what is stored in ~/.snap/auth.json?15:13
zyga-suseyes15:13
mvofgimenez: the error is "expected", we could SRU 2.26.9 - then it will go away. maybe thats cleaner15:13
ahasenackhm15:13
ahasenackthx15:13
zyga-suseuh, oh15:15
zyga-susethunderstorm15:15
fgimenezmvo: np, thank you, btw all the ongoing dragonboard test executions on testflinger have suddenly stopped with "Timeout while trying to communicate with the server.", i'll try to retrigger them but this is going to make the validation longer, pi2 and pi3 finished successfully15:16
* zyga-suse shuts the desktop down :/15:16
zyga-susebut hey, laptops15:16
Saviqsergiusens, alan_g, bug #170387815:17
mupBug #1703878: Race/environment leak between parts <Snapcraft:New> <https://launchpad.net/bugs/1703878>15:17
mvofgimenez: thanks - strange, any idea what happend there?15:18
fgimenezmvo: nope, maybe plars can help15:19
zyga-susedo you have a log?15:19
mvofgimenez: all 2.26.9 debs uploaded to -proposed, things should be in sync now test-wise (once they get accepted)15:20
fgimenezmvo: great thanks!15:21
mupPR snapd#3544 closed: tests: make main/help run on opensuse and fedora again <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/3544>15:34
sergiusensSaviq: `snapcraft cleanbuild --debug` or `snapcraft --debug cleanbuild`?15:43
sergiusensSaviq: http://paste.ubuntu.com/25075840/ (I am fixing it so it works when specified the other way around)15:52
zygacachio, fgimenez: I just found a weird bug where one spread test failed because core had a random refresh15:56
zygaare we rescheduling refreshes in the prepare stage?15:57
zygamore, I think (not sure if possible) is that it was *snapshotted* this way16:00
zygaso each subsequent test fails on the same "core has changes in progress"16:00
fgimenezzyga-suse: looks like bad timing, maybe your test was run at the same time the last edge core was published16:25
fgimenezin other words, perhaps the new core was made available during the run, we have had this issue before16:26
plarsfgimenez: I'm out this week, but if it's one of ours, I can tell you that I just got results in email of one of our runs that was successful. If you have a log or something, please send it so I can see what was going on when I get back. Otherwise maybe retry it?16:26
fgimenezzyga-suse: last core was available about 2h ago https://travis-ci.org/snapcore/spread-cron/builds/25282572116:27
fgimenezplars: thanks! it just printed "Timout while trying to communicate with the server." (sic) during the execution, now i'm not able to retrigger, i get a job id but the polling gets stuck16:28
fgimenezplars: i had good executions until ~1:30min ago, i'll sned you the details by mail, thx!16:30
mupPR snapd#3498 closed: hooks: support for install and remove hooks <Created by stolowski> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3498>18:51
mupPR snapcraft#1404 opened: cleanbuild: ensure we enter a shell on failures on --debug <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1404>19:22
=== JanC is now known as Guest95169
=== JanC_ is now known as JanC
=== JanC_ is now known as JanC

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