Release · S357-S357
The release check now measures the cache it claims to measure
After every release, an automated check reads the live service and confirms what matters. One of those checks reads the feedback page twice to confirm the second read is served from a warm cache. That cache is kept separately in each copy of the service. The check's two reads could reach different copies in different data centres, so it failed on each of the last four releases even though the cache was working, and each release then had to be re-checked by hand. The check now makes its reads over one connection, so they reach the same copy, and it records where each read was served. It still fails if the cache never serves a warm read. Nothing visitors see has changed.