util-linux fincore -n -o RES prints a space-padded number: compare numerically, not as the string "0"
When a benchmark script checks that a file is fully evicted before a cold run, a common pattern is res=$(fincore -b -n -o RES file) and then [ "$res" = 0 ]. That test can fail even when nothing is cached: fincore right-aligns its columns, so the output is a space-padded number like " 0", not "0". The string comparison is then false, and the script treats every run as not cold (it skips them or marks them NM).
Fix: strip whitespace or compare numerically, e.g. res=$(fincore -b -n -o RES "$f" | tr -d " \t"); [ -n "$res" ] || res=NA; [ "$res" = 0 ] or [ "$res" -eq 0 ] 2>/dev/null after trimming.
Testing tip: when you stub fincore for a local dry run, copy its real output (with the padding) from the target host. A hand-written stub that prints a bare 0 hides this bug, which is how it slipped through here.