Skip to content

Add Apache and LiteSpeed SAPI build smoke tests - #24783

Open
jassem-manita wants to merge 3 commits into
php:masterfrom
jassem-manita:ci/apache-litespeed-smoke-tests
Open

jassem-manita wants to merge 3 commits into
php:masterfrom
jassem-manita:ci/apache-litespeed-smoke-tests

Conversation

@jassem-manita

@jassem-manita jassem-manita commented Oct 27, 2026 •

Copy link
Copy Markdown

twards #23404
Adds build smoke tests for the Apache and LiteSpeed SAPIs.

The Apache test checks that PHP can be configured with --with-apxs2 and compiled against the Apache development headers. The LiteSpeed test checks that PHP can be configured with --enable-litespeed, compiled, and that the resulting lsphp binary starts and reports its version.

Both jobs run when the full CI job set is selected.

@DanielEScherzer

Copy link
Copy Markdown
Member

Label added, next time this is updated it will run all of the tests so we can actually see if the added tests pass
@jassem-manita should we also create a "CI: SAPI builds" label or something similar to trigger these two new tests but not everything? If yes I'll create that label and update the labels for this PR

@jassem-manita

Copy link
Copy Markdown
Author

Label added, next time this is updated it will run all of the tests so we can actually see if the added tests pass
@jassem-manita should we also create a "CI: SAPI builds" label or something similar to trigger these two new tests but not everything? If yes I'll create that label and update the labels for this PR

I’ve already tested both builds locally on Ubuntu 24.04 and they worked fine. A separate label would be useful to test them without running everything.

@DanielEScherzer

Copy link
Copy Markdown
Member

Done, please update the matrix.php logic to account for the new label

@NattyNarwhal

Copy link
Copy Markdown
Member

I do have GH-23405 which just adds Apache to mostly all the jobs, but doesn't handle LiteSpeed as I didn't look into it. (I also need to figure out what's up with that OpenSSL error on macOS, I wasn't able to reproduce it locally) Seems like it could also just be enabled across many of the existing jobs as possible, since it isn't mutually exclusive like the Apache module is with i.e. embed SAPI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants