- Issue created by @fjgarlin
- last update
over 1 year ago run-tests.sh exception - last update
over 1 year ago run-tests.sh exception - Status changed to Needs work
over 1 year ago 12:06pm 24 November 2023 - 🇪🇸Spain fjgarlin
MariaDB is connecting now. However, mid-tests, we have
SQLSTATE[HY000] [2006] MySQL server has gone away in
Am I am not sure why...
- last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - First commit to issue fork.
- last update
over 1 year ago 2,163 pass - last update
over 1 year ago run-tests.sh exception - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - last update
over 1 year ago 2,163 pass - Status changed to Needs review
over 1 year ago 11:53am 27 November 2023 - 🇪🇸Spain fjgarlin
The MR is ready for review: https://git.drupalcode.org/project/drupal/-/merge_requests/5537/diffs
The changes are:
- Uncomment the MariaDB job
- Tweak the CONCURRENCY value for the MariaDB image to work. This value is the same as D10+ is using (probably for the same reasons).
- Also tweak KUBERNETES_CPU_REQUEST value to match that of D10+ for similar jobs, as that also has an impact on the running/waiting time.
- Echo the value of echo SIMPLETEST_DB to be 100% sure that is the right one (also done in D10+ for the same reasons).The last MariaDB pipelines are running as expected. ie: https://git.drupalcode.org/issue/drupal-3403989/-/pipelines/55604
- Status changed to RTBC
over 1 year ago 2:14pm 29 November 2023 - 🇧🇪Belgium BramDriesen Belgium 🇧🇪
This looks straightforward enough 😁 wanted to comment if we needed the echo but then saw your comment again. LGTM!
- last update
over 1 year ago run-tests.sh exception - 🇸🇰Slovakia poker10
Thanks for working on this!
@fjgarlin, I see that in D10 the
CONCURRENCY
is 24 (https://git.drupalcode.org/project/drupal/-/blob/11.x/.gitlab-ci.yml?ref...), only for PHPUnit Functional Javascript tests there is 15 (but these are JS browser tests, something that is not in D7). Should we then keep theCONCURRENCY
at 24 for D7 as well?KUBERNETES_CPU_REQUEST
seems to be aligned with D10 on value 16. - 🇪🇸Spain fjgarlin
I'm good either way. The MariaDB images weren't copying with that at first, but that was fixed in #3404256: MySQL/MariaDB containers do not use the provided configuration → and they should now.
Having said that, whilst working on ✨ [investigation] get metrics of request to see which settings need to be changed for random failures Active we've been recommended by infra not to have too high concurrency and to have it aligned/close with the cpu_request value. By having values close to one another the pod assigned to run the job should have a normal load. This one is still a work in progress tho.
So I'm happy to make changes and adjust values but I'm also happy with the suggested values.
- Status changed to Fixed
over 1 year ago 5:23pm 30 November 2023 - 🇸🇰Slovakia poker10
Ok, sounds good. Let's use these values as proposed in the MR - it will align the concurrency with cpu_request as recommended and similar setup is in D10. We can always change that in the future if needed. Committed and pushed, so we will have MariaDB working. Thanks all!
Automatically closed - issue fixed for 2 weeks with no activity.