Use provided waitUntil for pending revalidates (#74164) #50291
build_and_test.yml
on: pull_request
Determine changes
10s
build-next
/
build
1m 4s
optimize-ci
/
Graphite CI Optimizer
4s
build-native
/
build
26s
validate-docs-links
14s
Matrix: test unit
test cargo benches
/
Test
6m 55s
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 5s
thank you, next
0s
Annotations
4 errors, 14 warnings, and 10 notices
test integration (8/12) / build
$GITHUB_STEP_SUMMARY upload aborted, supports content up to a size of 1024k, got 3191k. For more information see: https://docs.github.com/actions/using-workflows/workflow-commands-for-github-actions#adding-a-markdown-summary
|
test dev (2/4) / build
Process completed with exit code 1.
|
test integration (9/12) / build
Process completed with exit code 1.
|
thank you, next
Process completed with exit code 1.
|
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/value/fail_non_local.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_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_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
|
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-browser/src/ecmascript/evaluate/chunk.rs#L221
Calling `chunk.ident().to_string().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/rebase.rs#L55
Calling `RebasedAsset::new(*module, *self.input_dir, *self.output_dir)
|
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-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`.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
test-playwright-snapshots-test-dev-react--2-4
|
1.49 MB |
|
test-playwright-snapshots-test-integration-9-12-react-
|
87.8 KB |
|
test-playwright-snapshots-test-turbopack-integration-react--1-5
|
365 KB |
|
test-playwright-snapshots-test-turbopack-integration-react--4-5
|
15.8 MB |
|
test-reports-test-dev-react--1-4
|
118 KB |
|
test-reports-test-dev-react--2-4
|
45.5 KB |
|
test-reports-test-integration-9-12-react-
|
26.6 KB |
|
test-reports-test-turbopack-integration-react--1-5
|
79.5 KB |
|
test-reports-test-turbopack-integration-react--4-5
|
48.5 KB |
|
turbo-run-summary-test-dev-react--1-4
|
238 KB |
|
turbo-run-summary-test-turbopack-integration-react--1-5
|
238 KB |
|
turbo-run-summary-test-turbopack-integration-react--4-5
|
238 KB |
|