> or a failure to reach the cloud image server.
The tests work on wily and vivid, so in principle they can talk to the
cloud image server or linuxcontainers.org. It might of course be that
later LXC versions got some proxy fixes or something such. However, the
tests in trusty also worked until
Running lxc test against trusty-release in the CI production environment
still works fine (against kernel -65). I do get the hang with running
against -proposed, under otherwise the exact same circumstances.
The dist-upgrade to -proposed does the following:
The following NEW packages will be
Running lxc test against trusty-release in the CI production environment
still works fine (against kernel -65). I do get the hang with running
against -proposed, under otherwise the exact same circumstances.
The dist-upgrade to -proposed does the following:
The following NEW packages will be
> or a failure to reach the cloud image server.
The tests work on wily and vivid, so in principle they can talk to the
cloud image server or linuxcontainers.org. It might of course be that
later LXC versions got some proxy fixes or something such. However, the
tests in trusty also worked until
Keeping notes: I did a local QEMU run against trusty release and trusty-
proposed:
adt-run lxc -s --- qemu /srv/vm/adt-trusty-amd64-cloud.img
adt-run --apt-pocket=proposed -U lxc -s --- qemu
/srv/vm/adt-trusty-amd64-cloud.img
They both fail for the same reason: five tests fail due to
Keeping notes: I did a local QEMU run against trusty release and trusty-
proposed:
adt-run lxc -s --- qemu /srv/vm/adt-trusty-amd64-cloud.img
adt-run --apt-pocket=proposed -U lxc -s --- qemu
/srv/vm/adt-trusty-amd64-cloud.img
They both fail for the same reason: five tests fail due to
They all get stuck in lxc-test-ubuntu which would indicate either a hang
in debootstrap (newly introduced debconf question) or a failure to reach
the cloud image server.
In either case, you've not actually regressed LXC, the other tests would
have failed if that was the case.
So I'd toss this
They all get stuck in lxc-test-ubuntu which would indicate either a hang
in debootstrap (newly introduced debconf question) or a failure to reach
the cloud image server.
In either case, you've not actually regressed LXC, the other tests would
have failed if that was the case.
So I'd toss this
