Skip to content
build-and-deploy

ResolvedVc<T> #19034

Sign in to view logs

ResolvedVc<T>

ResolvedVc<T> #19034

Triggered via push November 29, 2024 18:12
@kdy1kdy1
pushed 818ea15
kdy1/resolved-vc-turbopack-css
Status Failure
Total duration 4m 23s
Artifacts 4

build_and_deploy.yml

on: push
deploy-target
9s
deploy-target
build
2m 8s
build
Matrix: build-wasm
publish-turbopack-npm-packages
0s
publish-turbopack-npm-packages
Matrix: build-native
Deploy examples
0s
Deploy examples
Potentially publish release
0s
Potentially publish release
Upload Turbopack Bytesize metrics to Datadog
0s
Upload Turbopack Bytesize metrics to Datadog
Deploy preview tarball
0s
Deploy preview tarball
Release Stats
0s
Release Stats
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
stable - x86_64-unknown-linux-gnu - node@16: turbopack/crates/turbopack-css/src/process.rs#L250
mismatched types
stable - x86_64-unknown-linux-gnu - node@16: turbopack/crates/turbopack-css/src/process.rs#L481
type mismatch resolving `<UnresolvedUrlReferences as VcValueType>::Read == VcTransparentRead<UnresolvedUrlReferences, Vec<(String, Vc<UrlAssetReference>)>, _>`
stable - x86_64-unknown-linux-gnu - node@16
Process completed with exit code 1.
stable - x86_64-unknown-linux-gnu - node@16: turbopack/crates/turbopack-css/src/references/mod.rs#L11
unused import: `ResolvedVc`
stable - x86_64-unknown-linux-gnu - node@16
Unsupported Cargo.lock format, fallback to caching entire file

Artifacts

Produced during runtime
Name Size
turbo-run-summary-wasm-nodejs
100 KB
turbo-run-summary-wasm-web
100 KB
wasm-binaries-nodejs
6.98 MB
wasm-binaries-web
6.98 MB