Skip to content

Enable Helix queue stats logging for Arcade unit tests#17018

Draft
chcosta wants to merge 2 commits into
dotnet:mainfrom
chcosta:dev/chcosta/enable-helix-queue-stats
Draft

Enable Helix queue stats logging for Arcade unit tests#17018
chcosta wants to merge 2 commits into
dotnet:mainfrom
chcosta:dev/chcosta/enable-helix-queue-stats

Conversation

@chcosta

@chcosta chcosta commented Jun 17, 2026

Copy link
Copy Markdown
Member

Enables the new opt-in Helix queue health summary (added in #16922) for Arcade's own tests/UnitTests.proj.

Adds <EnableShowHelixQueueStats>true</EnableShowHelixQueueStats> so that every Helix job submitted by the Arcade unit-test pipeline logs the queue health summary at submit time. This dogfoods the feature and gives FRs immediate signal on Helix queue conditions when Arcade's own CI submits work.

Depends on #16922 having shipped through Arcade.

Copilot AI review requested due to automatic review settings June 17, 2026 16:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Enables Helix queue health summary logging for Arcade’s own Helix-submitted unit test jobs by opting in via MSBuild property, so Arcade CI “dogfoods” the feature and emits queue condition signal at job submission time.

Changes:

  • Set EnableShowHelixQueueStats to true in tests/UnitTests.proj so Helix submissions from Arcade unit tests log the queue health summary.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Default CI verbosity is Minimal, which filters out MessageImportance.Normal
messages. When EnableShowHelixQueueStats is opted in, route SendAsync log
output (including the queue-health summary) at High importance so it
survives the default verbosity.
@chcosta

chcosta commented Jun 17, 2026

Copy link
Copy Markdown
Member Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@chcosta

chcosta commented Jun 19, 2026

Copy link
Copy Markdown
Member Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

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.

2 participants