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

Flood comparision tool #6337

Merged
merged 205 commits into from
Dec 8, 2023
Merged

Flood comparision tool #6337

merged 205 commits into from
Dec 8, 2023

Conversation

kamilchodola
Copy link
Contributor

Tool allows to test RPC with flood (https://github.com/paradigmxyz/flood/) - it is executing RPC tests comparing Your base to the selected node.
In case of this action it allows to compare with:

  1. Other branch (by specifying branch name)
  2. Infura
  3. Nethermind Archive node

Some changes may still be needed but would appear when developers would start using it more extensively.
Also PR to proper flood repo is needed to make test data more dynamic (currently working on Piotr fork).

Types of changes

What types of changes does your code introduce?

  • Bugfix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)
  • Breaking change (a change that causes existing functionality not to work as expected)
  • Optimization
  • Refactoring
  • Documentation update
  • Build-related changes
  • Other: New testing type

Testing

Requires testing

  • Yes
  • No

If yes, did you write tests?

  • Yes
  • No

Documentation

Requires documentation update

  • Yes
  • No

Requires explanation in Release Notes

  • Yes
  • No

benaadams and others added 30 commits November 28, 2023 20:16
* Use different processing timer

* Use single queue

* Revert to simpler
(cherry picked from commit 3e330ad)
(cherry picked from commit 47a92ee)
Fix path

Run on push temporarily

Fix file path

Fix inputs and missing vars

All fields not required

Inherit secrets when calling run-a-single-node-from-branch

Add default for cl_client

Use base_tag generated by run-a-single-node

Download artifacts from other post-merge-smoke-tests

Remove the old download-artifact

Change the name of token secret

Remove usage of external action

Allow to specify smoke tests branch to use

Remove additional option to fit dispatch limit

fix: wrong inputs string format

Export run id

Fix rpc url

Fix debug

Add runner's ip to `allowed_ips`

Maximum 10 inputs is allowed in workflow_dispatch

Add allowed_ips to workflow_dispatch inputs

Try to join two ips

Print `,` conditionally

Update public-ip

Debug

Use VPN

Add wireguard.conf

Fix location

Checkout the repository before installing wireguard

Update wireguard.conf to match nethermind repo secrets

Update environment variables to match secrets

Install flood before wireguard

Use include in matrix to specify both name and address

Revert "Use include in matrix to specify both name and address"

This reverts commit 71caa0c.
For github hosted runners time limit for a job is 6 hours.
It is less than a node needs to sync.
Thus we wait 5.5 hours before checking the sync status of node.
@kamilchodola kamilchodola requested review from rubo and a team as code owners December 6, 2023 18:02
@kamilchodola kamilchodola requested review from smartprogrammer93, benaadams, piwonskp, a team and rubo and removed request for a team and rubo December 6, 2023 18:02
main_branch_file="rpc_url%${{ env.CLEAN_MAIN_REF }}%${{ github.run_id }}.txt"
compare_branch_file="rpc_url%${{ env.CLEAN_COMPARE_REF }}%${{ github.run_id }}"

ls artifacts
Copy link
Contributor

Choose a reason for hiding this comment

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

a leftover from testing?

@kamilchodola kamilchodola merged commit 64dbf40 into master Dec 8, 2023
62 checks passed
@kamilchodola kamilchodola deleted the rpc-comparision-1.23.0 branch December 8, 2023 08:12
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.

7 participants