-
Notifications
You must be signed in to change notification settings - Fork 12
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
Speed up integration tests #104
Comments
Experimenting with running one integration test per GitHub Actions runner in #101 |
Results of consolidating multiple Multiple statements7d68ff5
Runs on Google Cloud VM:
One statementaf46d38
Runs on Google Cloud VM:
|
Note that Google Cloud VM used is GitHub Actions runners have 2 vCPUs and 7 GB ram: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources |
Results from running (while running
Total time: 5 min 45 sec Compared to total time in integration test: 6 min 53 sec |
Results with Google Cloud VM Manual commands: |
Results with Google Cloud VM Multiple statements (7d68ff5)
One statement (af46d38)
|
Repeated
One statement: 7 min 12 sec
|
SummaryTest run time of
|
CPU info: Note that this was collected separately from the tests; if the CPU changed between VMs of the same class that is not captured below. GitHub Actions
Google Cloud 4vCPUs (n2-standard-4)
Google Cloud 16vCPUs (n2-standard-16)
|
Results from single run on Google Cloud n2 VMs on af46d38
|
Logs 2 vCPUs, 8GB RAM
4 vCPUS, 16 GB RAM
4 vCPUs, 32GB RAM
16 vCPUs, 32GB RAM
16 vCPUs, 64GB RAM
|
Integration tests currently take 40+ minutes (example)
Caching the
charmcraft pack
LXC container (#78) decreased the time by about 15-20 minutesThis issue is to document efforts to further decrease the time
The text was updated successfully, but these errors were encountered: