Skip to content

Conversation

@s8sato
Copy link
Contributor

@s8sato s8sato commented Mar 16, 2025

Prerequisites for testing the prediction feature in #5355.

Signed-off-by: Shunkichi Sato <[email protected]>
@s8sato s8sato added the CI label Mar 16, 2025
@s8sato s8sato self-assigned this Mar 16, 2025
@s8sato s8sato marked this pull request as ready for review March 16, 2025 18:37
@s8sato s8sato enabled auto-merge (squash) March 16, 2025 18:37
@s8sato s8sato disabled auto-merge March 16, 2025 22:08
@s8sato s8sato marked this pull request as draft March 16, 2025 22:08
Copy link
Contributor

@0x009922 0x009922 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 it isn't really necessary to compile irohad twice. It's fine to compile once with all features.

mv ${{ env.WASM_TARGET_DIR }}/libs ${{ env.DEFAULTS_DIR }}/libs
mv ${{ env.DEFAULTS_DIR }}/libs/default_executor.wasm ${{ env.DEFAULTS_DIR }}/executor.wasm
- name: Install irohad
run: which irohad || cargo install --path crates/irohad --locked
Copy link
Contributor Author

Choose a reason for hiding this comment

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

By the way, what is the possible cases that irohad is found by which command here @0x009922 ?

Copy link
Contributor

Choose a reason for hiding this comment

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

As far as I remember, it was about caching and the possibility that irohad is already available. Though I don't understand how that could be possible.

@s8sato
Copy link
Contributor Author

s8sato commented May 8, 2025

Closed as not planned, in accordance with #5355 (comment)

@s8sato s8sato closed this May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants