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

Bug Fix (#882) Use correct feature flags with srtool #884

Merged
merged 1 commit into from
Jan 9, 2023

Conversation

wilwade
Copy link
Collaborator

@wilwade wilwade commented Jan 7, 2023

Goal

The goal of this PR is to make sure that the correct feature flags are being used with srtool for wasm generation

Closes #882

Discussion

  • srtool default-features flag does not work as intended
  • Instead using build-opts
  • Enabled debug logging in srtool for easier checking
  • Added subwasm check to test the output wasm

Test Runs:

Checklist

  • Tests added

Enabled debug logging in srtool for easier checking
Copy link
Collaborator

@saraswatpuneet saraswatpuneet left a comment

Choose a reason for hiding this comment

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

🎉🎤 will figure out issue with default features

Copy link
Collaborator

@demisx demisx left a comment

Choose a reason for hiding this comment

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

I presume doing the "Test WASM this in "Verify PR" workflow is not possible? Just trying to see if there is a way to fail early, not during release.

Other than that, looks good.

@wilwade wilwade merged commit 6053ae1 into main Jan 9, 2023
@wilwade wilwade deleted the bug/fix-srtool-issue-882 branch January 9, 2023 13:26
@wilwade
Copy link
Collaborator Author

wilwade commented Jan 9, 2023

@demisx

I presume doing the "Test WASM this in "Verify PR" workflow is not possible? Just trying to see if there is a way to fail early, not during release.

This really is just a check on srtool not our code, so it is release oriented only. None of our code /should/ impact this.

Also keeping an eye on chevdor/srtool-cli#7 to see if we can use something simpler when it is out.

abadaa pushed a commit that referenced this pull request Jan 10, 2023
# Goal
The goal of this PR is to make sure that the correct feature flags are
being used with srtool for wasm generation

Closes #882 

# Discussion
- srtool default-features flag does not work as intended
- Instead using build-opts
- Enabled debug logging in srtool for easier checking
- Added subwasm check to test the output wasm

Test Runs:
- Mainnet:
https://github.com/LibertyDSNP/frequency/actions/runs/3859784794/jobs/6579633360
<img width="1010" alt="image"
src="https://user-images.githubusercontent.com/1252199/211126355-d6f917d3-0ef2-447c-8f81-ac5333ce34d1.png">

- Rococo:
https://github.com/LibertyDSNP/frequency/actions/runs/3859784794/jobs/6579633325
<img width="892" alt="image"
src="https://user-images.githubusercontent.com/1252199/211126378-037467be-b34d-4e6c-bafb-effdafb46328.png">


# Checklist
- [x] Tests added
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.

[Bug] mainnet wasm has wrong version
3 participants