Files
orca/tests
Jinwoo-H 102df2754b test(browser): make the resident-cap spec assert recency, not creation order
CI on Linux caught a flaw in my own test. It assumed the pages created first
are the least recently used, but a page's reclaim clock restarts when its load
completes, and load completion does not have to follow creation order — under
Xvfb it did not, so a different page was resident than the spec named.

Touching two pages once up front had the same hole: a page finishing its load
after the touch overtakes it. The spec now keeps two pages genuinely in use
across the convergence poll, which is what its name claims and what makes the
most-recently-used set unambiguous. It asserts those two are the residents,
which proves recency is what decides — something creation order never showed.
2026-08-19 19:07:13 -04:00
..