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.
CreditAttribution: phenaproxima at Acquia commented
I want to RTBC this, since it looks completely simple and straightforward to me, but I'm wondering about that SQLite failure. I know SQLite database locks are a known problem for us, but I'd feel better if someone in the know (looking at you, @xjm) could confirm that those are affecting HEAD from time to time.
I always, always queue only MySQL and Maria environments for testing random fails, because Postgres and SQLite are prone to DB problems. SQLite especially is prone to database locks, and that's what happened here: SQLSTATE[HY000]: General error: 5 database is locked.Does the database file exist?Does web server have permission to write to the database file?Does the web server have permission to write to the directory the database file should be created in?
So we can ignore that result. However, I'm going to queue a couple more jobs on MySQL environments to be safe.
CreditAttribution: phenaproxima at Acquia commented
Status:
Needs review
» Reviewed & tested by the community
I compared the patch in #14 to what was committed. They look identical to me, so I queued up a bunch more MySQL environments. If they come back green, and I'm guessing they will, I'd say this is RTBC.
Comments
Comment #2
bnjmnmComment #3
bnjmnm#2 👆 runs the test 1200 times
Comment #4
bnjmnmComment #5
phenaproximaI want to RTBC this, since it looks completely simple and straightforward to me, but I'm wondering about that SQLite failure. I know SQLite database locks are a known problem for us, but I'd feel better if someone in the know (looking at you, @xjm) could confirm that those are affecting HEAD from time to time.
Comment #6
xjmI always, always queue only MySQL and Maria environments for testing random fails, because Postgres and SQLite are prone to DB problems. SQLite especially is prone to database locks, and that's what happened here:
SQLSTATE[HY000]: General error: 5 database is locked.Does the database file exist?Does web server have permission to write to the database file?Does the web server have permission to write to the directory the database file should be created in?
So we can ignore that result. However, I'm going to queue a couple more jobs on MySQL environments to be safe.
Comment #7
phenaproximaOkay, then I'm kicking this to RTBC on the assumption that the MySQL jobs will pass.
Comment #8
phenaproximaOn the other hand, looks like a reroll of #2 is necessary...
Comment #9
xjmI think it is RTBC for 10.1.x; just we will need a different backport patch for 9.4.x.
Comment #13
xjmCommitted to 10.1.x, 10.0.x, and 9.5.x, thanks!
NW for the 9.4.x backport.
Comment #14
ravi.shankar CreditAttribution: ravi.shankar at OpenSense Labs commentedAdded a patch for Drupal 9.4.x.
Comment #15
phenaproximaI compared the patch in #14 to what was committed. They look identical to me, so I queued up a bunch more MySQL environments. If they come back green, and I'm guessing they will, I'd say this is RTBC.
Comment #17
xjmCommitted to 9.4.x. Thanks!