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

[CI]: investigating broken CI #864

Closed
misterdev opened this issue Apr 26, 2019 · 5 comments · Fixed by #871
Closed

[CI]: investigating broken CI #864

misterdev opened this issue Apr 26, 2019 · 5 comments · Fixed by #871

Comments

@misterdev
Copy link
Contributor

Describe the bug
I'm investigating on how to fix the currently broken CI.

Travis on the same commit completed with success previously (see builds):

zio

But now fails on travis_wait npm ci (log).

Does anyone knows what is happening?

@ematipico
Copy link
Contributor

I can't tell honestly. Maybe it's an issue with travis + lerna?

@ematipico
Copy link
Contributor

Ok, the problem is around Node 12. I'd suggest, to fix this issue, is to remove the stable from our Travis CI configuration and adding Node 12 as separate PR. Probably there's a breaking change around our deps or around travis

@misterdev
Copy link
Contributor Author

Ok, I'll take a look at this. Thank you!

@misterdev
Copy link
Contributor Author

The installation of iltorb fails when node-gyp rebuild is executed.
It happens on Windows, Linux, and MacOS both on Travis and Azure Pipelines (see #872), the common factor is Node 12, that explains why the CI broke the same day that Node 12 became "stable"

iltorb

@misterdev
Copy link
Contributor Author

Seems like iltorb doesn't support node 12
We use bundlesize that depends on iltorb, there's an open PR to fix this bundlesize#295 I guess we should wait for it to be merged.

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

Successfully merging a pull request may close this issue.

2 participants