You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our go tests are starting to take quite a long time now, we should look into performance improvements or gating tests behind flags so they are not always ran. (though caching should already be doing this)
Here are the tests that are currently taking more than 2 seconds, sorted in ascending order:
Sadly caching doesn't tend to help because our top-most packages by definition depend on everything meaning 1. they're generally the slowest of tests as they're the most e2e-y, and 2. pretty much all changes to the codebase invalid their test cache
So I knew since we introduced them that the offline/local database based tests are a large source of time because they have to download the all.zip files multiple times and they can be quite large - I've had an idea or two on how we could possibly improve this which I'm exploring now and it looks like it's working (taking us down to 10 seconds!).
There's some trade-offs to discuss and I need to actually cleanup the code to confirm everything properly which is why I'm not sharing more details just yet, but mentioning it now in case anyone else looks at this to avoid possible double work
Our go tests are starting to take quite a long time now, we should look into performance improvements or gating tests behind flags so they are not always ran. (though caching should already be doing this)
Here are the tests that are currently taking more than 2 seconds, sorted in ascending order:
The text was updated successfully, but these errors were encountered: