Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I poked around in this, and Im only seeing one other job that has been affected since this was last posted. Most of the core dump issues had to do with mysql errors, so I think we can assume that now that we're destroying the mysql containers each time, we're not likely to run into this issue again. If it does, we can re-open and solve.
Comments
Comment #1
MixologicComment #2
MixologicThese jobs all failed this way, documenting in the hopes that there is discoverable pattern.
https://dispatcher.drupalci.org/job/default/270/console
https://dispatcher.drupalci.org/job/default/686/console
https://dispatcher.drupalci.org/job/default/690/console
https://dispatcher.drupalci.org/job/default/691/console
https://dispatcher.drupalci.org/job/default/697/console
https://dispatcher.drupalci.org/job/default/698/console
https://dispatcher.drupalci.org/job/default/2213/console
https://dispatcher.drupalci.org/job/default/2220/console
https://dispatcher.drupalci.org/job/default/2221/console
https://dispatcher.drupalci.org/job/default/2222/console
https://dispatcher.drupalci.org/job/default/2223/console
https://dispatcher.drupalci.org/job/default/3594/console
https://dispatcher.drupalci.org/job/default/3817/console
https://dispatcher.drupalci.org/job/default/4126/console
https://dispatcher.drupalci.org/job/default/4258/console
https://dispatcher.drupalci.org/job/default/4327/console
https://dispatcher.drupalci.org/job/default/4329/console
Comment #3
MixologicI poked around in this, and Im only seeing one other job that has been affected since this was last posted. Most of the core dump issues had to do with mysql errors, so I think we can assume that now that we're destroying the mysql containers each time, we're not likely to run into this issue again. If it does, we can re-open and solve.
Comment #4
MixologicYeah, this just isnt happening.
Comment #5
Mixologic