Skip to content
PR Build

CiBuildLogsRecorder: Fix collection of logs #2312

Sign in to view logs

CiBuildLogsRecorder: Fix collection of logs

CiBuildLogsRecorder: Fix collection of logs #2312

Triggered via pull request May 24, 2025 11:15
@autoantwortautoantwort
opened #1689
autoantwort:feature/fix-collection-of-logs
Status Success
Total duration 36m 38s
Artifacts –

pr.yaml

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

Annotations

40 errors and 1 warning
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-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 (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 restore: Cache service responded with 422