Skip to content

[DIAGNOSTIC ONLY] Compare exact method exclusion with correlated SQL-pool retry - #12499

Draft
Prangshuman Das (t-prda) wants to merge 1 commit into
features/646383-sql-api-warmup-experimentfrom
features/646383-sql-api-two-arm-experiment
Draft

Prangshuman Das (t-prda) wants to merge 1 commit into
features/646383-sql-api-warmup-experimentfrom
features/646383-sql-api-two-arm-experiment

Conversation

@t-prda

@t-prda Prangshuman Das (t-prda) commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Diagnostic only — DO NOT MERGE

AB#646383

User-authorized two-arm CI experiment, stacked on draft warmup PR #12471 at immutable baseline 8a7ebc7.

  • A: add only CU148318 CapabilitiesProjectsEnabledViaAPI to the existing runner disabled-test configuration. Do not drop the codeunit.
  • B: preserve all baseline-enabled tests; permit at most one whole-CU retry only for complete failed JUnit cases correlated to NST event701 ClientSessionId + RootException NullReferenceException + AcquireSqlConnectionFromPool and the observed metadata/OData frames during that dispatch.
  • Every retry follows a pristine restore and fresh companies probe. BCH ReRun is removed so all CU methods run. No generic HTTP500/NRE, warmup, scheduler, job, or CI retries.
  • One manual matrix: 2 arms x W1/DE x 5 trials = 20 disposable containers, maximum parallelism 5 globally, 120 minutes per cell. Exact head excluded from automatic full PR Initialization. No automatic reruns.
  • Both arms use one-attempt companies probes (20s connect/read), original first-app warmup, and nested artifact collection. Same packages, source, runtime, cohort, auth, and SQL database names.
  • Preserve original and retry snapshots/outcomes and correlated events separately; only complete validated recovery replaces the CU in final merged results. Actual A/B target skip state is checked from JUnit.

Immutable provenance

AL/source: c4953dc; compiled package run37372848860; W1 artifacts11374170356/11374145359; DE11376415128/11375174896. All four are currently nonexpired and match their pinned digests/source run.

NST30.0.55665.0; application30.0.55683.0; BCH6.1.19-preview2811389; AL-Go91b96c2b294be6f823277dafe6f03350abfb9d23; original pinned generic-image digest. No source/package/auth changes.

Strict ordered21-CU cohort retained, including148315,148318,148343. Baseline complete W1:253 cases (234pass,19skip); A expects one additional skip, B no additional skips. Runner loss or incomplete evidence is inconclusive; nonreproduction is not proof of a production fix.

Validation

212 focused Pester tests passed (pilot, scheduler, evidence classifier and treatment isolation), zero failed containers. PSScriptAnalyzer: no new warning/error compared with baseline (four unchanged pre-existing warnings). git diff --check and pinned-source diff checks passed. No local NST or SQL experiments.

Full protocol: build/scripts/SqlResetPilot/README.md.

Launched

Manual run: https://github.com/microsoft/BCApps/actions/runs/37629351966

Pinned experiment commit: fbd7ec4. Dispatch event, run attempt1; all20 A/B-W1/DE-trial cells materialized, with cells running and queued. Automatic PR Initialization is verified SKIPPED in run37629353298. No replacement or rerun was submitted.

AB#646383. Diagnostic only: twenty manual W1/DE trials, maximum five parallel; immutable source and runtime pins.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 3952f078-a881-4da8-ad96-13b727e48a91
@github-actions github-actions Bot added Build: Automation Workflows and other setup in .github folder Build: scripts & configs Build scripts and configuration files Ownership: Needs Review Ownership is Other, low confidence, or needs manual correction Team: Other GitHub request for other area than SCM, Finance or Integration labels Oct 7, 2026
@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.


🔄 How to trigger a new status check:

  1. 📤 Push a new commit to the PR branch, or
  2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.

This branch was successfully deployed

1 active deployment
triage — fbd7ec46 Deployed Oct 7, 2026 by t-prda via Classify team ownership #7064
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build: Automation Workflows and other setup in .github folder Build: scripts & configs Build scripts and configuration files Ownership: Needs Review Ownership is Other, low confidence, or needs manual correction Team: Other GitHub request for other area than SCM, Finance or Integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant