unit test a single case

7 years ago by Sam Ding — view source

unread

Hi PHP developers,

I am new and try to porting php v7.2.1 on IBM s390x, after building and
run unit test "make test", there are
some failed cases. Is there any way I can run a single case and get the
result?
Further how to debug a php unit case code?

Thanks,

Sam Ding,
Linux on z Systems Open Source Ecosystem
IBM Toronto Lab,
email: samding@ca.ibm.com
phone: (905)413-2947

7 years ago by Nikita Popov — view source

unread

Hi PHP developers,

I am new and try to porting php v7.2.1 on IBM s390x, after building and
run unit test "make test", there are
some failed cases. Is there any way I can run a single case and get the
result?
Further how to debug a php unit case code?

You can use one of

make test TESTS=dir
sapi/cli/php run-tests.php -P dir

to run tests in a certain directory, or a specific test file.

The first step for debugging would be to look at the .out or .diff file for
the failing .phpt. There will also be a .php file, which can be used to run
the test file directly.

Nikita

7 years ago by mail@pmmaga.net — view source

unread

Hi PHP developers,

I am new and try to porting php v7.2.1 on IBM s390x, after building and
run unit test "make test", there are
some failed cases. Is there any way I can run a single case and get the
result?
Further how to debug a php unit case code?

You can use one of
make test TESTS=dir
sapi/cli/php run-tests.php -P dir
to run tests in a certain directory, or a specific test file.

The first step for debugging would be to look at the .out or .diff file for
the failing .phpt. There will also be a .php file, which can be used to run
the test file directly.

Nikita

To add to what Nikita said, there will also be a .sh file next to the
failing test that you can use to repeat that test only.

Regards,
Pedro

7 years ago by Christoph M. Becker — view source

unread

Further how to debug a php unit case code?

The first step for debugging would be to look at the .out or .diff file for
the failing .phpt. There will also be a .php file, which can be used to run
the test file directly.

--
Christoph M. Becker

7 years ago by Christoph M. Becker — view source

unread

I can run the test case individually now and compare the result between
s390x and x86_64 (both RHEL 7.2) on failed cases.
Found the different results between the two platforms, some are related to
function var_dump(), how can I debug php code or even the interpreter
code ?
what debugger is used?

If possible, use gdb. There's a .gdbinit[1] in the PHP source tree
which offers some helpful macros.

[1] https://github.com/php/php-src/blob/master/.gdbinit

--
Christoph M. Becker

7 years ago by Christoph M. Becker — view source

unread

"gdb" seems not support php code.

I run gdb like follows:

gdb ../sapi/cli/php

GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
Copyright (C) 2013 Free Software Foundation, Inc.
...
Reading symbols from /home/work/php/php-src/sapi/cli/php...done.
(gdb) b bug72300.php:5
No source file named bug72300.php.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (bug72300.php:5) pending.
(gdb) r
Starting program: /home/work/php/php-src/case/../sapi/cli/php
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

then gdb freezes at this point (/lib64/libthread_db.so.1).

How to set break point in php and then step by step go into C code?

As far as I know, this is not possible. You can, however, set a
breakpoint for a certain PHP function (just preprend zif_ to the PHP
function name; in this case do b zif_ignore_user_abort). To actually
start the debugging, do something like r ext/standard/tests/general_functions/bug72300.php.

Most likely, there are more elegant ways to do this, but I don't know them.

BTW: it seems that your latest mails didn't make it to the list (see
e.g. https://externals.io/message/101603) for whatever reason.

--
Christoph M. Becker