Open ash0080 opened 6 years ago
@ash0080 thank you for the feedback. Seems to be permissions issue. Either because selenium
user is not in some pulseaudio
group or because pulse
user has no permissions in /home/selenium
directory.
@vania-pooh Is this '/home/selenium/.config/pulse' a path in container? Any way to quick fix it?
@ash0080 will try to build Firefox 59 image with potential fix.
@ash0080 unfortunately can't reproduce this issue. Could you provide an example scenario how to reproduce it?
ubuntu 16.04 64bit / 1 core vps
./cm selenoid configure --browsers firefox --last-versions 1 --tmpfs 128 \
&& ./cm selenoid start --port 4445 --args "-limit 2 -service-startup-timeout 60s -session-attempt-timeout 60s -session-delete-timeout 30s -timeout 120s"
const webdriverio = require('webdriverio')
const options = {
host: '',
port: 4445,
connectionRetryCount: Number.MAX_VALUE,
sync: false,
debug: true,
desiredCapabilities: {
browserName: 'firefox',
// 'moz:firefoxOptions': {
// 'args': ['-headless']
// },
maxInstances: 2,
version: '58.0',
unexpectedAlertBehaviour: 'accept'
}
}
module.exports = webdriverio.remote(options)
then wrap 2 requests in a Promise.all()
@ash0080 ok, two parallel requests to the same session. Let me try this.
@vania-pooh actually no matter parallel or sequence call will both products this error
Could be related to https://github.com/aerokube/selenoid/issues/956.
run multiple browser instances will logs this error, only the first docker container will not logs error,
for example
one firefox with error, one not this permission error will trigger timeout error quite possibly.