Skip to content

[ci-scan] Test failure: AppHost.Bundle.Tests.BundledAppWithSubDirs reuses a stale extraction on macOS Helix #135155

Description

@lewing

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1621829
Build error leg or test failing: runtime osx-arm64 Debug CoreCLR_AllSubsets - AppHost.Bundle.Tests.BundledAppWithSubDirs.FrameworkDependent(options: BundleAllContent)
Pull request: #134813

KBE authoring guidance (ci-failure-scan)
  • Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
  • Build Analysis parses only the single JSON block under Error Message.
  • ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
  • Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.

Error Details

The first run of a BundleAllContent bundle is expected to extract, but the host found an existing extraction and reused it. The default extraction base on the macOS Helix runner is the runner account's home directory (/Users/helix-runner/.net/...), which persists across work items, so an extraction left by an earlier run of the identical bundle on the same machine makes the "new extraction" assertion fail. Build Analysis reports a 0.26% failure rate. The SelfContained variant uses the same assertion and would fail the same way. Likely fix: give the tests a per-run DOTNET_BUNDLE_EXTRACT_BASE_DIR (not verified).

failed AppHost.Bundle.Tests.BundledAppWithSubDirs.FrameworkDependent(options: BundleAllContent) (1s 616ms)
  **WARNING** failure message 'The command error output did not contain expected result: 'Starting new extraction of application bundle'
  ...
  Files embedded within the bundle will be extracted to [/Users/helix-runner/.net/AppWithSubDirs/o30fbB-HueWi] directory.
  Reusing existing extraction of application bundle.
  ...
    at Microsoft.DotNet.CoreSetup.Test.CommandResultAssertions.HaveStdErrContaining(String pattern) in /_/src/installer/tests/TestUtils/Assertions/CommandResultAssertions.cs:100
    at AppHost.Bundle.Tests.BundledAppResultExtensions.CreateExtraction(CommandResultAssertions assertion, Boolean shouldExtract)
    at AppHost.Bundle.Tests.BundledAppWithSubDirs.FrameworkDependent(BundleOptions options) in /_/src/installer/tests/AppHost.Bundle.Tests/BundledAppWithSubDirs.cs:71

Error Message

{
  "ErrorMessage": "The command error output did not contain expected result: 'Starting new extraction of application bundle'",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log

Note

This issue was drafted with GitHub Copilot.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1621829
Error message validated: [The command error output did not contain expected result: 'Starting new extraction of application bundle']
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/3/2026 2:14:01 AM UTC

Report

Build Repository Test Pull Request
1621829 dotnet/runtime AppHost.Bundle.Tests.BundledAppWithSubDirs.FrameworkDependent #134813

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 1 1

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Build ErrorUse this to report build issues in the .NET Helix tabarea-Hostblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'untriagedNew issue has not been triaged by the area owner

    Type

    No type

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions