Work around "[Error 35] Resource unavailable" on Python 2.7 during CI conda packaging #1259
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelbabyn
pushed a commit
to michaelbabyn/plotly.py
that referenced
this pull request
Dec 22, 2018
… conda packaging (plotly#1259) * Work around ""[Error 35] Resource unavailable" on Python 2.7 * Write output file to artifacts directory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building conda packages for Python 2.7 has been erroring out with "[Error 35] Resource unavailable".
This seems to be somewhat related to the volume of output that the conda build command produces. This PR reduces the verbosity of conda-build and redirects output to a file and uploads that as a circle CI artifact