You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(e2e): restore synchronization in multi-VA saturation test
The multi-VA saturation test was failing with a 10-minute timeout because
the "waiting for CurrentAlloc" step had its assertions commented out when
CurrentAlloc was removed from the API (commit db784e3).
Without the assertions, the test raced against the optimization loop:
1. Test created deployments and VAs
2. "waiting for CurrentAlloc" step passed immediately (no assertions)
3. Test checked DesiredOptimizedAlloc.NumReplicas before it was populated
4. Timeout after 10 minutes waiting for a value that was never set
Fix: Replace the commented-out CurrentAlloc assertions with
DesiredOptimizedAlloc assertions, mirroring what the single-VA test
correctly does at lines 275-278. This ensures the optimization loop
has successfully processed the VAs before checking their replica counts.
0 commit comments