--verbose=<int> options fails with fatal error

[maks-rafalko]

Q	A
ParaTest version	6.3.1
PHPUnit version	9.5.9
PHP version	8.0.10

Summary

--verbose=<int>

option does not work, while it mentioned on README https://github.com/paratestphp/paratest#troubleshooting

Current behavior

--verbose=1 fails with the following exception:

In ArgvInput.php line 228:
                                                          
  [Symfony\Component\Console\Exception\RuntimeException]  
  The "--verbose" option does not accept a value.         
                                                          

Exception trace:
  at /srv/api/vendor/symfony/console/Input/ArgvInput.php:228
 Symfony\Component\Console\Input\ArgvInput->addLongOption() at /srv/api/vendor/symfony/console/Input/ArgvInput.php:140
 Symfony\Component\Console\Input\ArgvInput->parseLongOption() at /srv/api/vendor/symfony/console/Input/ArgvInput.php:76
 Symfony\Component\Console\Input\ArgvInput->parse() at /srv/api/vendor/symfony/console/Input/Input.php:55
 Symfony\Component\Console\Input\Input->bind() at /srv/api/vendor/symfony/console/Command/Command.php:258
 Symfony\Component\Console\Command\Command->run() at /srv/api/vendor/symfony/console/Application.php:978
 Symfony\Component\Console\Application->doRunCommand() at /srv/api/vendor/symfony/console/Application.php:295
 Symfony\Component\Console\Application->doRun() at /srv/api/vendor/symfony/console/Application.php:167
 Symfony\Component\Console\Application->run() at /srv/api/vendor/brianium/paratest/bin/paratest:37

Passing --verbose works, but does not do anything.

What I would like to do is to understand how coverage are combined and merged, because paratest definitely breaks coverage (will report under separate issue).

[Slamdunk]

because paratest definitely breaks coverage

Take a look at:

1. Code coverage merge doesn't seem to take @covers into account #400
2. Collect code coverage for test annotated with @coversNothing sebastianbergmann/php-code-coverage#726

[maks-rafalko]

@Slamdunk any recommendations on how to debug the issues with "random" coverage on each run for the same commit?

btw, I've checked #400 - it works correctly, so the issue reported there is not reproduced anymore. But on my project - we have different jumps related to code coverage when paratest is used

#1

#2

#3

[Slamdunk]

I have this issue from the beginning of my usage of ParaTest, and never been able to properly debug it ever since, any help is welcome

[maks-rafalko]

But from paratest point of view, is there any commands/options useful for debugging?

I hoped it would be --verbose, but it doesn't work :)

The only one way I see is by using debugger

[Slamdunk]

I have to say I'm a bit ashamed, I've never put much effort in providing better debugging tools for inspecting ParaTest issues.
What I can say is:

1. -vv is the only meaningful verbosity, it prints the underlying command ParaTest executes; what it doesn't tell you is, in the WrapperRunner context, the n-th process the command is running on, that would be a bit more helpful
2. Right now there is no way to have deterministic runs: the first process that returns free receives the next test. That's a pita for debugging purposes, because we can't have always #1 or #2 or #3 output, but just a random one out of the three base on how each test lasted

So, in order to fix this I'd say we'd first need a deterministic Runner to properly debug the exact same run multiple times.

[github-actions]

This issue has gone two months without activity. In another two weeks, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Backlog or In Progress, I will leave it alone ... forever!

[Slamdunk]

Hi, #679 aligned --verbose behavior to PHPUnit's one, and added --debug like PHPUnit's one.