There are 2 ways to test this: 1) locally, installing and running the tool . I've uploaded the results of that , and it's easy to see that, now, login is happening and the rest of requests (view course, page, post...) are doing things (there are dbwrites). Without the patch, basically all requests were the same (login failed) and dbwrites values were always in [0, 1] range. Configure the tool in webserver_config.properties to use 'git://git.moodle.org/integration.git' as 'beforebranchrepository' and 'afterbranchrepository', and 'master' as 'beforebranch' and 'afterbranch'. 2) Applying for the change in HQ performance infrastructure. To do so: Disable the $CFG->disablelogintoken temporal fix. Relaunch a comparison from https://ci.moodle.org Verify results have sense, dbwrites are back. It doesn't matter if it's leading to a pass or a fail at the moment it's tested. Just that it's back to work.