Skip to content

/ saltfs

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

Jump to bottom

Windows buildbot failure: LLVM ERROR: IO failure on output stream. #585

Closed
Ms2ger opened this issue Jan 24, 2017 · 3 comments
Closed

Windows buildbot failure: LLVM ERROR: IO failure on output stream. #585

Ms2ger opened this issue Jan 24, 2017 · 3 comments

Comments

@Ms2ger
Copy link
Contributor

@Ms2ger Ms2ger commented Jan 24, 2017

http://build.servo.org/builders/windows-msvc-dev/builds/482/steps/compile__1/logs/stdio

Possibly running out of disk space?
@Ms2ger
Copy link
Contributor Author

@Ms2ger Ms2ger commented Jan 24, 2017

I hit the "graceful shutdown" button on servo-windows1, that seems to have helped a bit.
This was referenced Jan 24, 2017
Merged
Merged
Merged
Merged
@Ms2ger
Copy link
Contributor Author

@Ms2ger Ms2ger commented Jan 25, 2017

@edunham @larsbergstrom this is making windows the long pole, can we please get a real fix? Thanks!
@jdm jdm mentioned this issue Jan 28, 2017
Merged
3 of 5 tasks complete
@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Jan 28, 2017

I just logged into servo-windows1 and restarted Buildbot, as well as removed some obsolete build directories. Currently looking for more old files to delete to free up space, but this should be ok for now.
@aneeshusa aneeshusa closed this Jan 28, 2017
@aneeshusa aneeshusa mentioned this issue Jan 28, 2017
Open
@asajeffrey asajeffrey mentioned this issue Jan 28, 2017
Merged
3 of 3 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@Ms2ger @aneeshusa
You can’t perform that action at this time.