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

Re-factor the npm test command, used by Travis, to avoid running the 'default_preferences' tasks concurrently (issue 10732) #11413

Merged
merged 1 commit into from
Dec 18, 2019

Conversation

Snuffleupagus
Copy link
Collaborator

Please note: This patch does not prevent the 'default_preferences' task from running more than once during npm test, but it does ensure that the tasks won't run concurrently by running the relevant tests in series.

While it would obviously still make sense to re-factor the gulpfile to account for changes in gulp version 4, by at least tweaking the npm test command the intermittent failures on Travis should at least go away.

…e 'default_preferences' tasks concurrently (issue 10732)

*Please note:* This patch does *not* prevent the 'default_preferences' task from running more than once during `npm test`, but it does ensure that the tasks won't run *concurrently* by running the relevant tests in *series*.

While it would obviously still make sense to re-factor the gulpfile to account for changes in `gulp` version 4, by at least tweaking the `npm test` command the intermittent failures on Travis should at least go away.
@timvandermeij
Copy link
Contributor

I agree. It would be helpful to at least get rid of the intermittent failures and fix the issues regarding Gulp 4 changes in a separate scope.

@Snuffleupagus Snuffleupagus marked this pull request as ready for review December 18, 2019 21:35
@Snuffleupagus
Copy link
Collaborator Author

I agree. It would be helpful to at least get rid of the intermittent failures and fix the issues regarding Gulp 4 changes in a separate scope.

Yeah, that was my thought as well (since a proper Gulp 4 migration is a larger undertaking); and I had trouble following all the changes in the other PR (and it doesn't seem to prevent the concurrency issue either).

@timvandermeij timvandermeij merged commit cf3f342 into mozilla:master Dec 18, 2019
@timvandermeij
Copy link
Contributor

Thank you for improving the situation here!

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.

2 participants