-
Notifications
You must be signed in to change notification settings - Fork 217
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
Bump to cardano-node 1.29.0-rc1 #2831
Conversation
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.
Thanks
stack.yaml
Outdated
@@ -4,7 +4,7 @@ | |||
# | |||
# NOTE: Remember to update the version matrix in README.md when | |||
# bumping the Cardano version. | |||
resolver: https://raw.githubusercontent.com/input-output-hk/cardano-haskell/c2aa1078ca8261d98cfce16d1131fbc687f6692b/snapshots/cardano-alonzo-purple-1.0.1.yaml | |||
resolver: tmp-snapshot.yaml |
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.
If you would like to move the snapshot back into stack.yaml
, feel free.
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.
I'm not sure if it helps the cache issues, but very happy to try. And even if not, it's easier to bump cabal.project
and stack.yaml
in the same repo than having the cardano-haskell indirection.
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.
Yup, the buildkite cache does still break 😕
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.
OK, pity - sounds like we need add a cache key then, based on the content of stack.yaml
.
d62df56
to
d3be764
Compare
243f5a1
to
f8c0d9d
Compare
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
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.
Thanks 👍
Please do squash the fixup commits before merging.
Those Hydra build failures seem to have been due to some builds getting killed by a sysadmin. Unfortunately the killed builds (and builds depending on them) were cached as failed, and so kept on failing until I restarted them all. |
I thought I tried restarting them before, but ran into exactly the same issues 🤔 — but I might have misread it |
4731833
to
d7be0b9
Compare
Thanks for the help @rvl ! bors r+ |
2831: Bump to cardano-node 1.29.0-rc1 r=Anviking a=Anviking - [x] Bump to cardano-node 1.29.0-rc1 - [x] Bump to the actual tag, when it exists - <s>Move snapshot to cardano-haskell</s> - [x] Update readme - [ ] Fix arcane windows hydra issues ### Issue Number <!-- Put here a reference to the issue that this PR relates to and which requirements it tackles. Jira issues of the form ADP- will be auto-linked. --> ADP-1081 ### Comments <!-- Additional comments or screenshots to attach if any --> Co-authored-by: Johannes Lund <[email protected]> Co-authored-by: Rodney Lorrimar <[email protected]>
Build failed: |
No, the recent failure is recent, and not cached. Previously I saw:
which I thought was related to https://input-output-rnd.slack.com/archives/CAP8NM7N0/p1629473846081300?thread_ts=1623935006.211500&cid=CAP8NM7N0 But this time it just failed with
|
bors r+ |
Build succeeded: |
Move snapshot to cardano-haskellIssue Number
ADP-1081
Comments