summaryrefslogtreecommitdiff
path: root/sapi/cli/tests
Commit message (Collapse)AuthorAgeFilesLines
* Fix borked SKIPIFsFabien Villepinte2019-09-302-4/+10
|
* Fix pipe detection and stream position handlingNikita Popov2019-09-051-0/+31
| | | | | | | | | | There are two related changes here: 1. Also check for S_ISCHR/FILE_TYPE_CHAR when checking for pipes, so that we detect ttys as well, which are also not seekable. 2. Always set position=-1 (i.e. ftell will return false) when a pipe is detected. Previously position=0 was sometimes used, depending on whether we're on Windows/Linux and whether the FD or FILE codepath was used.
* Avoid accessing undefined index in CLI server testNikita Popov2019-08-301-3/+3
|
* Switch to using shell-less proc_open() in various server testsNikita Popov2019-07-112-30/+17
|
* Set up asan+ubsan scheduled build on azureNikita Popov2019-06-281-0/+4
| | | | | | | | | Also adds an --asan flag to run-tests.php to setup all the necessary environment variables. Some tests are marked as skipped because they are incompatible with asan or too slow. I'm basing this on the DEBUG_ZTS build, which seems to give us the most mileage.
* Split test caseChristoph M. Becker2019-06-244-72/+84
| | | | | | This test is failing on AppVeyor almost all of the time, so splitting it seems appropriate. This also allows us to rid php_cli_server_stop() which was only used by this test case.
* refactor a little more to add some more useful error messages and raise the ↵Joe Watkins2019-06-191-15/+46
| | | | limits on waiting for slow machines
* Separate check for process creation and ability to accept connectionsJoe Watkins2019-06-191-14/+13
|
* fix mac tests on azureJoe Watkins2019-06-143-2/+10
|
* Don't involve output check in the testAnatol Belski2019-06-011-5/+15
|
* Fix ZTS issue regarding new Windows CTRL handling APIChristoph M. Becker2019-06-011-2/+0
| | | | | | | | | | | | | | php_win32_signal_system_ctrl_handler() is called from a kernel thread, so the former initialization of `vm_interrupt_flag` has no effect, since it is defined as thread-local. This is, however, not necessary, since the CTRL signal handling is supposed to work only for the main thread anyway. We therefore change `vm_interrupt_flag` and the related variables to true globals. This also allows us to unmark the respective test case as XFAIL. Furthermore, `vm_interrupt_flag` is declared as `zend_bool *`, so we better treat it such.
* Mark sapi_windows_set_ctrl_handler.phpt as XFAILNikita Popov2019-05-311-0/+2
|
* Update cli reflection testNikita Popov2019-05-291-2/+4
|
* Remove two zpp tests in sapi/cli/testsNikita Popov2019-05-292-35/+0
| | | | These fail on master -- apparently we're not running these tests...
* Replace dirname(__FILE__) by __DIR__ in testsFabien Villepinte2019-03-1511-14/+14
|
* Implement fine-grained conflict handlingNikita Popov2019-02-201-0/+1
| | | | | | Tests can specify conflict keys, either in --CONFLICTS-- or a per-directory CONFLICTS file. Non-conflicting tests may be run in parallel.
* Implement FR #77377 handle CTRL+C in WindowsAnatol Belski2019-02-081-0/+75
|
* Update and fix remaining year ranges (2019)Peter Kokot2019-02-081-2/+2
| | | | | | This patch follows previous license year ranges updates. With new approach source code files now have simplified headers with license information without year ranges.
* Revert removal of private __clone() methodsNikita Popov2019-01-141-4/+7
| | | | | | | | | | | | I thought these were redundant, because we already NULL out the clone_obj object handler. However, it turns out that reflection is using private __clone() to determine clonability (isCloneable) for the case where we only have a class, rather than an object. As such, removing these methods would be a BC break. This reverts commit e7131a4e9fa0acf8fc1e486b49851e71859ef5b8. This reverts commit 55bd88ce0d1bf461546d5d0b40920491d566ed48.
* Remove redundant Exception::__clone() methodNikita Popov2018-11-261-7/+4
| | | | | | Exceptions already prohibit cloning by setting clone_obj to NULL (which is integrated with reflection). No need to additionally define a dummy __clone() method.
* Merge branch 'PHP-7.3'Anatol Belski2018-11-161-0/+42
|\ | | | | | | | | * PHP-7.3: Fixed bug #77111 php-win.exe corrupts unicode symbols from cli parameters
| * Merge branch 'PHP-7.2' into PHP-7.3Anatol Belski2018-11-161-0/+42
| |\ | | | | | | | | | | | | * PHP-7.2: Fixed bug #77111 php-win.exe corrupts unicode symbols from cli parameters
| | * Fixed bug #77111 php-win.exe corrupts unicode symbols from cli parametersAnatol Belski2018-11-161-0/+42
| | | | | | | | | | | | | | | | | | The binary can be of course used on console, for whatever reasons, so UNICODE API should be used in that case. That might however not work as expected, if the binary is used for a service.
| | * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-156-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| | * Trim trailing whitespace in *.phptPeter Kokot2018-10-1450-101/+101
| | |
| | * Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Merge branch 'PHP-7.3'Rasmus Lerdorf2018-10-311-1/+0
|\ \ \ | |/ / | | | | | | | | | * PHP-7.3: Fix stray newline that caused this test to fail
| * | Fix stray newline that caused this test to failRasmus Lerdorf2018-10-311-1/+0
| | |
| * | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-156-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Trim trailing whitespace in *.phptPeter Kokot2018-10-1449-94/+94
| | |
| * | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-156-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Trim trailing whitespace in *.phptPeter Kokot2018-10-146-6/+6
| | |
* | | Trim trailing whitespace in testsGabriel Caruso2018-10-1449-86/+86
| | |
* | | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Make more tests run on LinuxGabriel Caruso2018-08-283-14/+8
|/ /
* | Merge branch 'PHP-7.2'Anatol Belski2018-05-181-6/+12
|\ \ | |/ | | | | | | * PHP-7.2: Fix cli server test fails after recent AppVeyor image update
| * Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-05-181-6/+12
| |\ | | | | | | | | | | | | * PHP-7.1: Fix cli server test fails after recent AppVeyor image update
| | * Fix cli server test fails after recent AppVeyor image updateAnatol Belski2018-05-181-6/+12
| | |
* | | Use EXPECT instead of EXPECTF when possibleGabriel Caruso2018-02-2027-27/+27
| | | | | | | | | | | | EXPECTF logic in run-tests.php is considerable, so let's avoid it.
* | | Use bool instead of boolean while throwing a type errorGabriel Caruso2018-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PHP requires boolean typehints to be written "bool" and disallows "boolean" as an alias. This changes the error messages to match the actual type name and avoids confusing messages like "must be of type boolean, boolean given". This a followup to ce1d69a1f6dcf15d43029301059c25e5bc09a577, which implements the same change for integer->int.
* | | Use int instead of integer in type errorsGabriel Caruso2018-02-041-17/+17
| | | | | | | | | | | | | | | | | | | | | PHP requires integer typehints to be written "int" and does not allow "integer" as an alias. This changes type error messages to match the actual type name and avoids confusing messages like "must be of the type integer, integer given".
* | | Remove superfluous SKIPIF sections in more testsGabriel Caruso2018-02-043-15/+9
| | |
* | | Added PCRE_JIT_SUPPORT flagXinchen Hui2017-11-141-1/+5
| | |
* | | Patch core for PCRE2 supportAnatol Belski2017-11-131-1/+3
| | | | | | | | | | | | RFC https://wiki.php.net/rfc/pcre2-migration
* | | Merge branch 'PHP-7.2'Anatol Belski2017-09-181-13/+1
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Fix the version check causing the test fail
| * | Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2017-09-181-13/+1
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Fix the version check causing the test fail
| | * Merge branch 'PHP-7.0' into PHP-7.1Anatol Belski2017-09-181-13/+1
| | |\ | | | | | | | | | | | | | | | | * PHP-7.0: Fix the version check causing the test fail
| | | * Fix the version check causing the test failAnatol Belski2017-09-181-13/+1
| | | |
* | | | Fix test portabilityAnatol Belski2017-09-061-11/+11
| | | |