touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #40128
[Bug 1396951] Re: webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied
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_: ah, it should be a symlink
<pitti> err, oSoMoN
<pitti> well, it really shouldn't be, but with Debian's layout it should
<oSoMoN> pitti, do you know what is responsible for creating it in the first place, when creating a chroot?
<pitti> oSoMoN: it depends on how you build it, but I figure somewhere between initscript's postinst and debootstrap; mk-sbuild and friends might also make some adjustments there, and sbuild has its own fstabs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1396951
Title:
webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is
denied
Status in Automated UI testing on Hardware:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
The CI job that runs autopilot tests for webbrowser-app on otto (desktop) has been consistently failing since the switch to vivid.
The error seen in the log is the following:
/var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.org.chromium.Chromium.UAVbQt failed: Permission denied
/var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(234)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied
/var/local/autopilot/autopilot.log: [1127/102329:FATAL:shared_memory_posix.cc(236)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.
At a first glance it looks to me like the problem is in the otto setup
itself.
To manage notifications about this bug go to:
https://bugs.launchpad.net/otto/+bug/1396951/+subscriptions
References