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
{{ message }}
Repository navigation
Report failed performance scenarios separately from timings #112
scripts/Measure-InstallPerformance.ps1 records elapsed time even when a measured installation action fails. The console summary omits the recorded Error property, allowing partial work to look like a successful benchmark result.
Observed behavior
The action exception is caught and stored, but a normal result object is still appended to JSONL and displayed with DurationS. The -All measurements used for #100 stopped on font-file collisions yet appeared in the timing table.
Expected behavior
Failed scenarios are visibly reported as failures and are excluded from successful timing comparisons.
Reproduction
Run the harness with an action that throws, such as a known colliding -All installation.
Observe that a duration is written and displayed as though the scenario completed.
Inspect the JSONL manually to discover the hidden Error value.
Environment
PowerShell 7 on Windows. The behavior is platform-independent.
Activity