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

Consistent node-sass failures on master #389

Closed
mscdex opened this issue Mar 13, 2017 · 15 comments
Closed

Consistent node-sass failures on master #389

mscdex opened this issue Mar 13, 2017 · 15 comments

Comments

@mscdex
Copy link

mscdex commented Mar 13, 2017

  • Node Version: master
  • CitGM Version: whatever node CI is using
  • Platform: any

It seems that node-sass explicitly checks process.versions.modules, but currently the master branch has a module version (53) that is not in their current modules version list, so a couple of the binding tests fail every time.

Is there some way we can ignore these particular errors for node-sass or perhaps mark it as flaky on master?

@gdams
Copy link
Member

gdams commented Mar 13, 2017

we can definitely mark node-sass as flaky on master

@gibfahn
Copy link
Member

gibfahn commented Mar 13, 2017

@xzyfer could node-sass either support master, or proceed even if a later module version is found?

@xzyfer
Copy link
Contributor

xzyfer commented Mar 13, 2017

@gibfahn we can fix these failing tests. They shouldn't fail the way they are. I'll look into to it asap.

xzyfer added a commit to xzyfer/node-sass that referenced this issue Mar 21, 2017
This is a workaround for nodejs/citgm#389. The install/build flow
needs to be updated so that unsupported environments result in an
informative warning instead of a failure.
@xzyfer
Copy link
Contributor

xzyfer commented Mar 21, 2017

My apologies for the delay. I've just release node-sass@v4.5.1 which should address the issue described. We'll work on a more permanent solution so you don't run into this again with Node 9.

@mscdex mscdex closed this as completed Mar 21, 2017
@mscdex mscdex reopened this Mar 29, 2017
@mscdex
Copy link
Author

mscdex commented Mar 29, 2017

Reopening this as this seems to be happening again, my guess is because the module version (now 54) was bumped again due to the V8 5.7 upgrade.

ping @xzyfer

EDIT: PR incoming: sass/node-sass#1934

@xzyfer
Copy link
Contributor

xzyfer commented Mar 29, 2017

Will ship an update today. Will find time to make this more fault tolerant asap.

@xzyfer
Copy link
Contributor

xzyfer commented Mar 29, 2017

Published the fix in node-sass@v4.5.2

@mscdex
Copy link
Author

mscdex commented Mar 29, 2017

Thanks!

@mscdex mscdex closed this as completed Mar 29, 2017
@mscdex mscdex reopened this May 16, 2017
@mscdex
Copy link
Author

mscdex commented May 16, 2017

@xzyfer This is an issue again with node master, which currently has a modules version of '55'.

EDIT: Also note that master/v8.x will be upping its modules version higher sometime in the not-so-distant future too.

@xzyfer
Copy link
Contributor

xzyfer commented May 16, 2017

@mscdex patched in sass/node-sass#1969 and accounted for the bump to 57. Will ship in 4.5.3 with in the hour.

@MylesBorins
Copy link
Contributor

MylesBorins commented May 16, 2017 via email

@xzyfer
Copy link
Contributor

xzyfer commented May 16, 2017

Published node-sass@4.5.3 with support for module version 55 and 57.

@tech4him1
Copy link

@xzyfer Will this be fixed for future versions, or will it still need to be upgraded every new Node version?

@xzyfer
Copy link
Contributor

xzyfer commented Aug 17, 2017

@tech4him1 this will be fixed for reals, but I'd be lying if put a date on it. We're working on a better solution.

@tech4him1
Copy link

@xzyfer Do you have an issue on node-sass that I can watch, or just here?

@targos targos closed this as completed Dec 16, 2018
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

No branches or pull requests

7 participants