Skip to content

fix: persist repeated profile test results - #10466

Open
Shubham-Padkonde wants to merge 1 commit into
2dust:masterfrom
Shubham-Padkonde:fix/profile-test-results-persistence
Open

Shubham-Padkonde wants to merge 1 commit into
2dust:masterfrom
Shubham-Padkonde:fix/profile-test-results-persistence

Conversation

@Shubham-Padkonde

Copy link
Copy Markdown

Fixes #10465.

A new profile is queued when it is created and again when its test result is set. Saving the same new ID twice makes the transactional insert fail with a duplicate primary key, rolling back all new rows and preventing existing results in that batch from being updated.

Deduplicate the drained IDs and save their current records with a transactional insert-or-replace. This also removes the database snapshot used to classify inserts versus updates, which could become stale when saves overlap. Add SQLite-backed regression tests for repeated results across several new profiles and for batches mixing new and existing profiles, including a subsequent update.

Validation:

  • Windows x64, .NET SDK 10.0.403: all 138 ServiceLib tests pass; no skips.
  • Linux validation: full ServiceLib suite passes. Both new regression tests fail with unchanged production files and pass with the fix.
  • Changed-file whitespace formatting and git diff --check pass. No live proxy or GUI testing performed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant