Skip to content

Fix public triage launch flakiness - #8333

Open
Thaddeus Loke (thloke) wants to merge 1 commit into
masterfrom
fix/triage-launch-flakiness
Open

Fix public triage launch flakiness#8333
Thaddeus Loke (thloke) wants to merge 1 commit into
masterfrom
fix/triage-launch-flakiness

Conversation

@thloke

Copy link
Copy Markdown
Contributor

Summary

  • resolve Business Central application and platform manifest versions independently from the running container
  • wait for the hosted Windows runner Docker API before creating the sandbox
  • retry ALTool symbol downloads only when ALTool marks the failure as retryable
  • pin BcContainerHelper 6.1.17 in both triage setup paths
  • accept equivalent affirmative wording when the agent recommends closing an issue as likely fixed

Failure evidence

  • Runs 30, 31, 33, and 34 requested platform 30 symbols from BC 30 artifacts whose platform was still 29, producing Downloaded 1 of 2 requested symbols
  • Runs 20, 24, and 32 started before the hosted runner Docker API was ready
  • Run 29 completed agent execution but failed the narrow likely-fixed recommendation regex

Validation

  • pwsh -NoProfile -File scripts/Test-AlIssueTriageWorkflow.ps1
  • PowerShell parser checks for all changed scripts
  • git diff --check
  • verified BcContainerHelper 6.1.17 is available from PSGallery and exports both version-discovery commands

Resolve BC application and platform versions independently, wait for the hosted runner Docker API, retry explicitly transient symbol downloads, and accept equivalent likely-fixed close recommendations.

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

Copilot-Session: bef46529-fd3d-459a-aba7-5c7014d23da2
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.

1 participant