mirror of
https://github.com/php/pftt2.git
synced 2026-03-24 09:12:17 +01:00
[Test Issue] [OpcacheOn] Opcache/opt test case fail when opcache.opt_debug_level=0x20000 #46
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hollyhuiLi on GitHub (Aug 27, 2019).
among all the opt test cases, 26 test cases having debug level 0x020000 all failed.
ext/opcache/tests/opt/dce_001.phpt
ext/opcache/tests/opt/dce_002.phpt
ext/opcache/tests/opt/dce_003.phpt
ext/opcache/tests/opt/dce_004.phpt
ext/opcache/tests/opt/dce_005.phpt
ext/opcache/tests/opt/dce_006.phpt
ext/opcache/tests/opt/dce_007.phpt
ext/opcache/tests/opt/dce_008.phpt
ext/opcache/tests/opt/jmp_001.phpt
ext/opcache/tests/opt/sccp_001.phpt
ext/opcache/tests/opt/sccp_002.phpt
ext/opcache/tests/opt/sccp_003.phpt
ext/opcache/tests/opt/sccp_004.phpt
ext/opcache/tests/opt/sccp_005.phpt
ext/opcache/tests/opt/sccp_006.phpt
ext/opcache/tests/opt/sccp_007.phpt
ext/opcache/tests/opt/sccp_008.phpt
ext/opcache/tests/opt/sccp_009.phpt
ext/opcache/tests/opt/sccp_010.phpt
ext/opcache/tests/opt/sccp_011.phpt
ext/opcache/tests/opt/sccp_012.phpt
ext/opcache/tests/opt/sccp_016.phpt
ext/opcache/tests/opt/sccp_017.phpt
ext/opcache/tests/opt/sccp_019.phpt
ext/opcache/tests/opt/sccp_022.phpt
ext/opcache/tests/opt/sccp_024.phpt
@cmb69 commented on GitHub (Aug 27, 2019):
I can reproduce this (Windows only) with run-test.php, so this is not directly related to PFTT, but rather a general issue. Please file a bug report in the bugtracker, and close this ticket afterwards. Thanks.
@hollyhuiLi commented on GitHub (Aug 28, 2019):
But from my side, it doesn't repro with run-test.php...
@cmb69 commented on GitHub (Aug 28, 2019):
Thanks! So I'll have a closer look ASAP.
@cmb69 commented on GitHub (Aug 29, 2019):
You're right. The problem is that these opcache dumps are written to stderr, but apparently stderr is ignored by the test output reader.
@cmb69 commented on GitHub (Sep 2, 2019):
Hmm, not always at least (a respective comment is confusing). When debugging, sometimes the tests passed for me. Also setting
opcache.log_verbosity_levelto 2 (instead of 0) and triggering an OPcache warning (e.g. by settingopcache.file_cacheto a non existing folder) makes the tests pass (unlessopcache.error_logis set). Looks like some stderr output is ignored, but I don't know why.