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

[WIP]: Caching slow test on github CI pipeline #6174

Conversation

Formasitchijoh
Copy link
Contributor

@Formasitchijoh Formasitchijoh commented Feb 4, 2025

What this PR does

This PR is a work in progress to reduce the build time on the CI pipeline by caching the response for slow test and running any other test when the test file changes

@ragesoss
Copy link
Member

ragesoss commented Feb 6, 2025

This seems promising. Is it possible to test how much it speeds things up, without merging it? If we use this approach, we'll also need some documentation of the caching strategy and instructions for breaking the cache.

@Formasitchijoh
Copy link
Contributor Author

This seems promising. Is it possible to test how much it speeds things up, without merging it? If we use this approach, we'll also need some documentation of the caching strategy and instructions for breaking the cache.

@ragesoss Thanks for the feedback! Just to clarify, are you asking if I can measure the speed improvement by running the CI pipeline on my branch before merging? My plan is to:

  • Run the CI on my branch and compare the total build time before and after caching.
  • Track how long the slow test takes with and without caching.
  • Run the pipeline multiple times to see if the caching consistently speeds things up.

@ragesoss
Copy link
Member

ragesoss commented Feb 6, 2025 via email

@Formasitchijoh Formasitchijoh reopened this Feb 6, 2025
@Formasitchijoh Formasitchijoh marked this pull request as draft February 7, 2025 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants