Skip to content
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

BUG: Use GNU tar instead of MacOS tar for checkpoint option #283

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

SimonRit
Copy link

@SimonRit SimonRit commented Sep 4, 2024

The action started failing with the message:

tar: Option --checkpoint=10000 is not supported                                                                                             

See here for the result before the patch here after the patch.

Copy link
Member

@dzenanz dzenanz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think all the remote modules broke recently, hopefully this will restore them?

@dzenanz dzenanz requested a review from thewtex September 4, 2024 14:37
@SimonRit
Copy link
Author

SimonRit commented Sep 4, 2024

There is also a disk space issue with macos arm, see here, but I don't know if it's the case on all remotes.

@dzenanz dzenanz merged commit 601dccf into InsightSoftwareConsortium:master Sep 4, 2024
1 check passed
@dzenanz
Copy link
Member

dzenanz commented Sep 4, 2024

The out of space issue is also present here: https://github.com/dzenanz/ITKMontage/actions/runs/10704742693/job/29678469324
but this patch is a move in the right direction.

@dzenanz
Copy link
Member

dzenanz commented Sep 4, 2024

Simon, could you look into python-build-workflow / build-macos-arm-py (9): No space left on device issue? Maybe the same virtual machine is used for all the arm packages? We could solve it by clearing the cache? Or reusing the cached files?

@SimonRit
Copy link
Author

SimonRit commented Sep 6, 2024

Simon, could you look into python-build-workflow / build-macos-arm-py (9): No space left on device issue? Maybe the same virtual machine is used for all the arm packages? We could solve it by clearing the cache? Or reusing the cached files?

See #284, let me know there if this is a good enough solution!

@thewtex
Copy link
Member

thewtex commented Sep 6, 2024

cherry-picked to release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants