Skip to content

Correct skipped-simulation accounting by counting DB-hit results as skipped - #112

Merged
APN-Pucky merged 5 commits into
masterfrom
copilot/fix-skipped-simulation-counter
May 25, 2026
Merged

APN-Pucky merged 5 commits into
masterfrom
copilot/fix-skipped-simulation-counter

Conversation

Copilot AI commented May 22, 2026 •

Copy link
Copy Markdown

Skipped simulation accounting is now aligned so that when a previously seen deck is served from DB, those iterations are counted as skipped simulations in the reported (<simulated> + <skipped>) totals.

  • Skipped-counter semantics

    • Restored direct skipped accounting in algorithms.cpp so DB-hit reused results contribute to skipped_simulations.
    • Removed the helper that excluded DB-only coverage from skipped counts.
  • Regression coverage

    • Added/updated focused DB regression coverage in sim_test.cpp:
      • warm DB with a climb run using no-db-load
      • assert warmup skipped simulations are zero (Z == 0) for the no-DB-load warmup run
      • rerun with DB load enabled using beam
      • parse Evaluated X decks (Y + Z simulations). and assert cached run skipped count is non-zero (Z > 0), confirming DB-hit results are counted as skipped.
  • Snippet (core behavior)

    if (!emplace_rv.second)
    {
        skipped_simulations += prev_results.second;
    }

[!WARNING]

Copilot AI changed the title [WIP] Fix counter of skipped simulations when database is hit Correct skipped-simulation accounting for DB-served evaluations May 22, 2026
Copilot AI requested a review from APN-Pucky May 22, 2026 22:00
@APN-Pucky

Copy link
Copy Markdown
Owner

@copilot if the database is hit the results taken from the database should be counted as skipped, right?

Copilot AI commented May 25, 2026 •

Copy link
Copy Markdown
Author

@copilot if the database is hit the results taken from the database should be counted as skipped, right?

Yes — agreed. I updated it so DB-hit results are counted as skipped simulations again (commit 330a16f).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • dl.google.com
    • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI changed the title Correct skipped-simulation accounting for DB-served evaluations Correct skipped-simulation accounting by counting DB-hit results as skipped May 25, 2026
@APN-Pucky

Copy link
Copy Markdown
Owner

@copilot also make sure that warmup skipped is zero asserted.

Copilot AI commented May 25, 2026 •

Copy link
Copy Markdown
Author

@copilot also make sure that warmup skipped is zero asserted.

Done in 5ff5f04: the test now explicitly asserts warmup skipped is zero (no-db-load warmup) before checking cached skipped behavior.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • dl.google.com
    • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

@APN-Pucky
APN-Pucky marked this pull request as ready for review May 25, 2026 11:25
@APN-Pucky
APN-Pucky merged commit e56bf8a into master May 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Counter of skipped simulations might need change when db is hit

2 participants