we’re trying to work on a feature in LXD and as a first step have attempted to replicate a continuous test environment.
However, when it comes to unit tests, we had to run them in single-process mode: https://github.com/lxc/lxd/issues/4328 and integration tests are failing us in two different ways as well:
when running them by hand, remote_usage fails:
EROR[03-13|20:46:14] Failed to retrieve PID of executing child process: EOF
when running them in gitlab-ci, basic_usage fails:
Starting c1
action=start created=2018-03-13T20:33:45+0000 ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2018-03-13T20:33:45+0000 used=1970-01-01T00:00:00+0000
error: Failed to run: /root/go/bin/lxd forkstart c1 /root/go/src/github.com/lxc/lxd/test/tmp.8PP/hQd/containers /root/go/src/github.com/lxc/lxd/test/tmp.8PP/hQd/logs/c1/lxc.conf:
Try `lxc info --show-log lxd2:c1` for more info
==> Cleaning up
after fixing the GOPATH to /srv/go in .gitlab-ci, there’s still something struggling against it in the tests…
so we’re now passing it to make GOPATH=$GOPATH check as well…
if this fails, we should probably revert to simply doing chmod +x /root /root/go (in the morning)
You could run the testsuite with LXD_VERBOSE=1 set in the environment, it’d show you exactly what part of the apparmor test is failing.
Are you running the testsuite inside a container? If so, that’d explain the failure and also why you’re likely to run into a bunch more problems. The LXD testsuite is meant to run as root on a host, not inside a container.
you mean the TestHeartbeat failing unless ran with GOMAXPROCS=1
i can test that again for you and will report back (on the github issue, if it’s related to this!)