-
Notifications
You must be signed in to change notification settings - Fork 81
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
Upgraded the downloaded stack version to 2.7.5 #1751
Conversation
expiry issues on mirrors.json: haskell/hackage-server#834
Hi @symbiont-eric-torreborre , thanks for the PR! Could you elaborate a bit why you think this fixes the expiry issue? AFAIU, this is a server side problem and can only be fixed by updating the mirrors.json file? |
Hi, @avdv
That's because this check has been disabled by default in The mirrors.json file has indeed been eventually uploaded but our CI was down during the whole time. And as soon as you have SLAs your CI becomes really part of production :-) |
Is there anything I can / should do about the failing tests? |
Oh, that is quite old and is already part of stack 2.1.3. We had stack 2.3.1 which means you should not run into this problem... 🤔
For one, there was a problem downloading from hackage in the Build & Test - Nixpkgs (macos-10.15) check (was this the error you were seeing too?):
I restarted this job. Then, the Build & Test - bindist (windows-latest) check failed with a bazel crash after all tests were successful. Both, Build & Test - bindist (macos-10.15) and Build & Test - bindist (ubuntu-latest), failed because of this error:
Seems like we still use stack 2.3.1 somewhere. Could you look into this, please? |
@avdv oh, it looks like I misinterpreted this tag:
Good point! I dug into our CI logs when we had this issue and saw this that I missed the first time:
That would explain the
I'm going to have a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
@symbiont-eric-torreborre seems like the CI got stuck / wasn't triggered. Could you |
The default downloaded stack can be a new version but we should still be able to accept old ones
ce688ca
to
e05b545
Compare
done. |
I think the CI does not run on PRs from other repositories, so we usually push a copy of the branch to origin to trigger it:
|
🎉 |
to avoid expiry issues on mirrors.json: haskell/hackage-server#834.
I don't know if the additional field in
STACK_MIN_VERSION
works though. Maybe @facundominguez would know this?I also don't know if you prefer keeping a wider range of
stack
versions available despite this expiry issue.