-
Notifications
You must be signed in to change notification settings - Fork 580
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
Restructure E2E tests to reduce number of runners used #5062
Labels
e2e
type: productivity
Increase dev productivity and throughput by improving developer tooling, infrastructure, automation
Comments
chatton
added
type: refactor
Architecture, code or CI improvements that may or may not tackle technical debt.
e2e
labels
Nov 8, 2023
@chatton could I pick up this issue ? |
Hey @chatton, I'm here to solve it with @vuong177.
|
9 tasks
crodriguezvega
added
type: productivity
Increase dev productivity and throughput by improving developer tooling, infrastructure, automation
and removed
type: refactor
Architecture, code or CI improvements that may or may not tackle technical debt.
labels
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
e2e
type: productivity
Increase dev productivity and throughput by improving developer tooling, infrastructure, automation
Summary
Currently, our E2E tests use one host per runner, each test spins up a new chain, we run a test, and tear down the chain.
In order to save on runners, we can instead try to run 1 test suite per runner. Implementation wise the following may work
t.Parallel()
We would need to watch out for tests that have chain-wide effects like anything using gov proposals etc.
Ideally we can still run individual tests the way we do now locally.
For Admin Use
The text was updated successfully, but these errors were encountered: