Randy Fay
Randy Fay
Rebased to get docs test passing.
@mattstein do you want to take a look?
It's worth looking a a couple of things here: - [x] Why wasn't mariadb 10.11 previously being tested when snapshots and export-db were tested (export-db wasn't testing bzip2 on mariadb...
mariadb:10.4 failure seems to happen only on certain macOS systems. I'm able to recreate this, mariadb:10.4 only, on arm64. Maybe it's just arm64 that's the problem. Suspecting bad image push....
I re-pushed from arm64 machine and it solved this. `make PUSH=true DOCKER_ARGS=--no-cache VERSION=20240213_mariadb_1011_default mariadb_10.4` I will look at the original push (done via github) to see if there are any...
The last docker build here was done in https://github.com/rfay/ddev/actions/runs/7909096636/job/21589704201 It failed mariadb:10.8 and 10.11, didn't understand why, and pushed those from arm64 mac. I don't see anything at all interesting...
> Why wasn't mariadb 10.11 previously being tested when snapshots and export-db were tested (export-db wasn't testing bzip2 on mariadb 10.11 for sure)? TestDdevExportDB currently only tests the current default...
> Are there build complaints in several of the image builds? I see this in images based on Ubuntu 22.04: "Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead...
The problem pushing images with Ubuntu 22.04-derived dbimages (mariadb:10.8 + mariadb:10.11) is a SEGV on libc-bin (https://github.com/rfay/ddev/actions/runs/7944511561/job/21690113653#step:7:1533) ``` #16 71.57 Processing triggers for libc-bin (2.35-0ubuntu3.6) ... #16 71.74 Segmentation fault...