Update Travis & AppVeyor to allow node 0.10 failures #659
Conversation
|
Woot, my AppVeyor had a node 0.10 failure but the suite is marked as successful so it looks like everything is working. |
.travis.yml
Outdated
| - '0.10' | ||
| os: | ||
| - linux | ||
| - osx | ||
| script: | ||
| - npm run ci-test | ||
| sudo: false | ||
| matrix: | ||
| allow_failures: | ||
| - node_js: '0.10' |
There was a problem hiding this comment.
0.10 is actually reliable enough on Travis. There are random failures on OS X all the time, but Travis makes it easy enough to restart the specific items until they pass.
I don't think we need this one.
There was a problem hiding this comment.
Alright, I'll remove
|
Amended and force-pushed. |
|
@es128 coveralls API is being super flakey so I moved the coverage upload to Do you expect v2 to be released today? I'm really hoping to get gulp4 finalized and published to npm before Jan1 |
|
@phated idk whether it will work out to publish today. Should we add node v9 to the CI configs in this PR? |
|
Sure, I'll update shortly. What other things will we be waiting on? I have bandwidth to help out |
|
Off the top of my head: a new changelog entry and updating the readme appveyor badge to the new paulmillr path |
|
On it! |
1 similar comment
I believe this is the correct configuration but I'm still waiting on my AppVeyor to run.
@es128