Skip to content
PR Build

Collect telemetry before exit #2522

Sign in to view logs

Collect telemetry before exit

Collect telemetry before exit #2522

Triggered via pull request August 27, 2025 23:06
@vicromsvicroms
opened #1771
vicroms:telemetry-fix
Status Success
Total duration 36m 37s
Artifacts –

pr.yaml

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

Annotations

40 errors and 2 warnings
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 (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,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,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]: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-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-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-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/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/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
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 (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,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,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]: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-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-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-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/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/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
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 (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,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,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]: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-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-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-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/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/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/unexpected-pass-port-fail.txt#L2
vcpkg-empty-featureful-port[core,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-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,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,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]: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-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-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-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/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/conflicting-features.txt#L2
'b' was already declared as 'feature-fails'
format
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xo+vaAAAAAAKlXxOfToITpBII0t7NsaSQlkzRURHRTA0MTgARWRnZQ==
format
Failed to restore: Cache service responded with 400