2 Test failures on RHEL-7 without compression (zlib is outdated there)
TEST 617/793 [tests/profiler/bug02001-no-zlib-compression.phpt]
========DIFF========
002+ [3225030] [Config] INFO: Control socket set up succesfully: '@xdebug-ctrl.3225030'
[%d] [Config] WARN: Cannot create the compressed file '%s.out.gz', because support for zlib has not been compiled in. Falling back to '%s.out'
%A
005+ creator: xdebug 3.3.0 (PHP 8.0.30)
006+ cmd: /builddir/build/BUILD/php-pecl-xdebug3-3.3.0/src/tests/profiler/bug02001-no-zlib-compression.php
007+ part: 1
008+ positions: line
009+
010+ events: Time_(10ns) Memory_(bytes)
========DONE========
FAIL Test for bug #2001: no zlib, use_compression=1 [tests/profiler/bug02001-no-zlib-compression.phpt]
TEST 743/793 [tests/tracing/start_no_zlib_compression.phpt]
========DIFF========
--
%w%f %w%d
TRACE END [%d-%d-%d %d:%d:%d.%d]
010+ [3225290] [Config] INFO: Control socket set up succesfully: '@xdebug-ctrl.3225290'
[%d] [Config] WARN: Cannot create the compressed file '%s.xt.gz', because support for zlib has not been compiled in. Falling back to '%s.xt'
========DONE========
FAIL Compression: no zlib, use_compression=1 [tests/tracing/start_no_zlib_compression.phpt]
2 Test failures on Fedora Rawhide (other versions are OK)
https://koji.fedoraproject.org/koji/taskinfo?taskID=109759478
TEST 239/791 [tests/debugger/bug01388-08.phpt]
========DIFF========
--
-> run -i 6
<?xml version="1.0" encoding="iso-8859-1"?>
026+ <notify xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" name="breakpoint_resolved"><breakpoint type="line" resolved="resolved" filename="file://bug01388-08b.inc" lineno="9" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0002"></breakpoint></notify>
026- <notify xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" name="breakpoint_resolved"><breakpoint type="line" resolved="resolved" filename="file://bug01388-08b.inc" lineno="2" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0001"></breakpoint></notify>
<?xml version="1.0" encoding="iso-8859-1"?>
029+ <notify xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" name="breakpoint_resolved"><breakpoint type="line" resolved="resolved" filename="file://bug01388-08b.inc" lineno="2" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0001"></breakpoint></notify>
029- <notify xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" name="breakpoint_resolved"><breakpoint type="line" resolved="resolved" filename="file://bug01388-08b.inc" lineno="9" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0002"></breakpoint></notify>
<?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="run" transaction_id="6" status="break" reason="ok"><xdebug:message filename="file://bug01388-08b.inc" lineno="2"></xdebug:message></response>
--
========DONE========
TEST 291/791 [tests/debugger/bug02006-001.phpt]
========DIFF========
--
-> breakpoint_list -i 3
<?xml version="1.0" encoding="iso-8859-1"?>
014+ <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="breakpoint_list" transaction_id="3"><breakpoint type="call" function="b" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0002"></breakpoint><breakpoint type="call" function="a" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0001"></breakpoint></response>
014- <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="breakpoint_list" transaction_id="3"><breakpoint type="call" function="a" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0001"></breakpoint><breakpoint type="call" function="b" state="enabled" hit_count="0" hit_value="0" id="{{PID}}0002"></breakpoint></response>
-> breakpoint_remove -i 4 -d %d0001
<?xml version="1.0" encoding="iso-8859-1"?>
--
========DONE========
FAIL Test for bug #2006: Removing second call breakpoint with same function name crashes [tests/debugger/bug02006-001.phpt]
This is quite strange, could be related to some changes in build chain. | 