Skip to content

Remove broken 'Windows > Tests > Debugging' CI lane#11109

Merged
jonathanpeppers merged 1 commit intomainfrom
jonathanpeppers/remove-debugging-ci-lane
Apr 14, 2026
Merged

Remove broken 'Windows > Tests > Debugging' CI lane#11109
jonathanpeppers merged 1 commit intomainfrom
jonathanpeppers/remove-debugging-ci-lane

Conversation

@jonathanpeppers
Copy link
Copy Markdown
Member

@jonathanpeppers jonathanpeppers commented Apr 14, 2026

Fixes: #11062

Summary

Remove the Windows > Tests > Debugging CI lane (debug_windows_tests job) from the emulator test stage. This lane has been silently broken since at least March 21, 2026 — zero DebuggingTest tests have actually executed in over 4 weeks.

Root Cause

The Android emulator on Windows CI agents consistently fails to start with:

[Vulkan Loader] ERROR | DRIVER: windows_read_data_files_in_registry:
Registry lookup failed to get ICD manifest files.
Possibly missing Vulkan driver?

Because the pipeline treats emulator start failure as succeededWithIssues rather than a hard failure (by design — see the startContinueOnError: true and condition: eq(variables['EMULATOR_STARTED'], 'true') guards), the tests are silently skipped every run and the job appears to "pass".

Evidence

Checked the Debugging lane across all recent CI builds spanning March 21 → April 14:

  • Every single build: Start emulator → error → Run tests → skipped → job result: succeededWithIssues
  • Zero builds had the emulator successfully start or any tests actually run

What's removed

  • The debug_windows_tests job in stage-msbuild-emulator-tests.yaml (56 lines)
  • No other files reference this job

The Android emulator on Windows CI agents has been unable to start
since at least March 21, 2026, consistently failing with:

  [Vulkan Loader] ERROR | DRIVER: windows_read_data_files_in_registry:
  Registry lookup failed to get ICD manifest files.
  Possibly missing Vulkan driver?

Because the pipeline treats this as 'succeededWithIssues' rather than
a hard failure, the lane has been silently broken — zero DebuggingTest
tests have actually run in at least 4 weeks. Remove the lane entirely
until the infrastructure issue is resolved.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 14, 2026 14:32
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Removes the non-functional Windows > Tests > Debugging CI lane from the MSBuild emulator test stage, since the Windows emulator consistently fails to start and the pipeline logic causes the tests to be silently skipped while the job still “passes”.

Changes:

  • Removed the debug_windows_tests job from the emulator tests stage template.
  • Removed the associated “fail on issue only if emulator started” step tied to that job.

@jonathanpeppers
Copy link
Copy Markdown
Member Author

/azp run Xamarin.Android-PR

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@jonathanpeppers jonathanpeppers merged commit 65455f3 into main Apr 14, 2026
9 of 10 checks passed
@jonathanpeppers jonathanpeppers deleted the jonathanpeppers/remove-debugging-ci-lane branch April 14, 2026 18:56
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.

Emulator 36.x Vulkan probe failure on Windows CI agent despite -gpu swiftshader

2 participants