Fix missing error message in terminal for bound args serialization error #47626
unstubbablebuild_and_test.yml
on: pull_request
Determine changes
8s
build-next
/
build
1m 53s
optimize-ci
/
Graphite CI Optimizer
3s
build-native
/
build
42s
validate-docs-links
12s
Matrix: test unit
test cargo benches
/
Test
6m 12s
test next-swc wasi
/
build
test devlow package
/
build
Matrix: test prod
Matrix: test dev
Matrix: test integration
Matrix: Test new tests for flakes (dev)
Matrix: Test new tests for flakes (prod)
Matrix: test ppr dev
Matrix: test ppr prod
Matrix: test turbopack dev
Matrix: test turbopack development integration
Matrix: test turbopack production integration
Matrix: test turbopack production
Matrix: Run devlow benchmarks
Matrix: Test new tests when deployed
report test results to datadog
1m 57s
thank you, next
0s
Annotations
20 warnings and 10 notices
|
Determine changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
validate-docs-links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
optimize-ci / Graphite CI Optimizer
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
ast-grep lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/diagnostics/mod.rs#L114
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/source_map/mod.rs#L61
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/source_map/mod.rs#L95
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/source_map/mod.rs#L96
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L37
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L52
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L90
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L129
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/proxied_asset.rs#L18
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/proxied_asset.rs#L19
Don't use a Vc directly in a struct
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::Start`
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::End`
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::End`
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::Start`
|
|
thank you, next
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
report test results to datadog
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/reference/mod.rs#L180
Calling `RawModule::new(*source).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/resolve/mod.rs#L1062
Calling `FileSource::new(**path).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/resolve/mod.rs#L1080
Calling `FileSource::new(**path).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/resolve/mod.rs#L2254
Calling `Request::parse(Value::new(Pattern::Constant(request)))
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/rebase.rs#L55
Calling `RebasedAsset::new(*module, *self.input_dir, *self.output_dir)
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-css/src/chunk/mod.rs#L270
Calling `chunk_item_key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-css/src/chunk/mod.rs#L314
Calling `SingleItemCssChunk::new(*this.chunking_context, **item)
|
|
to-resolved-in-loop:
turbopack/crates/turbo-tasks-fs/src/embed/fs.rs#L52
Calling `path.join(entry_name.clone()).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/chunk/mod.rs#L90
Calling `chunk_item_key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/references/mod.rs#L616
Calling `EsmAssetReference::new(
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test-playwright-snapshots-test-dev-react--3-4
|
273 KB |
|
|
test-reports-test-dev-react--3-4
|
131 KB |
|
|
turbo-run-summary-test-dev-react--3-4
|
238 KB |
|