- Issue created by @elc
- Status changed to Needs work
5 months ago 3:50am 12 September 2024 - Issue was unassigned.
- Status changed to Fixed
5 months ago 10:32am 12 September 2024 - 🇺🇸United States greggles Denver, Colorado, USA
Wow, this is a great improvement. Thanks for making it and documenting the speedup!
- 🇦🇺Australia elc
I was fairly amazed by the speedup too. The other massive speedup was turning on concurrent phpunit which took the test run from 50-60 seconds down to 10-15. Inspired by the https://www.drupal.org/project/issues/search?issue_tags=Test%20suite%20p... →
There have been a lot of GitlabCI failures of late so I've been looking into what is causing issues - if the tests can run faster then there's less time being spent consuming that resource. Time of day is significant in the failures so it's a workload issue. Looking at the failures here, the biggest issue by far though appears to be downloading requirements from github as all requests for every composer build go direct! 🐛 Random HTTP timeouts for GitLab CI jobs Active is looking at dealing with that.
A caching squid proxy given to composer would make an enormous difference relatively trivially and composer has full proxy support using standard linux env variables.
Automatically closed - issue fixed for 2 weeks with no activity.