- Issue created by @catch
- 🇬🇧United Kingdom catch
🐛 Flood database backend ::isAllowed() should call ::ensureTableExists() Fixed likely caused this. The exceptions in the lazy creation table logic mean that the original query that triggered the exception (like FloodInterface::isAllowed()) don't get recorded, so that issue removes less observable queries than it does actual queries that run during tests.
- Merge request !5932Increase query assertion range to avoid random test failures. → (Closed) created by catch
- Status changed to Needs review
11 months ago 7:22am 22 December 2023 - Status changed to RTBC
11 months ago 9:39am 22 December 2023 - Status changed to Closed: duplicate
11 months ago 9:57pm 22 December 2023 - 🇬🇧United Kingdom catch
This ended up being included in 📌 Only clear flood attempts when necessary during user login RTBC which I wasn't expecting to land first.
- Status changed to Needs review
11 months ago 9:09am 23 December 2023 - 🇬🇧United Kingdom catch
No we do need to tweak it after all. https://git.drupalcode.org/project/drupal/-/jobs/529691
- Status changed to RTBC
11 months ago 2:03pm 23 December 2023 -
larowlan →
committed bdc1f78b on 11.x
Issue #3410450 by catch: Fix random performance test failures
-
larowlan →
committed bdc1f78b on 11.x
-
larowlan →
committed 51ebf197 on 10.2.x
Issue #3410450 by catch: Fix random performance test failures (cherry...
-
larowlan →
committed 51ebf197 on 10.2.x
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Committed to 11.x
Backported to 10.2.x because the related issues also were, so I assume the issue also exists there.
- Status changed to Fixed
11 months ago 10:12pm 27 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.