examples: remove the old files from with-postgres
#48179
samcxbuild_and_test.yml
on: pull_request
Determine changes
8s
build-next
/
build
33s
optimize-ci
/
Graphite CI Optimizer
3s
build-native
/
build
25s
validate-docs-links
13s
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
10 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/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
|
|
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:
crates/next-core/src/next_shared/transforms/swc_ecma_transform_plugins.rs#L54
Calling `project_path.root().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-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-ecmascript/src/typescript/mod.rs#L62
Calling `TsExtendsReference::new(**config_asset)
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/typescript/mod.rs#L154
Calling `TsConfigTypesReference::new(
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/references/mod.rs#L601
Calling `EsmAssetReference::new(
|
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 |
|