Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Could not run it on windows. Log file C:\...\PT_61A9.tmp is empty. #306

Closed
Wes0617 opened this issue Feb 17, 2018 · 14 comments
Closed

Could not run it on windows. Log file C:\...\PT_61A9.tmp is empty. #306

Wes0617 opened this issue Feb 17, 2018 · 14 comments

Comments

@Wes0617
Copy link

Wes0617 commented Feb 17, 2018

Log file C:\Users\Wes\AppData\Local\Temp\PT_61A9.tmp is empty.

However, I changed \Runners\PHPUnit\Options::phpunit() to:

    protected static function phpunit(): string
    {
        $vendor = static::vendorDir();
        return $vendor . '/phpunit/phpunit/phpunit';
    }

.and worked like a charm (using phpdbg). Not sure what's that .bat file. I've never used it. I'm not sure if this report helps, but I'm willing to help determining the problem with some pointers.

Thank you in advance. The speed is really impressive...

@Wes0617
Copy link
Author

Wes0617 commented Feb 17, 2018

also tested with plain php, and xdebug.
again, not sure why that bat is there (phpunit's), since php on windows can run /vendor/phpunit/phpunit/phpunit just fine

[...]phpdbg.exe -qrr "[...]/vendor/brianium/paratest/bin/paratest" "[...]/tests" -p 16 -f -c "[...]phpunit.xml"
[...]php.exe "[...]/vendor/brianium/paratest/bin/paratest" "[...]/tests" -p 16 -f -c "[...]phpunit.xml"

these work for me - with and without coverage

@Wes0617
Copy link
Author

Wes0617 commented Feb 28, 2018

Actually, the above works only for phpdbg. I'm sure I got it working with xdebug, but that doesn't seem to be the correct way

@Wes0617
Copy link
Author

Wes0617 commented Aug 11, 2018

any news on this?

@pana1990
Copy link

i have the same issue :(

@bhoehl
Copy link

bhoehl commented Sep 20, 2018

I have had the same issue and debugged it.
It has to do with environment settings for the spawned process executed.
I my case it couldn´t simply find the php.exe anymore and there are other issues, too.
The fix for this is to modify the way processes are created in
src\ParaTest\Runners\PHPUnit\ExecutableTest.php line 181
function run($binary ...

  • $this->process = new Process($command);
  • $this->process->start(null, $environmentVariables);

This ensures, that the newly created process inherits all env settings from the parent.
After applying this, it worked smoothely for me.
@Netmosfera @pana1990
have a look and see if it works for you

@andreasschroth
Copy link
Member

Please check if the problem still occurs on master, it might be fixed by now.

@pana1990
Copy link

pana1990 commented Sep 25, 2018

@andreasschroth it is not working for me yet :(

@bhoehl
Copy link

bhoehl commented Sep 25, 2018

@andreasschroth
I can not confirm this, as I have to use version <= 2 ( phpunit 5 )
this version does not have these changes

@pana1990
Copy link

@bhoehl I am using :

SO : windows 7
phpunit: 7.2
paratest: dev-master

@andreasschroth
Copy link
Member

andreasschroth commented Sep 25, 2018

@bhoehl Thanks for your feedback, but you must use dev-master... Could you please create a PR with the changes you applied locally and wrote before that it works with you?

@pana1990 Okay, thanks for your feedback. Not good, thought this might be fixed with the merged PR. Did you apply the changes locally @bhoehl proposed a few comments before? Did it fix the problem?

@pana1990
Copy link

@andreasschroth yes i did apply but it is not working :(

@SerafimArts
Copy link

I have a same error for *nix environment: https://travis-ci.org/railt/railt/jobs/482650052 =(

@oneumyvakin
Copy link

I've the same issue on Alpine Linux 3.9 stock PHP 7.2 with paratest and phpdbg.

@Slamdunk
Copy link
Member

Hi, master introduced CI testing on Windows, and now crashes report the original command that generated the crash, so it should be easy to debug, or to report here a more specific issue.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

7 participants