Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Enable result cache by default #3244

sebastianbergmann opened this issue Aug 6, 2018 · 4 comments

Enable result cache by default #3244

sebastianbergmann opened this issue Aug 6, 2018 · 4 comments


Copy link

@sebastianbergmann sebastianbergmann commented Aug 6, 2018

No description provided.

Copy link

@keradus keradus commented Sep 8, 2018

shall we also change order execution to depends,defects ?
the thing is, without that, cache file would be created, but not used, thus no benefits of creating it

Copy link
Owner Author

@sebastianbergmann sebastianbergmann commented Sep 8, 2018

Makes sense.

sebastianbergmann added a commit that referenced this issue Nov 19, 2018
Copy link
Owner Author

@sebastianbergmann sebastianbergmann commented Nov 19, 2018

@epdenouden I started to work on this in 36ed9fe.

One thing I noticed that if I run PHPUnit's own test suite with --do-not-cache-result then a cache file will still be written. This does not come from PHPUnit's own test suite itself but from one of the test suites used by it. Without --do-not-cache-result this cache file will be overwritten at the end by the cache file for PHPUnit's own test suite.

We probably have to disable the cache for all test suites executed by PHPUnit's own test suite.

Copy link

@epdenouden epdenouden commented Nov 19, 2018

@sebastianbergmann Yes, unfortunately that is a known issue with (some of?) the PHPT tests. I have never looked that up in detail, however I am aware of it. The saving grace for PHPUnit's own test suite is that it overwrites the other caches at the end.

I think at some point there was a development version that looked at the PHPUNIT_TESTSUITE constant being defined. Complicating factors I found but never fully explored:

  • the working directory of some tests results in caches being littered in subdirectories
  • caches in the working directory being left lying around when I CTRL-C the run

In newer tests I actively work around the issue by explicitly copying the cache to a temporary file somewhere else and deleting it afterwards. This works really well; example:

$tmpResultCache = tempnam(sys_get_temp_dir(), __FILE__);
file_put_contents($tmpResultCache, file_get_contents(__DIR__ . '/../../../../_files/DataproviderExecutionOrderTest_result_cache.txt'));
$_SERVER['argv'][1] = '--no-configuration';
$_SERVER['argv'][2] = '--order-by=defects';
$_SERVER['argv'][3] = '--debug';
$_SERVER['argv'][4] = '--cache-result';
$_SERVER['argv'][5] = '--cache-result-file=' . $tmpResultCache;
$_SERVER['argv'][6] = \dirname(\dirname(\dirname(__DIR__))) . '/../_files/DataproviderExecutionOrderTest.php';
require __DIR__ . '/../../../../bootstrap.php';

I am not sure what the best solution is that works in all cases, honestly. Wish I had a better answer for you already :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants