- 🇬🇧United Kingdom catch
It looks like there's a couple of approaches here, using <= seems like a good plan though. Tagging for issue summary update.
- Status changed to Postponed: needs info
22 days ago 5:08am 27 March 2025 - 🇦🇺Australia mstrelan
Is this still relevant since 📌 Optimize last_write_timestamp writes in ChainedFastBackend Active ?
- 🇬🇧United Kingdom catch
I converted the test-only patch to an MR, it passes locally, maybe it will fail with 100 runs.
The
<
check is still in core and I don't think it would hurt at all to change that to<=
📌 Optimize last_write_timestamp writes in ChainedFastBackend Active means that when there is one cache write on a page, the two servers would have to be more out of sync for there to be a problem, but it's only 50ms which is will within NTP tolerance, so it only makes the problem less likely and doesn't eliminate it. I think therre might be an issue around to try to use something else (like a special cache tag) that doesn't rely on clock time.
- 🇬🇧United Kingdom catch
The test only job didn't fail, but reverting the fix causes the new test to fail - here's the failing job:
- 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
There are more tests that are failing on the last test run. All in ChainedFastBackend.
The change however makes sense and it has good test coverage.
- 🇬🇧United Kingdom catch
hmm the new test that fails is the one that's being added so something is still wrong here.