Skip to content
build-and-test

Docs: Getting Started Nits #48354

Sign in to view logs

Docs: Getting Started Nits

Docs: Getting Started Nits #48354

Triggered via pull request December 10, 2024 11:48
@delbaoliveiradelbaoliveira
synchronize #73596
docs-getting-started-nits
Status Success
Total duration 2m 49s
Artifacts 4

build_and_test.yml

on: pull_request
Determine changes
7s
Determine changes
build-next  /  build
38s
build-next / build
optimize-ci  /  Graphite CI Optimizer
10s
optimize-ci / Graphite CI Optimizer
build-native  /  build
36s
build-native / build
validate-docs-links
13s
validate-docs-links
Matrix: test unit
Waiting for pending jobs
rust check  /  build
rust check / build
test cargo unit  /  build
test cargo unit / build
ast-grep lint
9s
ast-grep lint
rustdoc check  /  build
rustdoc check / build
test next-swc wasm  /  build
test next-swc wasm / build
test cargo benches  /  Test
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
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
test ppr integration  /  build
test ppr integration / build
lint  /  build
1m 47s
lint / build
types and precompiled  /  build
1m 4s
types and precompiled / build
test firefox and safari  /  build
test firefox and safari / build
Matrix: Run devlow benchmarks
Waiting for pending jobs
Matrix: Test new tests when deployed
Waiting for pending jobs
report test results to datadog
0s
report test results to datadog
thank you, next
0s
thank you, next
Fit to window
Zoom out
Zoom in

Annotations

9 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
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
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/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
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/value/fail_non_local.rs#L8
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#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-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/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#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
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