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

Fix armv7 builds #694

Merged
merged 1 commit into from Dec 11, 2022
Merged

Fix armv7 builds #694

merged 1 commit into from Dec 11, 2022

Conversation

hasufell
Copy link
Member

No description provided.

@hasufell hasufell force-pushed the armv7-aarch64 branch 21 times, most recently from 3847328 to 4c09c98 Compare November 26, 2022 03:40
@hasufell
Copy link
Member Author

@newhoggy cabal-cache seems to do nothing, but doesn't error either: https://github.com/haskell/ghcup-hs/actions/runs/3552070582/jobs/5967056739#step:5:17079

I checked the bucket, it's empty. CABAL_DIR is set to a custom location.

@hasufell hasufell force-pushed the armv7-aarch64 branch 4 times, most recently from 682cf4e to c093022 Compare November 27, 2022 02:21
@hasufell
Copy link
Member Author

It seems only the self hosted runner is able to use cabal-cache with backblaze S3. I wonder if github runners have this blocked?

@hasufell
Copy link
Member Author

So with debug turned on I get

2022-11-27T03:01:48.7246401Z [Error] [tid: ThreadId 9][ServiceError] {
2022-11-27T03:01:48.7246691Z   service    = S3
2022-11-27T03:01:48.7246928Z   status     = 404 
2022-11-27T03:01:48.7247171Z   code       = 
2022-11-27T03:01:48.7247423Z   message    = Nothing
2022-11-27T03:01:48.7247784Z   request-id = Just da324536ddfccbd2

But cabal-cache does not error.

Additionally, this doesn't happen on our self hosted runner, only the github runners.

@newhoggy
Copy link

If downloading the cabal-cache does not error on 404 because that happens normally as well, for example using an uninitialised cache.

@newhoggy
Copy link

You could try using tmate to debug Github Actions https://github.com/mxschmitt/action-tmate

@hasufell hasufell force-pushed the armv7-aarch64 branch 27 times, most recently from 943628e to 32094b7 Compare December 11, 2022 12:59
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.

None yet

2 participants