Code review comment for ~jocave/plainbox-provider-snappy:add-plans-for-nesting

The merge was fine but running tests failed.

[xenial] [16:41:03] Unable to update pristine container!
[bionic] [16:41:04] starting container
Device project added to bionic-testing
[xenial] output: https://paste.ubuntu.com/p/WwVMHQHBd6/
[xenial] NOTE: unable to execute tests, marked as failed
[xenial] Trying to destroy to reclaim possible resources
[xenial] [16:41:06] Starting tests...
[xenial] Found a test script: ./requirements/container-tests-provider-snappy
[xenial] [16:41:07] container-tests-provider-snappy: FAIL
[trusty] [16:41:08] starting container
[xenial] output: https://paste.ubuntu.com/p/cgq4fywHRS/
[xenial] [16:41:09] Fixing file permissions in source directory
[xenial] [16:41:09] Unable to fix permissions!
Device project added to trusty-testing
[xenial] output: https://paste.ubuntu.com/p/vGh4cG4w9D/
[xenial] Some files owned by root may have been left around, fix them manually with chown.
[xenial] [16:41:12] Destroying container
[xenial] [16:41:12] Unable to stop container!
[xenial] output: https://paste.ubuntu.com/p/jdMYgY5XFn/
[xenial] You may need to manually 'lxc stop -f xenial-testing' to fix this
[bionic] [16:41:20] provisioning container
[bionic] [16:41:20] Unable to provision requirements in container!
[bionic] output: https://paste.ubuntu.com/p/nxBXXd7sj9/
[bionic] [16:41:22] Fixing file permissions in source directory
[bionic] [16:41:22] Unable to fix permissions!
[trusty] [16:41:23] provisioning container
[trusty] [16:41:23] Unable to provision requirements in container!
[bionic] output: https://paste.ubuntu.com/p/QRrkmx47PN/
[bionic] Some files owned by root may have been left around, fix them manually with chown.
[bionic] Destroying failed container to reclaim resources
[trusty] output: https://paste.ubuntu.com/p/jx5Qk7CgX2/
[trusty] [16:41:25] Fixing file permissions in source directory
[trusty] [16:41:25] Unable to fix permissions!
[trusty] output: https://paste.ubuntu.com/p/Bh4jqYN4Mq/
[trusty] Some files owned by root may have been left around, fix them manually with chown.
[trusty] Destroying failed container to reclaim resources