Testing internal caches expiration for Memcache
ITEM test [1 b; 0 s]
Failed condition "these keys have infinite expiration (the 1738250904 number might differ on your install)" - given "0 s" is not like some great integer like "1738250904"

In D443#8969, @erik wrote:

Testing internal caches expiration for Memcache
ITEM site_serial:1766886194:1:master:last_cache_rebuild [68 b; 0 s]
Failed condition "these keys have infinite expiration (the 1738250904 number might differ on your install)" - given "0 s" is not like some great integer like "1738250904"

Done requested changes - returned fallback to FakeCacheHandler zero time parameterusage and comments.

Testing internal caches expiration for Memcache
ITEM site_serial:1766886194:1:master:last_cache_rebuild [68 b; 0 s]
Failed condition "these keys have infinite expiration (the 1738250904 number might differ on your install)" - given "0 s" is not like some great integer like "1738250904"

In D443#8964, @erik wrote:

Detected that after memcache restart, test setCache with $application->setCache('key_with_def_exp', 'v1');, is passed only when twice open index.php. First index.php opening does not set value.

Detected that after memcache restart, test setCache with $application->setCache('key_with_def_exp', 'v1');, is passed only when twice open index.php. First index.php opening does not set value.

Fixed ArgumentCountError exception on the System Configuration step during clean install on PHP 7.4.

Set infinite expiration for site serial key.

Renoved fallback logic, updated test plan.

1. write a test plan for:
   • memory cache testing
   • database cache testing
   • template cache testing (via cache_timeout tag parameter, m_Cache tag and similar stuff)
2. store site serial with infinite expiration, because otherwise, it's expiration after 1 month will invalidate the whole cache

1. attempts to extract code from the trace, that doesn't contain a file reference
2. code of the source file/line isn't shown (because it's outside of a trace)

Adding phrases.

Fixed outdated phrase translation.

Changed terminology

Need to:

• finalize the plan for dead lock testing
• may add test plan for reconnect testing

Tried test part 4. No messages in system log given. Maybe, because of START TRANSACTION SQL command. Transaction not committed, so no records created in DB.

Bugfix: logging retry attempts reset retry counter resulting in indefinite retry attempts.

In D439#8859, @erik wrote:

@alex trouble in part3 1 G - cant't get "detailed lock retry info is shown in the system log".

On processing line with "Step 4." comment, i have lock much more then 50 seconds. Practically, it never ends. In case, when lock continue, in other debug window go to step 5 - lock ends, but no system log record about this lock created.

In D439#8859, @erik wrote:

@alex trouble in part3 1 G - cant't get "detailed lock retry info is shown in the system log".

@alex trouble in part3 1 G - cant't get "detailed lock retry info is shown in the system log".

Send e-mail upon retry (for real).

Send e-mail upon retry.

Added an explanatory comments.