fix: empty generateStaticParams should still create an ISR route #48268
ztannerbuild_and_test.yml
on: pull_request
Determine changes
7s
build-next
/
build
1m 7s
optimize-ci
/
Graphite CI Optimizer
2s
build-native
/
build
29s
validate-docs-links
12s
Matrix: test unit
test cargo benches
/
Test
6m 53s
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 29s
thank you, next
0s
Annotations
14 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/turbo-tasks-macros-tests/tests/function/fail_resolved_static.rs#L8
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_resolved_trait_impl.rs#L11
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_resolved_inherent_impl.rs#L11
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/value/fail_resolved.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:
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-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-core/src/introspect/utils.rs#L72
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#L89
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#L99
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#L121
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-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-ppr-dev-2-4
|
89.4 KB |
|
|
turbo-run-summary-test-ppr-dev-2-4
|
238 KB |
|