test(streaming): respect retained retirement barrier
Update the stale readiness fixture to preserve Slice E's cursor-budgeted Near retirement boundary before publishing the replacement Far base. The exact committed baseline deterministically failed because the test still assumed both transactions could cross the same frame. Co-authored-by: Codex <noreply@openai.com>
This commit is contained in:
parent
75b761e658
commit
3456dff038
1 changed files with 6 additions and 0 deletions
|
|
@ -394,6 +394,12 @@ public sealed class StreamingControllerReadinessTests
|
||||||
farBase,
|
farBase,
|
||||||
mesh));
|
mesh));
|
||||||
controller.Tick(0x12, 0x39);
|
controller.Tick(0x12, 0x39);
|
||||||
|
// Slice E retains retirement as a cursor-budgeted transaction. A
|
||||||
|
// generous frame can retire Near and resume Far immediately; a frame
|
||||||
|
// that exhausts its elapsed budget resumes on the next Tick. Pin the
|
||||||
|
// converged state rather than wall-clock-dependent frame count.
|
||||||
|
for (int i = 0; i < 4 && appliedBuilds.Count < 2; i++)
|
||||||
|
controller.Tick(0x12, 0x39);
|
||||||
|
|
||||||
Assert.Equal(1, ensureCalls);
|
Assert.Equal(1, ensureCalls);
|
||||||
Assert.DoesNotContain(geometryId, meshes.ReferenceCounts);
|
Assert.DoesNotContain(geometryId, meshes.ReferenceCounts);
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue