-
Notifications
You must be signed in to change notification settings - Fork 28
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
Make holesky-test suite faster #154
Comments
preprod is unstable, it is more difficult to identify. testnet now is 3 mins |
Indeed bowen just showed me testnet has been updated to 3 min batches: https://github.com/Layr-Labs/eigenda-devops/blob/master/charts/batcher/values/eigenda-testnet/us-east-1/holesky/values.yaml#L15 what does "difficult to identify" mean? |
difficult to identify the root cause when there is error. Moreover, oncall has responsibility to fix testnet, whereas it is possible for preprod to dangle for a while Finality is taking a larger chunk of time now, 3mins vs 12mins. But I think it makes sense to test for finality. |
Update: seems like e2e tests still took 14 mins without waiting for finality (action from #160)... so there's prob something else causing them to be slow. |
@samlaf we could trying logging the |
testnet has 10 min batching intervals, which I think (?) is why the holesky-e2e tests currently take roughly 20 mins to run. preprod cluster has 1 min batching, which should reduce the ci time for that test.holesky e2e test suite takes >15mins to run. Makes waiting for ci unbearably long, and devex experience pretty bad. We should find a way to optimize these tests.
The text was updated successfully, but these errors were encountered: