-
Notifications
You must be signed in to change notification settings - Fork 52
zkEVM-chain testing - Automation Infrastructure #28
Comments
I don't know if that's already planned: I did like to also activate the prover in ci tests but that requires heavy compute & ram. Hence, is it possible to integrate a custom runner that creates a sufficient instance from (example) the AWS spot market and terminates after the run? Something like in |
@pinkiebell the tasks listed here are for the most part ongoing (some are close to be done actually). We will be creating a utility to on/demand deploy and configure (how many provers, what ram, what cpu etc) individual full/fresh chain environments for testing purposes (via jenkins probably). That would require someone to manually run the jenkins job but at the same time gives more control over selection of needed resources. For ex, if a build fails due to oom, we include an option to redeploy the instance with more ram :). If we still think we need this in CI, it can certainly be done as well |
@pinkiebell having these tests outsourced to jenkins, has the added benefit of not running loooong lasting CI rounds in github |
Great! That will also solve the problem 👍 |
@pinkiebell @AronisAt79 can I help with this while I learn more about the project in general? |
@leolara Sounds good to me to getting used to the project structure. You have to check in with @AronisAt79 and @ntampakas for these tasks. I also added some smaller issues. Just look around and if you have any questions just ask on tg. We can also setup a call if you want. |
H @leolara ! thanks for offering a pair of hands! Much appreciated :). Would you like to start a tg group witih me (@mari0sAr) and Nick (@ntampakas) to discuss our ongoing activities? |
This is the parent task for all activities associated to creation of a fully automated environment to run functional and benchmarking tests against zkEVM-chain.
The text was updated successfully, but these errors were encountered: