Skip to content

Add support for pinning actors to a dedicated scheduler thread #2730

Add support for pinning actors to a dedicated scheduler thread

Add support for pinning actors to a dedicated scheduler thread #2730

Triggered via pull request November 24, 2024 17:52
Status Failure
Total duration 24m 46s
Artifacts

pr.yml

on: pull_request
Matrix: x86_64-linux
Lint bash, docker, markdown, and yaml
1m 15s
Lint bash, docker, markdown, and yaml
Validate musl Docker image builds
30s
Validate musl Docker image builds
Validate GNU Docker image builds
34s
Validate GNU Docker image builds
Validate Windows Docker image builds
2m 4s
Validate Windows Docker image builds
Validate musl Docker release image builds
21s
Validate musl Docker release image builds
Validate GNU Docker release image builds
47s
Validate GNU Docker release image builds
Validate Windows Docker release image builds
2m 32s
Validate Windows Docker release image builds
Verify CHANGELOG is valid
7s
Verify CHANGELOG is valid
x86-64 Apple Darwin
16m 30s
x86-64 Apple Darwin
arm64 Apple Darwin
10m 41s
arm64 Apple Darwin
x86-64 Windows MSVC
24m 33s
x86-64 Windows MSVC
Matrix: aarch64-linux
Matrix: arm-linux
Matrix: armhf-linux
Matrix: riscv64-linux
Matrix: use_directives
Fit to window
Zoom out
Zoom in

Annotations

9 errors
arm64 Apple Darwin
Process completed with exit code 2.
x86-64 Linux glibc
Process completed with exit code 2.
aarch64 Linux glibc
Process completed with exit code 2.
riscv64 Linux glibc
Process completed with exit code 2.
x86-64 Linux musl
Process completed with exit code 2.
x86-64 Apple Darwin
Process completed with exit code 2.
arm Linux glibc
Process completed with exit code 2.
armhf Linux glibc
Process completed with exit code 2.
x86-64 Windows MSVC
Process completed with exit code 1.