-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DevContainer only] "Cannot start ChromeHeadless" when running tests #10066
Comments
maxime-dupuis
changed the title
[DevContainer only] "Cannot start ChromeHeadless" because "GPU process isn't usable"
[DevContainer only] "Cannot start ChromeHeadless" when running tests
Jun 7, 2023
laurb9
added a commit
to openx/Prebid.js
that referenced
this issue
Jun 23, 2023
1 task
patmmccann
pushed a commit
that referenced
this issue
Jun 23, 2023
github-project-automation
bot
moved this from Triage
to Done
in Prebid.js Tactical Issues table
Jun 23, 2023
github-ishara-chan-tung
pushed a commit
to ebuzzing/Prebid.js
that referenced
this issue
Jul 12, 2023
musikele
pushed a commit
to rubicon-project/Prebid.js
that referenced
this issue
Aug 28, 2023
santii7395
pushed a commit
to themaven-net/Prebid.js
that referenced
this issue
Aug 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of issue
Bug
Description
I'm unable to run the tests from a VSCode DevContainer. The full error logs are below, here's what stands out:
Steps to reproduce
Open the project in VSCode, inside a DevContainer.
gulp test --file "test/spec/modules/sharethroughBidAdapter_spec.js"
Test page
Expected results
It works when I run the test locally without using the DevContainer:
Actual results
Error logs when running the test command from a DevContainer
Show error logs
Platform details
MacOs Monterey 12.6.3 (Chip: Apple M1 Pro)
VSCode 1.78.2
Other information
Possibly related to the different flags we use to run Headless Chrome from a Docker container?
Karma config
The text was updated successfully, but these errors were encountered: