Of course, if you try the test in CLI, make sure to enable the opcache even in the cli:

php -d opcache.enable=1 -d opcache.enable_cli=1 test.php

Don't think this is a bug. opcache_invalidate()/opcache_reset() isn't called after the updated file is written to disk, so the opcache just doesn't know the file on disk has changed. The timestamps are only validated every 2 sec. by default, but only once per request.

See http://www.php.net/manual/en/opcache.configuration.php#ini.opcache.revalidate-freq and Speed Tuning @ https://github.com/zendtech/ZendOptimizerPlus

Maybe you are right, but this is a huge inconsistency, difference and compatibility break from APC, which was the default opcache in 5.4.

(Just tested with Opcache disabled and php -d extension=apc.so -d apc.enabled=1 -d apc.enable_cli=1 test.php)

Why is this a problem? This is the analog of apc.stat.  The only material difference here is that apc.stat=1 by default.  OPcache defaults are different, but this is clearly documented.  If you want OPcache always to revalidate scripts, then set opcache.revalidate_freq=0 as per README and documentation.

Well, just tested with

php -d opcache.enable=1 -d opcache.enable_cli=1 -d opcache.revalidate_freq=0 test.php

and the result is the same, int(1), so the issue is still alive.

-d opcache.revalidate_freq=0  will result in OPcache checking for updates on every request.

You change the content DURING the request, so OPcache won't check for updates during the request.

http://www.php.net/manual/en/apc.configuration.php#ini.apc.stat
"This defaults to on, forcing APC to stat (check) the script on each request to determine if it has been modified."

Reads the same as opcache.revalidate. Because of your bugreport I guess apc.stat=1 checks the file on disk for modification on every include/require. And not just once per request, which is quite different..

I have the same problem. If I change a file nothing happens. For development purposes I tried to disable OPCache, but that doesn't work as well. Only way I can fix this problem is by rebooting the system.

Details:
 Ubuntu Server 13.10 x64
 PHP 5.5.3
 Apache 2.4.6

APC made a hack to prevent caching of just updated files.
This makes the test passed.

With opcache.revalidate_freq=0 OPCache checks file modification time on each include(), but the test script most probably makes two writes in a single second.
So file modification times are the same. If you insert sleep(1) between inclue()s, it works as expected.

To workaround the problem you may add the file into blacklist or use opcache_invalidate():

if (function_exists("opcache_invalidate")) opcache_invalidate($file, true);

We may also hack OPCache similar to APC, but I'm not sure it's the right way.

Hi dmitry, almost all http requests last less than 1 second, and it's common to write this cache algorithm:

$var = include $cachefile;
if (must_renew($var)) {
    file_put_contents($cachefile, renew($var));
    $var = include $cachefile;
}
use($var);

So I think APC did a workaround just because of that common usage.
Your workaround works, but it' pretty bad to couple a general algorithm to teh cache subsystem.

This is still a problem, because include is sometimes used for non-source code files that can be changed under 1 second during runtime.

https://github.com/tedivm/Stash/pull/135#issuecomment-38640785