docs: sort and update CMS examples #47484
delbaoliveirabuild_and_test.yml
on: pull_request
Determine changes
9s
build-next
/
build
32s
optimize-ci
/
Graphite CI Optimizer
2s
build-native
/
build
28s
validate-docs-links
14s
Matrix: test unit
Waiting for pending jobs
test cargo benches
/
Test
test next-swc wasi
/
build
test devlow package
/
build
Matrix: test prod
Waiting for pending jobs
Matrix: test dev
Waiting for pending jobs
Matrix: test integration
Waiting for pending jobs
Matrix: Test new tests for flakes (dev)
Waiting for pending jobs
Matrix: Test new tests for flakes (prod)
Waiting for pending jobs
Matrix: test ppr dev
Waiting for pending jobs
Matrix: test ppr prod
Waiting for pending jobs
Matrix: test turbopack dev
Waiting for pending jobs
Matrix: test turbopack development integration
Waiting for pending jobs
Matrix: test turbopack production integration
Waiting for pending jobs
Matrix: test turbopack production
Waiting for pending jobs
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
16 warnings and 10 notices
|
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.
|
|
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
|
|
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/turbopack-core/src/diagnostics/mod.rs#L114
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/source_map/mod.rs#L61
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/source_map/mod.rs#L95
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/source_map/mod.rs#L96
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L37
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L52
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L90
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/reference/mod.rs#L129
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/proxied_asset.rs#L18
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbopack-core/src/proxied_asset.rs#L19
Don't use a Vc directly in a struct
|
|
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-core/src/reference/mod.rs#L180
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/reference/mod.rs#L195
Calling `module.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-dev-server/src/source/asset_graph.rs#L180
Calling `asset.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#L1062
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#L1080
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#L2262
Calling `Request::parse(Value::new(Pattern::Constant(request)))
|
|
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-css/src/chunk/mod.rs#L272
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#L316
Calling `SingleItemCssChunk::new(*this.chunking_context, **item)
|
|
to-resolved-in-loop:
turbopack/crates/turbo-tasks-fs/src/embed/fs.rs#L52
Calling `path.join(entry_name.clone()).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 | |
|---|---|---|
|
turbo-run-summary-build-native
|
101 KB |
|
|
turbo-run-summary-build-next
|
137 KB |
|
|
turbo-run-summary-lint
|
238 KB |
|
|
turbo-run-summary-types-and-precompiled
|
238 KB |
|