-
Notifications
You must be signed in to change notification settings - Fork 400
Fix css/sass build failures #2275
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
Conversation
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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r+
Trying to delete the cache instead to see if that fixes it |
Woo! Deleting the Travis cache fixed this instead. |
Arrrgh! I didn't think of that. Thanks so much! I'll run through all the old PRs and restart them as needed.
Matthew Riley MacPherson (sent from mobile)
… On 18 Apr 2017, at 18:03, Kumar McMillan ***@***.***> wrote:
Woo! Deleting the Travis cache fixed this instead.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or mute the thread.
|
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 |
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.