Skip to content

ci: add flashbots integration tests to CI#222

Open
init4samwise wants to merge 2 commits intomainfrom
samwise/eng-1300-flashbots-ci
Open

ci: add flashbots integration tests to CI#222
init4samwise wants to merge 2 commits intomainfrom
samwise/eng-1300-flashbots-ci

Conversation

@init4samwise
Copy link
Contributor

Summary

Adds make test-flashbots command to the Builder CI pipeline.

Changes

  • Makefile: Added test-flashbots target that runs cargo nextest run --run-ignored=only --workspace to execute all ignored integration tests
  • flashbots-ci.yml: New GitHub Actions workflow that runs the flashbots integration tests on pushes to main and PRs

Testing

The workflow installs cargo-nextest and Foundry, then runs the integration tests that are currently marked with #[ignore] annotations.

Closes ENG-1300

- Add test-flashbots Makefile target that runs ignored integration tests
- Add flashbots-ci.yml workflow that runs on push to main and PRs
- Uses nextest with --run-ignored=only to run flashbots integration tests

Closes ENG-1300
Copy link
Contributor

@dylanlott dylanlott left a comment

Choose a reason for hiding this comment

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

This should be a triggerable job in Github Actions, but should not be added to the main CI pipeline. The Flashbots integrations tests are too flaky to be in the hot path. Also not sure if they still pass post-Fusaka.

Addresses review feedback - flashbots integration tests are too flaky
for the main CI pipeline. Changed to workflow_dispatch so tests can be
triggered manually when needed.

Added optional 'ref' input to allow testing specific branches/commits.
@init4samwise
Copy link
Contributor Author

Thanks for the review @dylanlott! Good call - I've updated the workflow to use workflow_dispatch instead of running on push/PR, so it's now manually triggerable only.

Also added an optional ref input so you can test specific branches/commits when needed.

Re: post-Fusaka compatibility - that's a good point. We can run the workflow manually once this is merged to verify current state.

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