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

add diff script and results #3037

Merged
merged 11 commits into from
Jul 14, 2023
Merged

Conversation

wakamex
Copy link
Contributor

@wakamex wakamex commented Jul 11, 2023

reth folder contains output of run_all for my erigon node
compare_expect_produced.sh runs diffs on produced vs. expected
diffs contains output of compare_expect_produced.sh on those results

@tjayrush tjayrush changed the base branch from master to develop July 12, 2023 17:11

# Check if the diff output is non-empty
if [[ -n "$diff_output" ]]; then
# If it is non-empty, save it to a file in dir3
Copy link
Member

Choose a reason for hiding this comment

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

Can you echo the corresponding curl command into the file here? (And into the expected results.) This would make it easy to copy and paste the curl command to the command line. It would create invalid JSON, so maybe not. Your call.

@tjayrush
Copy link
Member

Thanks so much for this. Is it run against the latest Erigon?

@tjayrush
Copy link
Member

I'll merge it once you respond to my questions above.

@wakamex
Copy link
Contributor Author

wakamex commented Jul 12, 2023

Ran it against erigon, posted results here: paradigmxyz/reth#3721 (comment)

Also added some parameters for placing results in specific folders, to allow multi-way comparison, and added a log file to see which commands were executed

@wakamex
Copy link
Contributor Author

wakamex commented Jul 12, 2023

Now that I think about it, these trace tests may be nice to have in their own repo, so people from the future (👋) can reference this non-standard

@tjayrush
Copy link
Member

Now that I think about it, these trace tests may be nice to have in their own repo, so people from the future (👋) can reference this non-standard

Absolutely, 100%. Please feel free to do that. If you need me to help, please let me know. I can put a pointer in the README so there's not two confusing copies.

@tjayrush
Copy link
Member

Would you like me to merge this? Please advise.

@tjayrush tjayrush merged commit 894aaa1 into TrueBlocks:develop Jul 14, 2023
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.

2 participants