Closed
Conversation
Collaborator
|
This is curious. I'm not seeing an error in the logs, and I wasn't able to reproduce locally (on I wonder if this the build hitting a resource constraint of the worker. In mostly unrelated news, public arm64 workers are here, though how to get the build to properly split across platforms and push to Dockerhub correctly is not trivial based on our previous attempts. |
This reverts commit e64f126be9b26dd8768e999684e11656f54fddd1.
Collaborator
|
one last idea, could try disabling ninja e.g. with |
Collaborator
Author
|
Closing this in favor of #578 |
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
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.
Our docker build has been broken for ~a week. Noticed because the user in #564
was still getting images the old read_parquet syntax.