-
Notifications
You must be signed in to change notification settings - Fork 183
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
Upgrade gulp to gulp 4 #742
Conversation
@@ -22,8 +22,8 @@ | |||
<script src="../../shared_utils.js"></script> | |||
<script> | |||
runTestFiles([ | |||
"output_test.js", | |||
"assert_test.js" | |||
"assert_test.js", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rearranged the order to match the webpage order (assert, then output) as one way to encourage mocha not to flake out on the first test.
@@ -78,7 +78,26 @@ var plugin = function (options) { | |||
} | |||
|
|||
const chrome = await launchChrome(); | |||
const protocol = await CDP({port: chrome.port}); | |||
|
|||
let protocol = null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is from: https://github.com/discourse/discourse/blob/master/test/run-qunit.js
Found it on this issue report:
GoogleChrome/chrome-launcher#145
Not sure why we didn't run into it before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool - thank you for taking the time to dig into this so that we can have something that works as expected!
Travis CI was happy! :) |
High-level description of change
This PR upgrades gulp to gulp 4. There were issues with gulp 3 and the current node, so this resolves those issues.
Are there performance implications for this change?
I increased the timeout for tests to take (as the first test in the SQL output suite kept failing, despite seemingly being within the timeout), so that could increase time for tests to run. I don't think it practically does, however.
Have you added tests to cover this new/updated code?
No :)
Risks involved
There could be some flakiness with the new gulp that we haven't encountered yet. Wonder how it'll do on Travis.
Are there any dependencies or blockers for merging this?
No
How can we verify that this change works?
npm run build
npm run test