cache post-setup failures
See original GitHub issueall of a sudden this morning our cache post-setup started failing with
Post Set up cache 15s
Post job cleanup.
/bin/tar -cz -f /home/runner/work/_temp/2c4ed222-ac5c-466d-b163-19853e6fd4a2/cache.tgz -C /home/runner/work/cloud-custodian/cloud-custodian/.tox/py37 .
[warning]Cache service responded with 500 during chunk upload.
events.js:187
throw er; // Unhandled 'error' event
^
Error: EBADF: bad file descriptor, read
Emitted 'error' event on ReadStream instance at:
at internal/fs/streams.js:167:12
at FSReqCallback.wrapper [as oncomplete] (fs.js:470:5) {
errno: -9,
code: 'EBADF',
syscall: 'read'
}
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Post setup Python step fails (pipenv cache) · Issue #436 - GitHub
Hey! So this used to work just a few days ago. We've been having some issues with cache in the last few days...
Read more >[PATCH 0/1] fontcache: fix fonts postinst failed - kernel
Expected: No build warning of "The postinstall intercept hook 'update_font_cache' failed" //Hongxu The following changes since commit ...
Read more >Getting npm caching to work for a .net core angular project in ...
Solution: @Walter's answer fixed one of the errors I was getting. Fixing the path, removing the quotes and pointing to the ClientApp folder,...
Read more >ERROR: petalinux-user-image-1.0-r0 do_rootfs - Xilinx Support
... do_rootfs: The postinstall intercept hook 'update_font_cache' failed, ... -xilinx-linux/petalinux-user-image/1.0-r0/rootfs/usr/libexec/fc-cache ...
Read more >The postinstall intercept hook 'update_pixbuf_cache' failed
loaders.cache: No such file or directory. WARNING: The postinstall intercept hook 'update_pixbuf_cache' failed (exit code: 1)! See log for ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting! Issue was caused by an automated OS update that started failing requests with large bodies. We have been deploying a fix using the old OS image. The fix has already deployed to 2 of the 3 scale units, so this may be mitigated for some of you. Will be fixed on the last scale unit in about 20 minutes.
I get same error today. But my error in upload-artifact@v2