• exec/tests/mailbox/files.

    From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Sun Nov 22 01:09:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/14fe8ef4f36bad129ba05fdf
    Modified Files:
    exec/tests/mailbox/files.js
    Log Message:
    mailbox tests: wait for a lock to be stale by file_mutex()'s own measure

    files.js made a lock stale by waiting a fixed 2.1 seconds with a max_age
    of 1, and expected a conflict from a fresh lock under that same max_age. file_mutex() counts a lock's age as the clock minus its file's
    modification time, so on a file system with coarse or skewed file times
    either can flip: on the NetBSD CI runner, which builds on a share, a
    lock 2.1 seconds old was not taken over (job 1891084), and in another
    run an expected conflict did not happen (job 1888322).

    The conflict is now checked with a max_age of 30, and the stale cases
    wait (up to 30 seconds) until the clock minus the lock file's date is
    over max_age, the test file_mutex() applies, instead of for a fixed
    time. Dating the lock file back with file_utime() would be quicker, but
    it fails on a CIFS mount.

    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net