Chinesezjc 72241b9f06 test(code-runtime-python): correct the dual-limit CPU overrun assertion and use a hard limit >= 2 ...

The dual-limit CPU test used ulimit -t 1 (hard == 1), which the _clamped
soft-lowering guard (hard >= 2) intentionally does not lower, and trapped
SIGXCPU (which defeats the fix). Use ulimit -t 2 (hard == 2, so the soft is
lowered to 1) and leave SIGXCPU unhandled; the run then classifies as a timeout.
The message is the CPU-time-exhausted diagnostic, not the literal 'SIGXCPU'.

2026-08-31 14:33:31 +08:00

..

boot-write-failure.spec.ts

fix(code-runtime-python): seal stray fragments, flush by serialized cost, charge lone surrogates fully

2026-08-31 14:22:37 +08:00

protocol-mirror.e2e.ts

docs(code-runtime-python): name the roster aliases by subset direction, align metering prose

2026-08-07 15:37:19 +08:00

protocol.spec.ts

docs(code-runtime-python): trim metering prose and cover encodeJsonPlain depth

2026-08-07 13:27:54 +08:00

residual-detach.spec.ts

docs(code-runtime-python): sync README with the shipped backend

2026-08-31 14:20:00 +08:00

runtime.spec.ts

test(code-runtime-python): correct the dual-limit CPU overrun assertion and use a hard limit >= 2

2026-08-31 14:33:31 +08:00