You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"ErrorMessage" : "Can not open the file as archive",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
}
@dotnet/dnceng
Release Note Category
Feature changes/additions
Bug fixes
Internal Infrastructure Improvements
Release Note Description
Additional information about the issue reported
Output:
❌Extraction failed for file: D:\a\_work\1\s\__download__\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release.zip code: 2 stdout: 7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21
Scanning the drive for archives:
1 file, 0 bytes
Extracting archive: D:\a\_work\1\s\__download__\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release.zip
Can't open as archive: 1
Files: 0
Size: 0
Compressed: 0
stderr: ERROR: D:\a\_work\1\s\__download__\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release.zip
Can not open the file as archive
error: undefined;
Build
https://dev.azure.com/dnceng-public/public/_build/results?buildId=618300
Build leg reported
Build / Installer Build and Test windows_x86 Debug / Unzip unified artifacts
Pull Request
dotnet/runtime#100001
Known issue core information
Fill out the known issue JSON section by following the step by step documentation on how to create a known issue
@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
Output:
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=618300
Error message validated:
[Can not open the file as archive
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/26/2024 11:00:34 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: