- Issue created by @bbrala
- @bbrala opened merge request.
- Status changed to Needs work
10 months ago 12:46pm 1 November 2023 - Status changed to Needs review
10 months ago 1:35pm 1 November 2023 - First commit to issue fork.
- Status changed to RTBC
10 months ago 5:34pm 1 November 2023 - 🇬🇧United Kingdom catch
I made some commits here but the only eventual change was going from 12 cores for functional tests to 24. At 20 or less we were seeing spikes where running tests would spike from ~6m30s to ~9m seemingly somewhat at random (i.e. not a gradual degradation but a sudden drop off). As a first step this is great, and we can try to do more in follow-ups like trading off parallel vs. concurrency as well as discussing with the infra team.
- Status changed to Downport
10 months ago 10:56pm 2 November 2023 - 🇬🇧United Kingdom catch
Going ahead and committing this because the quicker we do that, the quicker we'll get feedback from the DA on what the effect on runners is.
Committed/pushed to 11.x and cherry-picked to 10.2.x, thanks!
Doesn't apply to 10.1.x but we should probably try to backport it there, so moving to 'to be ported'.
- 🇮🇳India Gauravvv Delhi, India
I have re-rolled the patch fro 10.1.x. please check
- last update
10 months ago 29,678 pass - Status changed to RTBC
10 months ago 9:57am 12 November 2023 - 🇧🇪Belgium BramDriesen Belgium 🇧🇪
Thanks @Gauravvvv, I reviewed the patch and verified that all changes are at the correct place and have the correct value for the correct block. Think this is good to go into 10.1.x. Setting to RTBC since it's already reviewed before the other two commits.
- Status changed to Fixed
10 months ago 1:03pm 12 November 2023 Automatically closed - issue fixed for 2 weeks with no activity.