Skip to content
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

testem: Use --no-sandbox on TravisCI #7566

Merged
merged 3 commits into from Jan 21, 2018
Merged

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Jan 21, 2018

Similar to ember-cli/ember-cli-chai#45 this updates the testem.js file of the app blueprint to run Chrome with --no-sandbox when used on TravisCI to avoid travis-ci/travis-ci#8836

/cc @backspace

@Turbo87 Turbo87 added the bug label Jan 21, 2018
@Turbo87 Turbo87 requested a review from rwjblue January 21, 2018 19:45
Copy link
Member

@rwjblue rwjblue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m 👍 on the change generally speaking (and think we should get a point release out with it), but had one question RE: the specific environment variable used...

@@ -11,11 +11,14 @@ module.exports = {
Chrome: {
mode: 'ci',
args: [
// --no-sandbox is needed when running Chrome inside a container
process.env.TRAVIS ? '--no-sandbox' : null,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use process.env.CI instead? As I understand it a number of CI providers have this same basic issues (e.g. GitLab CI), and the CI environment flag is pretty universal...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure... GitLab CI can and often does use Docker containers, but you can also run it on real hosts, AppVeyor is likely VM-based, so there are also some CI systems that do not run in containers. The condition is easy enough to adjust if needed 🤔

@backspace
Copy link
Contributor

Nice, thanks for looking into this. I figured the sandbox was desirable for some reason? haha oops

`ember-qunit` is now generating a test of its own which we did not expect before. Updating the expected number of tests fixes our CI runs.
@Turbo87
Copy link
Member Author

Turbo87 commented Jan 21, 2018

FYI I had to include two more commits to make CI pass on the release branch

@rwjblue rwjblue merged commit 24aeacc into ember-cli:release Jan 21, 2018
@Turbo87 Turbo87 deleted the no-sandbox branch January 21, 2018 22:31
dunnkers added a commit to dunnkers/ember-polymer that referenced this pull request Jan 22, 2018
Related to use of Headless Chrome, see ember-cli/ember-cli#7566.
dunnkers added a commit to dunnkers/ember-polymer-paper that referenced this pull request Jan 22, 2018
Related to use of Headless Chrome, see ember-cli/ember-cli#7566.
mrloop added a commit to mrloop/race-ext that referenced this pull request Jan 29, 2018
mrloop added a commit to mrloop/ember-retry that referenced this pull request Feb 21, 2018
cyk added a commit to cyk/ember-cli that referenced this pull request Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants