Alpine 3.19 fails t/cli test with segmentation fault

[esabol]

FAIL: t/cli
===========

cli.gearman.--help					0:033674204 [ ok ]
cli.gearman.-H					0:037695937 [ ok ]
cli.gearman.-v					0:043918606 [ ok ]
cli.gearman.--unknown					0:038236170 [ ok ]
cli.gearman.-f echo -b payload					0:029500142 [ ok ]
cli.gearman.lp:833394					0:028560832 [ ok ]
cli.gearadmin.--help					0:022076461 [ ok ]
cli.gearadmin.--server-version					0:027260826 [ ok ]
cli.gearadmin.--server-verbose					0:027537683 [ ok ]
cli.gearadmin.--cancel-job					0:027294855 [ ok ]
cli.gearadmin.--show-jobs					0:027264252 [ ok ]
cli.gearadmin.--show-unique-jobs					0:027400623 [ ok ]
cli.gearadmin.--status					0:026903456 [ ok ]
cli.gearadmin.--priority-status					0:027035630 [ ok ]
cli.gearadmin.gearman_client_do_background(100) --status					0:717371613 [ ok ]
cli.gearadmin.--getpid					0:028108214 [ ok ]
cli.gearadmin.--workers					0:027960938 [ ok ]
cli.gearadmin.--create-function and --drop-function					0:054287913 [ ok ]
cli.gearadmin.--unknown					0:022723293 [ ok ]
Segmentation fault (core dumped)
FAIL t/cli (exit status: 139)

https://github.com/gearman/gearmand/actions/runs/10027275603/job/27712702515?pr=362#step:14:97

[esabol]

It's reproducible. I think the gearadmin_shutdown_test comes after cli.gearadmin.--unknown.

I'm wondering if PR #404 might fix this segmentation fault? That would just be too convenient, I'm sure! But that PR would fix an issue in libtest which could conceivably cause a segmentation fault....

[esabol]

I'm wondering if PR #404 might fix this segmentation fault? That would just be too convenient, I'm sure! But that PR would fix an issue in libtest which could conceivably cause a segmentation fault....

This indeed was the case. Alpine 3.19 build added to GitHub Actions CI in PR #410. Closing.