Skip to content
PR Build

Localized file check-in by OneLocBuild Task: Build definition ID 15684: Build ID 11775386 #2340

Sign in to view logs

Localized file check-in by OneLocBuild Task: Build definition ID 15684: Build ID 11775386

Localized file check-in by OneLocBuild Task: Build definition ID 15684: Build ID 11775386 #2340

Triggered via pull request June 17, 2025 21:51
@BillyONealBillyONeal
reopened #1706
locfiles/04b68422-598b-4467-8c8d-9cdaed67171c
Status Success
Total duration 38m 3s
Artifacts –

pr.yaml

on: pull_request
format
3m 27s
format
json-schema
1m 27s
json-schema
Matrix: builds / build
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 2 warnings
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-states.txt#L2
'vcpkg-empty-featureful-port' was already declared as 'pass'
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-combo-fail.txt#L2
vcpkg-empty-featureful-port[core,a,a-default-feature,b,c]:x64-osx passed but was marked expected to fail
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-cascade.txt#L2
vcpkg-empty-featureful-port[core,a]:x64-osx passed but vcpkg-empty-featureful-port[a] was marked expected to be a cascaded failure
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x64-osx passed but vcpkg-empty-featureful-port[b] was marked expected to fail
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core]:x64-osx passed but was marked expected to fail
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a]:x64-osx passed but was marked expected to fail
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a-default-feature]:x64-osx passed but was marked expected to fail
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x64-osx passed but was marked expected to fail
builds / build (macos-14, macos-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,c]:x64-osx passed but was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-states.txt#L2
'vcpkg-empty-featureful-port' was already declared as 'pass'
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-combo-fail.txt#L2
vcpkg-empty-featureful-port[core,a,a-default-feature,b,c]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-cascade.txt#L2
vcpkg-empty-featureful-port[core,a]:x64-linux passed but vcpkg-empty-featureful-port[a] was marked expected to be a cascaded failure
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x64-linux passed but vcpkg-empty-featureful-port[b] was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a-default-feature]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-22.04, linux-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,c]:x64-linux passed but was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-states.txt#L2
'vcpkg-empty-featureful-port' was already declared as 'pass'
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-combo-fail.txt#L2
vcpkg-empty-featureful-port[core,a,a-default-feature,b,c]:x86-windows passed but was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-cascade.txt#L2
vcpkg-empty-featureful-port[core,a]:x86-windows passed but vcpkg-empty-featureful-port[a] was marked expected to be a cascaded failure
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x86-windows passed but vcpkg-empty-featureful-port[b] was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core]:x86-windows passed but was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a]:x86-windows passed but was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a-default-feature]:x86-windows passed but was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x86-windows passed but was marked expected to fail
builds / build (windows-2022, windows-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,c]:x86-windows passed but was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/conflicting-states.txt#L2
'vcpkg-empty-featureful-port' was already declared as 'pass'
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-combo-fail.txt#L2
vcpkg-empty-featureful-port[core,a,a-default-feature,b,c]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-cascade.txt#L2
vcpkg-empty-featureful-port[core,a]:x64-linux passed but vcpkg-empty-featureful-port[a] was marked expected to be a cascaded failure
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-feature-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x64-linux passed but vcpkg-empty-featureful-port[b] was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,a-default-feature]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,b]:x64-linux passed but was marked expected to fail
builds / build (ubuntu-24.04-arm, linux-arm64-ci): azure-pipelines/e2e-assets/ci-feature-baseline/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,c]:x64-linux passed but was marked expected to fail
format
Failed to restore: getCacheEntry failed: Cache service responded with 503
format
Failed to save: reserveCache failed: Cache service responded with 503