* 'PHP-7.0' of git.php.net:/php-src:
Fixed bug #67707 IV not needed for ECB encryption mode, but it returns a warning
Fixed#73907 (nextSibling property not included in var_dump of DOMNode)
Fixed bug #61858 (DOMAttr debug info generates E_WARNING)
Fix glob-wrapper.phpt to not fail in Windows
Fix#73893: A hidden danger of death cycle in a function of gd
* 'PHP-7.1' of git.php.net:/php-src:
Fixed bug #67707 IV not needed for ECB encryption mode, but it returns a warning
Add support for "xfail" to phpt SKIPIF sections
Fixed#73907 (nextSibling property not included in var_dump of DOMNode)
Fixed bug #61858 (DOMAttr debug info generates E_WARNING)
Fix glob-wrapper.phpt to not fail in Windows
Set a session path for this test
Fix#73893: A hidden danger of death cycle in a function of gd
Missing %s
Ok, maybe Nikita is right. We should default this on.
Missed one. This needs gc as well
These tests expect gc to be enabled
* 'master' of git.php.net:/php-src:
Fixed bug #67707 IV not needed for ECB encryption mode, but it returns a warning
Add support for "xfail" to phpt SKIPIF sections
Fixed#73907 (nextSibling property not included in var_dump of DOMNode)
Fixed bug #61858 (DOMAttr debug info generates E_WARNING)
Fix glob-wrapper.phpt to not fail in Windows
Set a session path for this test
Set a session path for this test
Fix#73893: A hidden danger of death cycle in a function of gd
Missing %s
Missing %s
More missing gc inis
Ok, maybe Nikita is right. We should default this on.
Missed one. This needs gc as well
Missed one. This needs gc as well
These tests rely on gc being enabled
These tests expect gc to be enabled
If SKIPIF output starts with "xfail" instead of "skip", the test
will be marked as XFAIL with the following message. Example:
--TEST--
Test xfailif feature
--SKIPIF--
<?php
if (some_cond()) die('xfail Expected to fail!');
?>
--FILE--
...
It seems fair to remove this warning, given that:
* it is not documented in the official documentation
* the $specified property, which has a similar 'not implemented' status,
also does not trigger a warning
* it apparently hinders quite a lot of people during debugging, judging by
the number of votes on the bug
Xinchen Hui