-
Notifications
You must be signed in to change notification settings - Fork 7
Make witness generation conform to draft specs #8
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
base: main
Are you sure you want to change the base?
Changes from all commits
762348a
4c5f7d3
65594e9
b4c467c
78ae37e
7fe7493
fd4e9d1
5a2e472
3b227d0
1b0e9ec
f0edf76
eb4423f
d227eb7
c52abfb
444944d
402659c
6406a96
969b7fe
95174b5
315fcda
4a69b22
6846e66
e2a4498
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -54,6 +54,24 @@ jobs: | |
| - name: Run EF tests | ||
| run: ./scripts/run_ef_tests.sh ${{ matrix.trie }} | ||
|
|
||
| execution-witness-tests: | ||
|
jsign marked this conversation as resolved.
|
||
| name: Execution Witness tests | ||
| runs-on: ubuntu-latest | ||
| timeout-minutes: 30 | ||
| env: | ||
| RUST_LOG: info | ||
| RUST_BACKTRACE: 1 | ||
| EF_TEST_TRIE: default | ||
| EXECUTION_WITNESS_TESTS_URL: https://github.com/jsign/artifacts/releases/download/execution_witness_v0.0.1/execution_witness_tests_409fae8.tar.gz | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - uses: dtolnay/rust-toolchain@stable | ||
| - uses: Swatinem/rust-cache@v2 | ||
| with: | ||
| cache-on-failure: true | ||
| - name: Run Execution Witness tests | ||
| run: cargo run -p ef-test-runner --release -- --skip testing/runner/execution-witness-skip.txt $EXECUTION_WITNESS_TESTS_URL | ||
|
Comment on lines
+58
to
+73
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As I mentioned in a comment, there are now official spec and tests. But since they are meant to run on top of hte latest BAL devnet EL branches, for this PR I decided to keep these older execution witness tests, just temporarily. Not all the tests pass though, and the reason why is explained in the I would say to:
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we're running these official fixtures at stateless@bal-devnet-3 still some things to do regarding the ability to debug the tests properly (some don't pass) but most of the reth@bal-devnet-3 patching has been done
we should wait for upstream first imo, the detached commit problem would also be solved
would be very appreciated :)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nice, sounds great you're doing progress in that branch 🔥 I'll create the issue to explain things in more detail later/soon today. |
||
|
|
||
| no-std: | ||
| name: no_std (RISC-V) | ||
| runs-on: ubuntu-latest | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.