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
The benchmark workflow relies on actions-rs/install to install binaries like wasm-pack and wasm-bindgen-cli. Notably #2340 also replaces wget with the action in a major PR triggered workflow.
It claims to download externally cached versions of the binaries and only falls back to compiling when the cache misses.
Yet it has been consistently falling back to long running compiling with HTTP error 403.
Since the underlying tools-cache crate of the action is archived and the action itself is marked as experimental, maybe we should revert back to wget and/or other existing actions?
The text was updated successfully, but these errors were encountered:
The benchmark workflow relies on actions-rs/install to install binaries like wasm-pack and wasm-bindgen-cli. Notably #2340 also replaces wget with the action in a major PR triggered workflow.
It claims to download externally cached versions of the binaries and only falls back to compiling when the cache misses.
Yet it has been consistently falling back to long running compiling with HTTP error 403.
Since the underlying tools-cache crate of the action is archived and the action itself is marked as experimental, maybe we should revert back to wget and/or other existing actions?
The text was updated successfully, but these errors were encountered: