Skip to content

Changed package manager for install-native.mjs to pnpm #4690

Changed package manager for install-native.mjs to pnpm

Changed package manager for install-native.mjs to pnpm #4690

Triggered via pull request July 21, 2023 16:06
Status Success
Total duration 51m 29s
Artifacts 1
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build_and_test.yml

on: pull_request
test cargo unit  /  build
28s
test cargo unit / build
test cargo integration  /  build
1m 23s
test cargo integration / build
test cargo benchmarks  /  build
1m 31s
test cargo benchmarks / build
rust check  /  build
27s
rust check / build
Matrix: test dev
Matrix: test integration
Matrix: test prod
Matrix: test turbopack integration
test turbopack dev  /  build
4m 4s
test turbopack dev / build
test firefox and safari  /  build
8m 23s
test firefox and safari / build
report-test-results  /  build
1m 35s
report-test-results / build
thank you, next
0s
thank you, next
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 139 warnings
report-test-results / build
Unable to find an artifact with the name: Test trace reports
report-test-results / build
Process completed with exit code 1.
build-native / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
build-native / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
rust check / build
No files were found with the provided path: .turbo/runs. No artifacts will be uploaded.
rust check / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
rust check / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test cargo unit / build
No files were found with the provided path: .turbo/runs. No artifacts will be uploaded.
test cargo unit / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test cargo integration / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test cargo integration / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test cargo benchmarks / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
lint / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
lint / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
types and precompiled / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
types and precompiled / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test next-swc wasm / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test next-swc wasm / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test next-swc wasm / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test next-swc wasm / build: packages/next-swc/crates/core/src/lib.rs#L35
unused import: `env::current_dir`
test next-swc wasm / build
`next-swc` (lib) generated 1 warning (run `cargo fix --lib -p next-swc` to apply 1 suggestion)
test turbopack integration (2) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test turbopack integration (2) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test turbopack dev / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test turbopack dev / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test turbopack integration (3) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test turbopack integration (3) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test turbopack integration (4) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test turbopack integration (4) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test turbopack integration (1) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test turbopack integration (1) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test turbopack integration (5) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test turbopack integration (5) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test firefox and safari / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test firefox and safari / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (6) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (6) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (2) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (2) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (12) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (12) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (7) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (7) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (4) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (4) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (11) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (11) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (1) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (1) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (5) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (5) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (8) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (8) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test dev (2) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test dev (2) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test dev (1) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test dev (1) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (3) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (3) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (9) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (9) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test prod (2) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test prod (2) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test prod (1) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test prod (1) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test dev (3) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test dev (3) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test prod (3) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test prod (3) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test prod (4) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test prod (4) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test prod (5) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test prod (5) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
test integration (10) / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
test integration (10) / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)
report-test-results / build
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
report-test-results / build
`next-core` (lib) generated 2 warnings (run `cargo fix --lib -p next-core` to apply 2 suggestions)

Artifacts

Produced during runtime
Name Size
turbo run summary Expired
28.4 MB