tested, each test command, containing build_all.xml or build_custom.xml leads to config.php change where HMAC key containing variable ($_CONFIG['Misc']['SecurityHmacKey']) disappears, and then build failed due [InvalidArgumentException] "The HMAC key is empty."

Can't test because of different php version on VM.

No, build was not successful.

Partially tested, tests from part 4 like "confirm, by looking at the colorized output of the above command, that phpunit target was called" - failed. No PHPunit output generated.

Part 1 - microsoft do not support such links as 'file://' (security issue), so browser does not decode it properly. Result is like "file:///" in the FireFox browser. {F669820}And like 'about:blank#blocked' when trying follow this link in the Chrome browser.

All right, when debugger is off. When debugger os on - got about 20 "Trying to access array offset on value of type bool" notices

Not passed test plan part

Test by plan is passed, but, to have Groups section visible, with root user go to Configuration->Users-General section, press Save button - and got "Exception: Permission section not specified for prefix conf in w:\SVN\5.2.x\core\kernel\utility\event.php on line 439"

System log errors exists, but, seems, not related to the current patch. Equal errors count with patch and without patch.

Tested by using PHPStorm+XDebug with breakpoint in the SessionStorage::RemoveFromData method. Before patch applying SQL, that removes the priority_deleted session variable was executed. After patch applying SQL, that removes the priority_deleted session variable was not executed, because SessionSet property is set to false.

No words "mysqldump", "Warning" in the resulting files.

Last line from test result is: "Test 5 (correct custom cert failure): Failed"
Not match with defined in test plan "Test 5 (correct custom cert failure): Passed"

all right, test times:

All right in general, but

Time reports for all 8 tests

All works right, only test plan must be corrected.

Can't test with correct MySQL version, but visually code looks good and works good with current MySQL version.

In the chrome browser, after reload frame. window is not scrolled. In the firefox browser this auto-scrolling works good.

Not working as expected in test plan. No result_number key detected.

Can't test - local system has apache_request_headers function and test array looks good without patch.

After in-portal update, test plan works well only after patch applying.

Test plan works well also without applying this patch.

Written requested test plan

Failed test "Testing internal caches expiration for DB cache" in the part "all other keys have an expiration of 25 days (with a few seconds margin) relative to the time they're set".

Partially tested for Memcached. Failed test with $application->addCache('key_with_exp', 'v2', 3600);

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"

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"

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.

Renoved fallback logic, updated test plan.

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.

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.

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

Found difference from test plan expectation:
test Hour field validation: has error on 30-35 value

There is not simple filter by g.Name, but complex filter "((1) AND ( (g.Name) LIKE '%mem%'))", where part "(1) AND" is excessive. Maybe, this "(1) AND" should be removed from SQL request.

Tested with clean install only.

Math is incorrect.

Added code to avoid "Array to string conversion" notice. Added related test plan part.