Skip to content

Conversation

kumar303
Copy link
Contributor

@kumar303 kumar303 commented Apr 17, 2017

This should stop failures like this from happening: https://travis-ci.org/mozilla/addons-frontend/jobs/222881961

It appears that Travis had some cached artifacts of node-sass lying around and when it upgraded to a new LTS Node version, node-sass was left in a broken state.

before_script:
# Make sure we have the right node-sass. See:
# https://github.com/webpack-contrib/css-loader/issues/240#issuecomment-252661267
- npm rebuild node-sass
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This takes 5 seconds which sucks. Any ideas for improvement?

@kumar303 kumar303 requested a review from tofumatt April 17, 2017 21:20
@kumar303 kumar303 changed the title [WIP] Fix css/sass build failures Fix css/sass build failures Apr 17, 2017
Copy link
Contributor

@muffinresearch muffinresearch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+

@kumar303
Copy link
Contributor Author

Trying to delete the cache instead to see if that fixes it

@kumar303
Copy link
Contributor Author

Woo! Deleting the Travis cache fixed this instead.

@tofumatt
Copy link
Contributor

tofumatt commented Apr 18, 2017 via email

@kumar303
Copy link
Contributor Author

kumar303 commented Apr 18, 2017

Actually, we'll also need to delete the cache for any PR that is currently failing. There is sadly no 'delete all' button unless I'm missing it. https://travis-ci.org/mozilla/addons-frontend/caches

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 this pull request may close these issues.

3 participants