Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This is not a joke :)
Taking EntityFieldTest as an example, which apparently generates 38 passwords, takes more than 3 seconds in that function, other tests might not be as much but still a few.
The upcoming patch sets the log count variable for DUBT tests to 1, which results in the password hash generation taking 14msec instead.
Comment | File | Size | Author |
---|---|---|---|
#1 | password-log-count-2154961-1.patch | 811 bytes | Berdir |
Comments
Comment #1
BerdirComment #2
alexpottCan not see any disadvantages to doing this! Nice find :)
Comment #3
xjm1: password-log-count-2154961-1.patch queued for re-testing.
Comment #4
catchWhy not do this for web tests too?
Comment #5
BerdirThought about it but we currently don't have the possibility to do that.
I know there's an issue to add a testing service provider in an issue, but I can't remember which one right now, that would help.
Comment #6
catchFair enough. Committed/pushed to 8.x, thanks!
Comment #7
pwolanin CreditAttribution: pwolanin commentedIt roughly looks like inside DrupalKernel::initializeContainer() you could make some tweaks if the environment is "testing"?
Comment #8
pwolanin CreditAttribution: pwolanin commentedopened a new issue: #2165549: Reduce number of password hashing iterations in all tests to improve test performance