VMR Build Failure: Missing Artifact Paths

[mmitche]

Failure Mode: Missing Artifact Paths (Cascading Failure)

Detailed Explanation

The build failed to publish artifacts because the expected output paths did not exist. This is often a cascading failure resulting from earlier build steps failing, so the artifacts were never produced. The error is seen in the publish artifacts and publish build logs steps.

Relevant error lines:

• 'Path does not exist: ...'

Locations within a build:

• Various jobs, including:
  • Publish Artifacts (On Failure)
  • Publish BuildLogs

Affected Builds

• Build 20250509.4
• Build 20250507.4
• Build 20250508.2
• Build 20250507.6
• Build 20250514.1
• Build 20250514.3

---

Example Failure Log Lines

Click to expand

• Path does not exist: /Users/runner/work/1/a/prepublish
• Path does not exist: /mnt/vss/_work/1/a/prepublish
• Path does not exist: D:\a\_work\1\a\prepublish
• error NU1901: ... Package 'Microsoft.Build.Tasks.Core' ... has a known low severity vulnerability, https://github.com/advisories/GHSA-h4j7-5rxr-p4wc
• error MSB3073: ... The command ... exited with code ...

---

Note:
This issue continues to affect new builds, indicating an ongoing problem with artifact generation or a cascading failure from earlier build steps. Please refer to the build logs for more details on the specific jobs and errors encountered.