Skip to content
This repository has been archived by the owner on Jul 10, 2023. It is now read-only.

zkEVM-chain testing - Automation Infrastructure #28

Open
AronisAt79 opened this issue Sep 1, 2022 · 8 comments
Open

zkEVM-chain testing - Automation Infrastructure #28

AronisAt79 opened this issue Sep 1, 2022 · 8 comments
Assignees

Comments

@AronisAt79
Copy link
Contributor

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.

@AronisAt79
Copy link
Contributor Author

AronisAt79 commented Sep 1, 2022

This is a growing list of sub tasks:
#29
#30
#31
#32
#33
#34

#38

@pinkiebell
Copy link
Contributor

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 zkevm-circuits though without any reserved instances (if any).

@AronisAt79
Copy link
Contributor Author

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 zkevm-circuits though without any reserved instances (if any).

@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

@AronisAt79
Copy link
Contributor Author

@pinkiebell having these tests outsourced to jenkins, has the added benefit of not running loooong lasting CI rounds in github

@pinkiebell
Copy link
Contributor

Great! That will also solve the problem 👍

@leolara
Copy link
Contributor

leolara commented Sep 6, 2022

@pinkiebell @AronisAt79 can I help with this while I learn more about the project in general?

@pinkiebell
Copy link
Contributor

@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.

@AronisAt79
Copy link
Contributor Author

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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: 🆕 Product Backlog Items
Development

No branches or pull requests

4 participants