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

chore: fix xvfb in travis config, patch safari karma launchers #5755

Merged
merged 4 commits into from
Jan 15, 2019

Conversation

brandonocasey
Copy link
Contributor

It seems that we are having some trouble using xvfb on travis. I could not find any issues/blog posts related to this, but I noticed that the docs have changed for its usage. This fix has already been used in the generator and appears to have fixed the issue.

@@ -67,6 +67,7 @@
"docs:fix": "remark --output -- './{,!(node_modules)/**/}!(CHANGELOG)*.md'",
"docs:lang": "node build/translations.js",
"netlify": "babel-node ./build/netlify-docs.js",
"prepare": "patch-package",
Copy link
Member

Choose a reason for hiding this comment

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

prepare runs before packing the package when when npm install is run without anything https://docs.npmjs.com/misc/scripts

@gkatsev gkatsev changed the title ignore: fix xvfb in travis config chore: fix xvfb in travis config, patch safari karma launchers Jan 15, 2019
@gkatsev
Copy link
Member

gkatsev commented Jan 15, 2019

mojave is a lot stricter about where you can open files from without user interaction and travis got updated to a mojave version with this restriction. We watch to patch the karma-safari-launcher and karma-safaritechpreview-launcher to look for an approved place on mojave when it exists.

@gkatsev gkatsev merged commit 144907f into master Jan 15, 2019
@gkatsev gkatsev deleted the ignore/fix-travis branch January 15, 2019 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants