After updating the node_test submodule to track Node.js 25.8.1 (#32705), the following compat tests are failing:

Buffer

• test-buffer-concat.js — new test case with different expected length
• test-buffer-write-fast.js — requires internal/buffer Node module
• test-buffer-pool-untransferable.js — buffer.transfer() not supported

SQLite

• test-sqlite-named-parameters.js — allowUnknownNamedParameters option not supported
• test-sqlite-statement-sync.js — readBigInts, returnArrays, allowBareNamedParameters options not supported
• test-sqlite-config.js — defensive mode default behavior differs

Child Process

• test-child-process-spawnsync-validation-errors.js — fixed: use validateNumber for maxBuffer, validateInt32 for uid/gid
• test-child-process-spawn-typeerror.js — fixed: use validateInt32 for uid/gid
• test-child-process-spawn-timeout-kill-signal.js — AbortSignal listener not registered when signal option is passed to spawn with timeout (listenerCount(signal, 'abort') returns 0)
• test-child-process-fork-timeout-kill-signal.js — same AbortSignal listener issue as above

Streams / Net

• test-stream-duplex.js — cannot use BYOB reader with non-byte stream
• test-net-autoselectfamily-attempt-timeout-default-value.js — timeout default value differs

Assertions / Util

• test-assert-deep.js — new deep equal cases for sets/maps with mixed keys
• test-util-parse-env.js — expects Object.create(null) prototype on result
• test-parse-args.mjs — CLI flags (-e, --eval, etc.) parsing subtests

Other

• test-v8-stats.js — v8 heap stats keys differ
• test-process-features.js — process.features keys differ
• test-worker-cpu-usage.js — cpuUsage argument validation differs
• test-debugger-preserve-breaks.js — Node debugger specific
• test-fs-glob.mjs — ENOTDIR handling differs