-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Reduce integration test overhead #32475
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
Reduce integration test overhead #32475
Conversation
Reduce overhead of preparing the test Git repos by avoiding unnecessary copying of already existing files.
For non-immediate queues, FlushWithContext takes at least 40ms to verify that all items are processed. Calling this in parallel allows for just a single 40ms delay, instead of 40ms per queue.
We could make it even faster (without any waiting time). Could I edit your PR to implement my idea? |
I'd be fine with this! |
60c0327
to
ace4671
Compare
ffb110b
to
527c049
Compare
Done from my side. |
I think these changes look good! |
* giteaofficial/main: Fix oauth2 error handle not return immediately (go-gitea#32514) Fix incorrect project page CSS class (go-gitea#32510) Add avif image file support (go-gitea#32508) Reduce integration test overhead (go-gitea#32475) Remove jQuery import from some files (go-gitea#32512) Trim title before insert/update to database to match the size requirements of database (go-gitea#32498) Reimplement GetUserOrgsList to make it simple and clear (go-gitea#32486)
Need a following up PR: Improve testing and try to fix MySQL hanging #32515 |
In profiling integration tests, I found a couple places where per-test overhead could be reduced:
PrintCurrentTest
, invokeFlushWithContext
in a parallel.