Now that bug #1399772 has been fixed, the vivid chroots used by CI jobs
need to be rebuilt to ensure that /dev/shm is created with the correct
permissions.
** Summary changed:
- webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied
+ webbrowser-app’s unit tests crash in CI
In a utopic chroot, /dev/shm is a symlink to /run/shm:
lrwxrwxrwx 1 root root 8 Apr 29 2014 /dev/shm - /run/shm
drwxrwxrwt 2 root root 40 Dec 5 11:51 /run/shm
Whereas in vivid it is a directory, with no write permissions for group and
other:
drwxr-xr-x 2 root root 4096 Nov 7 10:21
For reference:
pitti oSoMoN: that looks ok; is /dev/shm a symlink?
oSoMoN pitti, no, /dev/shm is not a symlink, it’s a plain directory
(drwxr-xr-x)
ogra_ aha
and not 1777
oSoMoN yup
but I have no idea why it doesn’t have the right permissions
oSoMoN (which is my original question)
pitti ogra_:
I dug some more on the /dev/shm not a symlink and filed:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1399772
Also setting otto to won't fix as it's being deprecated.
** Changed in: otto
Status: New = Won't Fix
--
You received this bug notification because you are a member
** Also affects: oxide-qt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396951
Title:
webbrowser-app’s autopilot tests fail on otto: access to
Additionally, i386 and and amd64 builds now also fail in CI, because of
the same error (interestingly they pass on armhf, I guess because they
are being run on real hardware as opposed to chroots for the other
architectures). See e.g. https://jenkins.qa.ubuntu.com/job/webbrowser-
Discussed with Olivier over IRC that the otto issue is a limitation of
the lxc containment in use and further support of otto is being
deprecated in favor of a future solution that will run desktop tests
natively on the hardware. Olivier also supports just disabling these
tests (which was guidance
It’s likely that LP virtual builders for x86 are on trusty (or an older
ubuntu release anyway), this /dev/shm issue started appearing in vivid,
which would explain why we’re not seeing it in PPA builds.
Of course when LP builders are upgraded to vivid(+n), builds will start
failing. If we can
Oxide, which is based on chromium, needs write-access to /dev/shm to
function properly. So we need to ensure /dev/shm is writeable in our
test environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interestingly, I’m seeing the same error when running webbrowser-app’s unit
tests inside a vivid chroot.
The permissions for /dev/shm there are drwxr-xr-x.
** Also affects: otto
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
10 matches
Mail list logo
