A decade-old Servo test set to “expire” in 2026 — and someone just noticed

The odd little time bomb

It has been reported that a test written for the Servo browser engine roughly ten years ago includes an explicit expiry date in 2026, and the discovery was shared on Mastodon by @jdm_. The post — picked up in Hacker News threads — points to a tiny, human moment hidden in a codebase: a test that was given a shelf life and a calendar deadline. Allegedly it was meant as a temporary check, but ten years later the clock is still ticking.

Why this makes engineers smirk (and groan)

Why does a date in a test matter? Because software likes to assume the present is permanent. A hard-coded expiration can flip a passing test to a failing one without any change to the product. It’s the little Y2K for your unit tests — annoying, avoidable, and somehow entertaining when it pops up in the wild. The emotional payoff is real: part schadenfreude, part reminder that the things we ship will outlive our intentions.

A tiny lesson with a big tail

This is more than a cute anecdote. It’s a nudge to write ephemeral things in a way that actually expires — feature flags, clear TODOs, automation to clean up timeboxed code — or better yet, avoid arbitrary dates in tests altogether. Code has a long memory. Ten years later, that forgotten expiry is doing what it always did: reminding maintainers that the past is still running in their CI. Who hasn’t been there?

Sources: mastodon.social, Hacker News