Disable Run Helix Tests step in Azure pipeline due to offline devices#2407
Merged
Conversation
dotnet-policy-service
Bot
added
area-System.Device.Gpio
Co-authored-by: joperezr <13854455+joperezr@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Disable Run Helix Tests from our azure pipeline
Disable Run Helix Tests step in Azure pipeline due to offline devices
Jul 25, 2025
joperezr
reviewed
Jul 25, 2025
Co-authored-by: joperezr <13854455+joperezr@users.noreply.github.com>
joperezr
approved these changes
Jul 25, 2025
Member
|
/azp run dotnet.iot |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pgrawehr
approved these changes
Jul 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Run Helix Tests" step in the Linux job of our Azure DevOps pipeline has been consistently failing because the devices used for these tests are currently offline. This was causing all builds to fail, preventing changes from being merged.
This PR temporarily disables the failing step by changing its condition from
eq(variables['build.reason'], 'PullRequest')tofalse. The step structure is preserved to make re-enabling straightforward once the devices are back online.Changes:
azure-pipelines.yml(line 121)Impact:
Re-enabling:
When the devices come back online, simply change
condition: falseback tocondition: eq(variables['build.reason'], 'PullRequest')to restore the original behavior.Fixes #2406.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Microsoft Reviewers: Open in CodeFlow