When using protractor testing and headless mode in gitlab pipelines/CI this occurs:
- Failed: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=58.0.3029.110)
(Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.9.24-coreos x86_64)
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=58.0.3029.110)
(Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.9.24-coreos x86_64)
at Object.checkLegacyResponse (/builds/User/abc/node_modules/selenium-webdriver/lib/error.js:505:15)
at parseHttpResponse (/builds/User/abc/node_modules/selenium-webdriver/lib/http.js:509:13)
at doSend.then.response (/builds/User/abc/node_modules/selenium-webdriver/lib/http.js:440:13)
at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: Protractor.get(http://localhost:49152/user/login) - get url
at Driver.schedule (/builds/User/abc/node_modules/selenium-webdriver/lib/webdriver.js:816:17)
at ProtractorBrowser.executeScriptWithDescription (/builds/User/abc/node_modules/protractor/lib/browser.ts:584:24)
at driver.wait (/builds/User/abc/node_modules/protractor/lib/browser.ts:898:25)
at /builds/User/abc/node_modules/selenium-webdriver/lib/webdriver.js:947:14
at TaskQueue.execute_ (/builds/User/abc/node_modules/selenium-webdriver/lib/promise.js:2970:14)
at TaskQueue.executeNext_ (/builds/User/abc/node_modules/selenium-webdriver/lib/promise.js:2953:27)
at asyncRun (/builds/User/abc/node_modules/selenium-webdriver/lib/promise.js:2860:25)
at /builds/User/abc/node_modules/selenium-webdriver/lib/promise.js:676:7
at process._tickCallback (internal/process/next_tick.js:109:7)
Using headless chrome=58.0.3029.110 , Driver info: chromedriver=2.29.461571 , image: node:7.10.0, "protractor": "~5.1.1",
Protractor config:
capabilities: {
browserName: 'chrome',
chromeOptions: {
args: [ "--headless", "--disable-gpu","--window-size=800x600" ]
}
},
directConnect: true,
These tests work fine on non-docker/non-gitlab-ci/pc.
- Don’t want to use xvfb
- Have followed this: http://www.protractortest.org/#/browser-setup#setting-up-phantomjs
- Some have suggested shm_size issues
- Karma tests with headless chrome are fine
Is there any way to get access to the gitlab CI docker container system error?
Is there a way to debug this another way?
Is there a way to set shm_size in gitlab-ci.yml and not in https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md?
Anyone else got any ideas? Any help would be appreciated as this is very docker/gitlabCI specific.