- Issue created by @alexpott
- First commit to issue fork.
- Merge request !7393Try warming the front page then clearing caches again. → (Closed) created by catch
- Status changed to Needs review
8 months ago 8:34pm 9 April 2024 - 🇬🇧United Kingdom catch
OK this subtly changes all the test assumptions but it specifically does get rid of those two queries so hopefully this will get consistent results on @alexpott's local too. I'm not able to run functional js tests locally at the moment because chromedriver keeps crashing all the time (and didn't figure out why), so excuse all the commits here.
Remove a couple of assertBetween() too since ideally we don't need to do that any more.
After doing all this, I realised adding an extra sleep() after the first request might have been enough... this is probably better than doing that.
- Status changed to Needs work
8 months ago 8:46pm 9 April 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
I'm getting an error with this
ArgumentCountError: Too few arguments to function Drupal\Core\ProxyClass\Lock\DatabaseLockBackend::wait(), 0 passed in /Volumes/dev/sites/drupal8alt.dev/core/modules/system/tests/modules/performance_test/src/PerformanceDataCollector.php on line 74 and at least 1 expected in Drupal\Core\ProxyClass\Lock\DatabaseLockBackend->wait() (line 113 of core/lib/Drupal/Core/ProxyClass/Lock/DatabaseLockBackend.php).
- Status changed to Needs review
8 months ago 9:59pm 9 April 2024 - 🇬🇧United Kingdom catch
As soon as I got this back to green, it ran into merge conflicts. But then I tried to fix chromedriver locally again and may have done so finally, (increased shm_size in docker for the chromedriver image) -hopefully back to green again.
The lock wait issue can only happen if two requests are trying to write performance data at the same time, which should no longer be happening when we're trying to actually collect data to assert on, but could be happening in the initial cold cache requests where we warm up.
Re-did the locking logic slightly so it at least shouldn't error.
- Status changed to Needs work
8 months ago 5:12pm 10 April 2024 The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Needs review
8 months ago 7:09pm 10 April 2024 - Status changed to Needs work
8 months ago 11:02am 16 April 2024 The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Needs review
8 months ago 11:45am 16 April 2024 - Status changed to RTBC
8 months ago 12:41pm 16 April 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
This works great and passes locally for me. Nice!
-
longwave →
committed 35b7c9f2 on 10.3.x
Issue #3439671 by catch, alexpott: StandardPerformanceTest::...
-
longwave →
committed 35b7c9f2 on 10.3.x
-
longwave →
committed 4d00efb6 on 11.x
Issue #3439671 by catch, alexpott: StandardPerformanceTest::...
-
longwave →
committed 4d00efb6 on 11.x
- Status changed to Fixed
8 months ago 3:07pm 16 April 2024 - 🇬🇧United Kingdom longwave UK
Automatically closed - issue fixed for 2 weeks with no activity.