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

Warning: Exited with error code 100 #189

Closed
soundasleep opened this Issue Feb 12, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@soundasleep

soundasleep commented Feb 12, 2015

On Windows x64 I am getting this warning repeatedly but very intermittently, but it doesn't seem to cause any problems. It looks like it's an issue with Sass holding onto file descriptors perhaps - I don't know what "100" means and --debug/--verbose provides no better debug information, but does sometimes reduce the frequency of the errors, maybe because of the slowness of printing extra debug information to console.

Running "sass:dist" (sass) task
Warning: Exited with error code 100 Use --force to continue.

To reproduce: run grunt sass sass sass sass sass - it's likely one of these targets will return 100, causing the grunt process to stop.

Hacky suggestion: change

if (code > 0) {

to

if (code > 0 && code !== 100) {
  • ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
  • Sass 3.2.19 (Media Mark)
  • grunt-contrib-sass 0.9.2
@sindresorhus

This comment has been minimized.

Show comment
Hide comment
@sindresorhus

sindresorhus Feb 12, 2015

Member

🌴 Not going to add a workaround without knowing why it happens. This issue is better opened on Sass itself as it seems there some issue on Windows. 🌴

Member

sindresorhus commented Feb 12, 2015

🌴 Not going to add a workaround without knowing why it happens. This issue is better opened on Sass itself as it seems there some issue on Windows. 🌴

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment