Running Angular e2e tests using GitHub Actions throws "DevToolsActivePort file doesn't exist" error

Question

I'm experimenting with GitHub actions and trying to run Angular e2e tests in this CI workflow.

I'm using the default project created by the Angular CLI, and only made modifications around the Protractor configuration. On the GitHub side I'm using the default workflow for Node.js and Azure, but for troubleshooting I removed all Azure related steps, so it's just trying to run the e2e tests.

My sample code is available here: https://github.com/DanielSzentimrey-Harrach/ng-e2e-ci-dummy

When I run the CI job I get the following error:

"unknows error: DevToolsActivePort file doesn't exist"

After googling this error I understand it's a problem with how e2e tests are running in a container, but I didn't find any way to resolve this within GitHub Actions. Most posts talk about adding various parameters to the Protractor configuration. I've tried the below ones, and their various permutations, but still no luck:

--no-sandbox
--disable-dev-shm-usage
--disable-gpu
--remote-debugging-port=9222
--remote-debugging-address=0.0.0.0

ya_dimon · Accepted Answer · 2020-07-27 23:09:50Z

0

from docs should be not --protractor-config= ... but --protractorConfig
or better set the config in angular.json by e2e configuration, as e.g. 'ci'.
Then run npm run e2e -- -c=ci
example project

answered Jul 27, 2020 at 23:09

ya_dimon

3,9125 gold badges35 silver badges44 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Running Angular e2e tests using GitHub Actions throws "DevToolsActivePort file doesn't exist" error

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related