Skip to content

Fix unstable_allowDynamic when used with pnpm #48376

Fix unstable_allowDynamic when used with pnpm

Fix unstable_allowDynamic when used with pnpm #48376

Re-run triggered December 10, 2024 16:35
Status Success
Total duration 11m 46s
Artifacts 175

build_and_test.yml

on: pull_request
Determine changes
14s
Determine changes
build-next  /  build
45s
build-next / build
optimize-ci  /  Graphite CI Optimizer
2s
optimize-ci / Graphite CI Optimizer
build-native  /  build
33s
build-native / build
validate-docs-links
12s
validate-docs-links
Matrix: test unit
test next-swc wasm  /  build
2m 29s
test next-swc wasm / build
test cargo benches  /  Test
8m 58s
test cargo benches / Test
test next-swc wasi  /  build
test next-swc wasi / build
test devlow package  /  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
test ppr integration  /  build
1m 35s
test ppr integration / build
types and precompiled  /  build
1m 20s
types and precompiled / build
test firefox and safari  /  build
4m 56s
test firefox and safari / build
Matrix: Run devlow benchmarks
Matrix: Test new tests when deployed
report test results to datadog
1m 29s
report test results to datadog
Fit to window
Zoom out
Zoom in

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
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: 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-core/src/rebase.rs#L55
Calling `RebasedAsset::new(*module, *self.input_dir, *self.output_dir)
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-css/src/chunk/mod.rs#L271
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#L453
Calling `entry_module_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-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`.

Artifacts

Produced during runtime
Name Size
test-reports-test-dev-react--2-4
136 KB
turbo-run-summary-test-dev-react--2-4
238 KB