Skip to content

Test failure with external PCRE #12801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
orlitzky opened this issue Nov 27, 2023 · 3 comments
Closed

Test failure with external PCRE #12801

orlitzky opened this issue Nov 27, 2023 · 3 comments

Comments

@orlitzky
Copy link
Contributor

Description

FAILED TEST SUMMARY
---------------------------------------------------------------------
GH-11374 (PCRE regular expression without JIT enabled gives different result) [ext/pcre/tests/gh11374.phpt]

This was introduced in #12439 which backports a libpcre fix to the bundled copy and then tests for it. When using an external libpcre, nobody will have this fix because it doesn't appear in any released version of libpcre. So, the test fails.

Personally I don't think the test needs to be duplicated in PHP if it's already included in the upstream test suite (https://github.com/PCRE2Project/pcre2/pull/300/files), but if it's providing some peace of mind, maybe it could be made conditional on the internal libpcre?

PHP Version

git HEAD

Operating System

No response

@nielsdos
Copy link
Member

nielsdos commented Nov 27, 2023

I already took care of this in the current development versions by making it conditional on either being bundled or having a more recent version than 10.42 installed.
See

if (!zend_test_is_pcre_bundled() && (PCRE_VERSION_MAJOR == 10 && PCRE_VERSION_MINOR <= 42)) die("skip old pcre version");

@nielsdos nielsdos closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2023
@orlitzky
Copy link
Contributor Author

And that's why you git pull UPSTREAM master before filing a bug. Thank you :)

@nielsdos
Copy link
Member

No worries, I rather have people ask "too much" than "too little" :)

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

No branches or pull requests

2 participants