-
Notifications
You must be signed in to change notification settings - Fork 721
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
Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench #3707
Merged
Conversation
This file contains 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
jbgi
approved these changes
Mar 15, 2022
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 15, 2022
3656: cardano-node-3644: node state ADT expand. r=deepfire a=denisshevchenko As a result of #3591, we now have a new `DataPoint` called `NodeState`. An external application (for example, `cardano-wallet`) can ask for this `DataPoint` to know the current state of the node. Initially, `NodeState` was a primitive ADT and contained a very small portion of information. Now it's expanded. Also, this PR moved node's peers info in a separate `DataPoint`. The documentation is at: https://github.com/input-output-hk/cardano-node/wiki/cardano-node-and-DataPoints:-demo 3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Denis Shevchenko <denis.shevchenko@iohk.io> Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
Build failed (retrying...): |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 15, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
Build failed: |
7b479d4
to
2151fd1
Compare
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 15, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
2151fd1
to
72981b0
Compare
Canceled. |
d6a8631
to
442d9f0
Compare
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 16, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
Build failed: |
58b4d61
to
dfdfa8a
Compare
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 16, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
Build failed: |
1165de6
to
2c16fbd
Compare
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 18, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
2c16fbd
to
706f6ec
Compare
Canceled. |
706f6ec
to
8f67165
Compare
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 18, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
Build failed: |
… to query profile content
8f67165
to
9c61d35
Compare
9c61d35
to
0fd8482
Compare
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
Mar 18, 2022
3707: Workbench: make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input. Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
Build failed: |
bors r+ |
Build succeeded: |
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.
This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input.