fix(turbopack): Enable explicit_resource_management transform
#48575
kdy1build_and_test.yml
on: pull_request
Determine changes
9s
build-next
/
build
31s
optimize-ci
/
Graphite CI Optimizer
3s
build-native
/
build
51s
validate-docs-links
12s
Matrix: test unit
test cargo benches
/
Test
6m 47s
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
2m 26s
thank you, next
0s
Annotations
14 warnings and 10 notices
|
validate-docs-links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Determine changes
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/turbo-tasks-macros-tests/tests/function/fail_non_local_static.rs#L8
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_inherent_impl.rs#L11
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_trait_impl.rs#L11
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/value/fail_non_local.rs#L8
Don't use a Vc directly in a struct
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L953
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::Start`
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L953
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::End`
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L953
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::End`
|
|
rustdoc check / build:
crates/napi/src/next_api/project.rs#L953
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:
crates/next-core/src/next_shared/transforms/swc_ecma_transform_plugins.rs#L54
Calling `project_path.root().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/reference/mod.rs#L184
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-swc-utils/src/emitter.rs#L32
Calling `issue.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/code_builder.rs#L167
Calling `encoded.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/introspect/utils.rs#L77
Calling `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-core/src/introspect/utils.rs#L95
Calling `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-core/src/introspect/utils.rs#L105
Calling `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-core/src/introspect/utils.rs#L127
Calling `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-core/src/resolve/mod.rs#L1072
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#L1090
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`.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test-reports-test-ppr-dev-3-4
|
90.1 KB |
|
|
turbo-run-summary-test-ppr-dev-3-4
|
239 KB |
|