24 lines
1.9 KiB
Plaintext
24 lines
1.9 KiB
Plaintext
✔ REQ-LIMIT-4 a role run at its limit stops at the end of its turn: RESULT and read land first, the claim is revoked by limit-check (135.950817ms)
|
||
✔ REQ-LIMIT-4 the stop also lands on state; a run with no stop ends without a limit (183.02595ms)
|
||
✔ REQ-LIMIT-4 fail closed: a mustStop throw or a malformed answer stops the run, naming the bus and the code (446.621104ms)
|
||
✔ REQ-LIMIT-4 a thread run at its limit is released with the reason, and its end record names the limit (114.707723ms)
|
||
✔ REQ-LIMIT-4 a broker with no limit checks configured never stops a run (71.318028ms)
|
||
✔ P5 broker preserves original plugin subject and derives internal run context from authenticated native caller (89.174131ms)
|
||
✔ P5 configured key quotas never use a supplied safe-looking ID when trusted metadata lookup is missing (41.80406ms)
|
||
✔ P5 internal context resolves exactly current or retained generation; wrong business, instance, run and owner refuse (0.436962ms)
|
||
✔ P5 usage plugin off by default, default poll is 15 seconds and configured polls skip early ticks (57.810472ms)
|
||
✔ P5 safe telemetry stores failures per key and proxy-labelled accounts; no client/upstream value enters store/log/view or quota records (54.180897ms)
|
||
✔ P5 unknown msk key goes only to value-free reconcile log and other businesses stay isolated (41.762914ms)
|
||
✔ P5 queue failure is safe, does not enforce and does not retry before poll deadline (43.65014ms)
|
||
✔ P5 retiring key keeps attribution and telemetry rows remain append-only across reader restart (50.005361ms)
|
||
✔ P5 malformed queue batch is atomic: no valid prefix, body or credential can reach store/log/view (42.308399ms)
|
||
✔ P5 concurrent ticks issue one bounded queue read and a closed collector never polls again (46.350571ms)
|
||
ℹ tests 15
|
||
ℹ suites 0
|
||
ℹ pass 15
|
||
ℹ fail 0
|
||
ℹ cancelled 0
|
||
ℹ skipped 0
|
||
ℹ todo 0
|
||
ℹ duration_ms 1674.306377
|