Fix test when session extension is shared

[andypost]

When extension is build as shared then testing fpm configuration gets no extensions from EXTENSIONS section

Actual order in which extensions are loaded is defined by distro-builders (often via numeric prefix 00_ 10_) and I see no good "grepable" way to figure order from .m4 and .w32 files (they need clean-up) only few hard dependencies are found using ZEND_MOD_REQUIRED (will provide PR later)

Ref #9523 (comment)

[cmb69]

Hmm, this looks somewhat hackish to me. Can't we just detect the extension_dir and all loaded extensions in Adoy\FastCGI\Client\Tester and set it there when starting the server? At the very least, we should use ini_get('extension_dir') instead of hard-coding the path.

[andypost]

Thanks, will fix extension_dir as it could be inherited

But I see no way to get access to list of dependencies for test

[cmb69]

But I see no way to get access to list of dependencies for test

Since these should already be loaded, you could use get_loaded_extensions(), but applying that might be a fiddly.

[andypost]

@cmb69 There's TEST_PHP_EXTRA_ARGS env variable but it needs clean-up to be passed to fpm... maybe there's a way to get EXTENSIONS from env or by template from run-tests

[andypost]

Check via get_loaded_extensions() will not work because test has all extensions already and has no knowledge about it the extension shared or bundled (this runners are different SAPI)

[andypost]

Ah, that's not the same process, the test starts new fpm process and missed to provide proper config to it

should already be loaded

[andypost]

Using this as patch for 8.1 and 8.2 in Alpinelinux hope to get it in

[bukka]

I think this needs to be done differently. We could for example introduce a new environment variable and update CMD if there are set in a similar way like TEST_FPM_RUN_AS_ROOT. It should be enough to have it for extension dir (e.g. TEST_FPM_EXTENSION_DIR) and then have new parameter for required extension. If extension dir is set, it would be then provided as a list of additional parameters.

[bukka]

This produces warning if the session is statically compiled.

[bukka]

This is just specific to your setup where your extension dir is in modules so it cannot be applied in general. For example it produces warning in my local setup as I use some shared extensions that are not obviously in this directory.

[bukka]

@andypost I though that it might be easier to just implement it as that description might have not been that clear. Here it is: #9854 . Not tested so please test it. :)

[andypost]

Closing in favour of #9854