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

op-acceptor / devnet-sdk: Introduce room to alter test scheduling #14711

Open
protolambda opened this issue Mar 7, 2025 · 0 comments
Open

op-acceptor / devnet-sdk: Introduce room to alter test scheduling #14711

protolambda opened this issue Mar 7, 2025 · 0 comments
Labels
A-devnet-sdk Area: devnet-sdk

Comments

@protolambda
Copy link
Contributor

protolambda commented Mar 7, 2025

Introduce room to alter the scheduling of tests based on the availability of a devnet config.

Right now, opportunistically reuse devnet across tests (applies to op-e2e stack).

Note that the Go test runner does not offer this, this is something where:

  • the op-acceptor / test-runner will need to express what systems are "pending"
  • the devnet SDK will need to express if a "pending" system is preferred and then exit
  • the test runner can then schedule the test against the pending system.

Scheduling is difficult and may only make an impact once there are many different systems to choose from.
This feature is low-priority until this changes.

Right now, opportunistically reuse devnet across tests.

@protolambda protolambda added the A-devnet-sdk Area: devnet-sdk label Mar 7, 2025
@teddyknox teddyknox changed the title op-acceptor / devnet-sdk: introduce room to alter test scheduling op-acceptor / devnet-sdk: Introduce room to alter test scheduling Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-devnet-sdk Area: devnet-sdk
Projects
None yet
Development

No branches or pull requests

1 participant