Skip to content
Windows-CI

Adjust vcpkg baseline, etc. to fix backdoored liblzma issue #666

Sign in to view logs

Adjust vcpkg baseline, etc. to fix backdoored liblzma issue

Adjust vcpkg baseline, etc. to fix backdoored liblzma issue #666

Triggered via pull request April 23, 2024 00:51
@stephengtuggystephengtuggy
synchronize #845
stephengtuggy:fix/844_on_master
Status Failure
Total duration 3m 12s
Artifacts –

Windows-CI.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
build (windows-2022, VS2022Win64, 1, Debug)
Process completed with exit code 1.
build (windows-2019, VS2019Win64, 1, Release)
Process completed with exit code 1.
build (windows-2022, VS2022Win64, 1, Debug)
No files were found with the provided path: D:\a\Vega-Strike-Engine-Source\Vega-Strike-Engine-Source/**/test-results/**/*.xml. No artifacts will be uploaded.
build (windows-2022, VS2022Win64, 1, Debug)
Failed to restore: Cache service responded with 400
build (windows-2019, VS2019Win64, 1, Release)
Failed to restore: Cache service responded with 400
build (windows-2019, VS2019Win64, 1, Release)
No files were found with the provided path: D:\a\Vega-Strike-Engine-Source\Vega-Strike-Engine-Source/**/test-results/**/*.xml. No artifacts will be uploaded.