[Segment Cache] Move cache key creation to client #48984
acdlitebuild_and_test.yml
on: pull_request
Determine changes
7s
build-next
/
build
1m 8s
optimize-ci
/
Graphite CI Optimizer
2s
build-native
/
build
28s
validate-docs-links
12s
Matrix: test unit
test cargo benches
/
Test
5m 26s
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
Waiting for pending jobs
Matrix: Test new tests when deployed
Waiting for pending jobs
report test results to datadog
0s
thank you, next
0s
Annotations
3 errors, 14 warnings, and 10 notices
|
test dev (3/6) / build
Process completed with exit code 1.
|
|
test turbopack dev (3/5) / build
Process completed with exit code 1.
|
|
thank you, next
Process completed with exit code 1.
|
|
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
|
|
optimize-ci / Graphite CI Optimizer
Invalid authentication. Skipping Graphite checks.
|
|
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
|
|
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/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-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-ecmascript/benches/analyzer.rs#L96
Calling `Environment::new(Value::new(ExecutionEnvironment::NodeJsLambda(
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/manifest/chunk_item.rs#L87
Calling `SingleOutputAssetReference::new(*output_asset, key)
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/manifest/loader_item.rs#L119
Calling `SingleOutputAssetReference::new(
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test-playwright-snapshots-test-dev-react--3-6
|
1.74 MB |
|
|
test-playwright-snapshots-test-turbopack-dev-react--3-5
|
1.07 MB |
|
|
test-reports-test-dev-react--3-6
|
40.7 KB |
|
|
test-reports-test-turbopack-dev-react--3-5
|
38.1 KB |
|