• exec/tests/listfiles/lib.

    From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Thu Nov 19 09:20:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/487d2e038fbeb29c7509ca02
    Modified Files:
    exec/tests/listfiles/lib.js
    Log Message:
    tests/listfiles/lib.js: load listfiles_lib.js by path for jsdoor

    jsdoor sets exec_dir to the cwd, so a bare load("listfiles_lib.js") never searches exec/load/ and the jsdoor-testsuite CI jobs failed on every
    platform. Load it relative to the test directory, as dns/records.js does.

    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Fri Nov 20 14:39:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/d16c168b9a53884ab2e99099
    Modified Files:
    exec/tests/listfiles/lib.js
    Log Message:
    tests/listfiles/lib.js: load attr_option.js first, for jsdoor

    Every jsdoor-testsuite job failed this test with "listfiles_lib.js line
    8 Error: can't open attr_option.js". jsdoor has no exec dir to resolve
    the library's bare require("attr_option.js") against. Loading the file
    by path first does not help on its own: jsdoor's JSOPTION_VAROBJFIX binds
    the loaded functions to the global object, while require() looks for the
    symbol only on the js.exec() scope the test runs in (#1372). So the test
    also puts attr_option on its own scope, and the library's require() finds
    it there.

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