@laoneo Do we really have issues with opcache? I remember they were once solved in the filesystem library of the CMS, and after that we had no issues with it. After that, the CMS was changed to use the framework filesystem library and not the one from the CMS. However, the filesystem library is missing some of the changes from the CMS library. I have prepared a PR for that, see joomla-framework/filesystem#75 . It just needs some testing instructions. Maybe that could solve it?

This has nothing to do with the PHP filesystem code. To speed up the system tests, we write directly into the configuration.php file here. When we do an assertion afterwards, then it can be that still the old config from the opcache is loaded. That's why the SEF test here fails randomly, mostly on fast machines and works fine on slow ones.

Since this would break tests which require opcache testing I would suggest to disable opcache for this file:

add to the opcache.ini
opcache.blacklist_filename=/path/install/configure.php

Do we have any opcache tests? This disables it only for system tests.

if the issue is in opcache we wouldn't see it with the system tests if it's disabled like the reason you deactivate it, the tests, especially the system tests should be as near as possible as real setups right?

I have tested this item ✅ successfully on f5ab6db

I have tested this item ✅ successfully on f5ab6db

RTC

thanks