Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Update CI builds for NodeJS 6 #1486

Closed
wants to merge 1 commit into from
Closed

Conversation

nschonni
Copy link
Contributor

@nschonni nschonni commented Apr 27, 2016

@xzyfer
Copy link
Contributor

xzyfer commented Apr 27, 2016

Thanks. This will currently fail hard.

On 4/27/16, Nick Schonning notifications@github.com wrote:

You can view, comment on, or merge this pull request online at:

#1486

-- Commit Summary --

  • Update CI builds for NodeJS 6

-- File Changes --

M .travis.yml (1)
M appveyor.yml (3)

-- Patch Links --

https://github.com/sass/node-sass/pull/1486.patch
https://github.com/sass/node-sass/pull/1486.diff


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1486

Regards,
Michael

@nschonni
Copy link
Contributor Author

Looks like Appveyor is passing because it doesn't understand the 6 version yet. Looking to see why

@nschonni
Copy link
Contributor Author

Looks like AppVeyor will support it shortly appveyor/ci#770

@xzyfer
Copy link
Contributor

xzyfer commented Apr 27, 2016

I think the bigger problem is that node-sass just won't compile with node 6 yet. Every major node release invariably means we need to update the C/C++ binding code.

At the very least we'll need to update NAN.

@nschonni
Copy link
Contributor Author

Yeah, someone pointed out in the other tread that NAN is still trying to figure out the issues raised by the depreciation messages.

@xzyfer
Copy link
Contributor

xzyfer commented Apr 27, 2016

To my amazement we compile fine on Node 6. I've started building some binaries.

@xzyfer xzyfer added the BLOCKED label Apr 28, 2016
@xzyfer xzyfer added this to the next.patch milestone Apr 28, 2016
@xzyfer
Copy link
Contributor

xzyfer commented Apr 28, 2016

@nschonni please update this to match the changes to .travis.yml in #1500.

@nschonni
Copy link
Contributor Author

Rebased

@nschonni nschonni assigned xzyfer and unassigned nschonni Apr 29, 2016
@xzyfer
Copy link
Contributor

xzyfer commented Apr 29, 2016

Thanks. This is final blocker for 3.7.0.

@nschonni
Copy link
Contributor Author

Realized that the AppVeyor config was spit between the tag and master builds. I added 6 to the master section and repushed

@roc
Copy link

roc commented Apr 29, 2016

Can't wait for 3.7.0! :-)

@xzyfer
Copy link
Contributor

xzyfer commented Apr 29, 2016

Looks like node 6 has shipped on appveyor. We have a failing test on node 7 Windows. Will take a closer look tomorrow. It looks race conditiony.

@saper
Copy link
Member

saper commented May 1, 2016

I wonder if this didn't get solved in nodejs/node#5950 , after v6.0 release.
Actually, this was included in v6.0: nodejs/node@c43b182 , so maybe it broke it?

@xzyfer
Copy link
Contributor

xzyfer commented May 1, 2016

@saper I want to go ahead an ship 3.7.0 with the debug files, which means we don't need to subst. We can retroactively add the debug files when/if nodejs/node#6500 is suitably resolved.

Any objections?

xzyfer added a commit to xzyfer/node-sass that referenced this pull request May 2, 2016
@xzyfer
Copy link
Contributor

xzyfer commented May 2, 2016

Superseded by #1517 because of timezones.

@xzyfer xzyfer closed this May 2, 2016
@xzyfer xzyfer removed the BLOCKED label May 2, 2016
@xzyfer xzyfer removed this from the next.patch milestone May 2, 2016
xzyfer added a commit that referenced this pull request May 2, 2016
@nschonni nschonni deleted the add-node6-ci branch May 2, 2016 23:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants