Skip to content

[error overlay] fix infinite loop when frames are failed to fetch #25864

[error overlay] fix infinite loop when frames are failed to fetch

[error overlay] fix infinite loop when frames are failed to fetch #25864

Triggered via push February 13, 2025 00:05
Status Success
Total duration 5m 13s
Artifacts 7
deploy-target
22s
deploy-target
publish-turbopack-npm-packages
0s
publish-turbopack-npm-packages
Matrix: build-native
Matrix: build-wasm
Upload Turbopack Bytesize metrics to Datadog
0s
Upload Turbopack Bytesize metrics to Datadog
Deploy examples
0s
Deploy examples
Potentially publish release
0s
Potentially publish release
Deploy preview tarball
2m 10s
Deploy preview tarball
Release Stats
0s
Release Stats
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
stable - x86_64-unknown-linux-gnu - node@16
Unsupported Cargo.lock format, fallback to caching entire file
stable - x86_64-unknown-linux-gnu - node@16
Unsupported Cargo.lock format, fallback to caching entire file
stable - x86_64-unknown-linux-gnu - node@16
No files were found with the provided path: .turbo/runs. No artifacts will be uploaded.
build
Cache not found for keys: ae758ebccebc5c9bb75e90f38d02503d617a4ca4-25864-1

Artifacts

Produced during runtime
Name Size
next-swc-binaries-x86_64-unknown-linux-gnu
46 MB
preview-tarballs
68.9 MB
turbo-run-summary-wasm-nodejs
104 KB
turbo-run-summary-wasm-web
104 KB
turbopack-bytesize-x86_64-unknown-linux-gnu
207 Bytes
wasm-binaries-nodejs
6.97 MB
wasm-binaries-web
6.97 MB