-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Labels
bugSomething isn't workingSomething isn't workingnew-issueNew issue which was not discussed yetNew issue which was not discussed yet
Description
Describe the bug
More recently we spotted a notable number of failures which are likely caused by cached broken archives.
The cache mechanism should try to remove a broken archive and perform a download instead of current behavior.
See https://github.com/ansible/vscode-ansible/actions/runs/18847067994/job/53773796606#step:20:80
Please note that we ween more than 10s of such errors which still also happened after we removed all the GHA caches, making us believe that getting broken archive is more common than expected.
Steps to reproduce
N/ALogs
Downloading VS Code: 1.104.2 / stable
VS Code archive 1.104.2-stable.tar.gz already exists in storage folder, skipping download
Unpacking VS Code into /home/runner/work/vscode-ansible/vscode-ansible/out/test-resources
Error: unexpected end of file
at genericNodeError (node:internal/errors:983:15)
at wrappedFn (node:internal/errors:537:14)
at Zlib.zlibOnError [as onerror] (node:zlib:190:17)Operating System
Visual Studio Code
vscode-extension-tester
NodeJS
npm
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingnew-issueNew issue which was not discussed yetNew issue which was not discussed yet
Type
Projects
Status
New