[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-27 Thread Adam Conrad
This is fixed in snapd 2.11. ** Changed in: snapd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599799 Title: snapd > 2.0.2 fails on yakkety To man

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-15 Thread Martin Pitt
At this point this needs to be looked at by a snapd developer anyway, see comment 12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599799 Title: snapd > 2.0.2 fails on yakkety To manage notificat

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-15 Thread Federico Gimenez
This is the test executed [1], with [2] the snapbuild binary should be generated. Not sure why it's not present after the test exits in your case, I can find it running locally (yakkety, autopkgtest 4.0.2, command line: "adt-run --unbuilt-tree . --apt-upgrade -s --- qemu ~/adt-yakkety- amd64-cloud.

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-14 Thread Martin Pitt
> there should be a copy of the snapbuild binary in the testbed in the paths /usr/bin/snapbuild and $AUTOPKGTEST_ARTIFACTS/build/bin/snapbuild after a test run. No, there isn't -- I already searched the entire VM for "*build*", and the only hit is the aforementioned snapbuild/ dir which only conta

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-14 Thread Federico Gimenez
Hi again, > integration-tests/bin/ does not exist, and tests/lib/snapbuild is a > directory with just "main.go" in it. This is true for both the > original source dir and the copy in > $AUTOPKGTEST_ARTIFACTS/build/src/github.com/snapcore/snapd > that the test creates. Sorry, I mistakenly sent the

Re: [Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-14 Thread Martin Pitt
Federico Gimenez [2016-07-14 13:03 -]: > * Where do you get this "basic.snap" from? > > It is built from the source files, from the root of the project > something like: > > integration-tests/bin/snapbuild integration-tests/data/snaps/basic . integration-tests/bin/ does not exist, and tests/

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-14 Thread Federico Gimenez
Hi Pitti, thanks a lot for looking into this. About your questions: * Where do you get this "basic.snap" from? It is built from the source files, from the root of the project something like: integration-tests/bin/snapbuild integration-tests/data/snaps/basic . That should generate a basic_1.0_al

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-14 Thread Martin Pitt
Correlating this with dmesg shows some kernel errors: Jul 14 13:07:23 autopkgtest /usr/lib/snapd/snapd[2079]: taskrunner.go:238: DEBUG: Running task 17 on Do: Mount snap "basic-service" Jul 14 13:07:23 autopkgtest systemd[1]: Mounting Mount unit for basic-service... Jul 14 13:07:23 autopkgtest ke

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-11 Thread Martin Pitt
FTR, the test regression of snapcraft confirms that this is not a bug in the tests, but an https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/s/snapcraft/20160711_021706@/log.gz . -- You received this bug notification bec

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-07 Thread Michael Hudson-Doyle
This bit of the output seems to be the core of it: Jul 08 09:51:08 autopkgtest systemd[1]: dev-loop2.device: Job dev-loop2.device/start timed out. Jul 08 09:51:08 autopkgtest systemd[1]: Timed out waiting for device /dev/loop2. Jul 08 09:51:08 autopkgtest systemd[1]: Dependency failed for Squashf

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-07 Thread Federico Gimenez
FWIW this is the output of journalctl -xe after the error http://paste.ubuntu.com/17367141/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599799 Title: snapd > 2.0.2 fails on yakkety To manage not

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-07 Thread Martin Pitt
> What does the /srv/vm argument do? that's just the directory where I keep my QEMU images in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599799 Title: snapd > 2.0.2 fails on yakkety To manage

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-07 Thread Zygmunt Krynicki
Somewhat a shot in the dark (testing ongoing): https://github.com/snapcore/snapd/pull/1504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599799 Title: snapd > 2.0.2 fails on yakkety To manage noti

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-07 Thread Zygmunt Krynicki
What does the /srv/vm argument do? Thanks for the analysis so far, it is very helpful. I will check what's going on with the env.conf file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599799 Title:

[Bug 1599799] Re: snapd > 2.0.2 fails on yakkety

2016-07-07 Thread Martin Pitt
I also confirm that snapd 2.0.2 as in yakkety-release still succeeds. So the regression happened in 2.0.3, and the above command needs to be adjusted to autopkgtest --apt-pocket=proposed -U -s snapd -- qemu /srv/vm /autopkgtest-yakkety-amd64.img ** Summary changed: - autopkgtests fail on yakke