Nightly #40
spomichternightly.yml
on: schedule
Checks
/
Check if running codegen would produce any changes
23h 48m
Checks
/
Rerun lints
28s
Checks
/
Toml format check
18s
Checks
/
Check uv.lock is up-to-date
37s
Checks
/
Check for too large files
19s
Checks
/
Check for wrong publish flags
19s
Checks
/
Check example thumbnails
25s
Checks
/
Check example manifest coverage
18s
Checks
/
Lint markdown
22s
Checks
/
Spell Check
8s
Checks
/
Misc formatting
20s
Checks
/
Check links
39s
Checks
/
matrix_prep
5s
Build JS
/
Build rerun_js
23h 48m
Build web viewer
/
Build web viewer
23h 48m
Checks
/
C++ formatting check
31s
Checks
/
Rust lints (fmt, check, clippy, doc)
23h 48m
Checks
/
Test on Linux
23h 48m
Checks
/
Python lints (ruff, mypy, …)
42s
Checks
/
Test Python Docs
40s
Benchmarks
/
Rust Criterion benchmarks
23h 48m
Matrix: Checks / mac-windows-checks-nightly
Matrix: Checks / Tests only (main)
Matrix: cargo build on clean container
Linux-arm64: Build & Upload rerun-cli
/
set-config
Windows-x64: Build & Upload rerun-cli
/
set-config
Matrix: Checks / cpp-tests
Upload JS
/
Upload rerun_js to google cloud
Upload Web
/
Upload web build to google cloud (wasm32 + wasm-bindgen)
Linux-arm64: Build & Upload rerun-cli
/
build-rerun-cli
Linux-x64: Build & Upload rerun-cli
/
build-rerun-cli
Mac-arm64: Build & Upload rerun-cli
/
build-rerun-cli
Windows-x64: Build & Upload rerun-cli
/
build-rerun-cli
Linux-Arm64: Build & Upload rerun_c
/
rs-build-rerun_c
Linux-x64: Build & Upload rerun_c
/
rs-build-rerun_c
Mac-Arm64: Build & Upload rerun_c
/
rs-build-rerun_c
Windows-x64: Build & Upload rerun_c
/
rs-build-rerun_c
Bundle and upload rerun_cpp_sdk.zip
/
Bundle and upload rerun_cpp_sdk.zip
linux-arm64: Test Wheels
/
test-wheels
Upload Examples
/
Upload Examples to Google Cloud
Linux-x64: Test Wheels
/
test-wheels
macos-arm64: Test Wheels
/
test-wheels
Windows-x64: Test Wheels
/
test-wheels
Sync pre-release assets & build.rerun.io
/
Upload assets from build.rerun.io
Annotations
38 errors and 15 warnings
|
cargo build on clean container (macos-26-xlarge)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
cargo build on clean container (ubuntu-latest-16-cores)
The strategy configuration was canceled because "clean-build.macos-26-xlarge" failed
|
|
cargo build on clean container (windows-latest-8-cores)
The strategy configuration was canceled because "clean-build.macos-26-xlarge" failed
|
|
Checks / macos (individual crates)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / macos (base & deny)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / macos (tests)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / macos (wasm & examples)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / macos (docs)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / macos (tests default features)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / C++ build & test - Mac aarch64
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
|
|
Checks / C++ build & test - Linux x64, C++17
The strategy configuration was canceled because "checks-cpp.cpp-tests.Mac_aarch64_macos-26-xlar" failed
|
|
Checks / C++ build & test - Windows x64, C++17
The strategy configuration was canceled because "checks-cpp.cpp-tests.Mac_aarch64_macos-26-xlar" failed
|
|
Checks / C++ build & test - Windows x64, C++20 (skipped on PRs)
The strategy configuration was canceled because "checks-cpp.cpp-tests.Mac_aarch64_macos-26-xlar" failed
|
|
Checks / C++ build & test - Linux x64, C++20 (skipped on PRs)
The strategy configuration was canceled because "checks-cpp.cpp-tests.Mac_aarch64_macos-26-xlar" failed
|
|
Checks / Toml format check
Process completed with exit code 1.
|
|
Checks / Misc formatting
Process completed with exit code 1.
|
|
Checks / Rerun lints
Process completed with exit code 1.
|
|
Checks / Check uv.lock is up-to-date
Process completed with exit code 1.
|
|
Checks / Check links
Process completed with exit code 2.
|
|
Checks / Test Python Docs
Process completed with exit code 1.
|
|
Checks / Python lints (ruff, mypy, …)
Process completed with exit code 1.
|
|
Benchmarks / Rust Criterion benchmarks
Canceling since a higher priority waiting request for nightly-bench exists
|
|
Checks / Test on Linux
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Checks / windows (base & deny)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Checks / Check if running codegen would produce any changes
Canceling since a higher priority waiting request for nightly-checks exists
|
|
Checks / windows (docs)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Checks / windows (wasm & examples)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Checks / windows (tests)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Build web viewer / Build web viewer
Canceling since a higher priority waiting request for nightly-build-web exists
|
|
Build JS / Build rerun_js
Canceling since a higher priority waiting request for nightly-build-js exists
|
|
Checks / Rust lints (fmt, check, clippy, doc)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Checks / windows (tests default features)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Checks / windows (individual crates)
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Nightly
Canceling since a higher priority waiting request for nightly-checks_rust exists
|
|
Nightly
Canceling since a higher priority waiting request for nightly-checks exists
|
|
Nightly
Canceling since a higher priority waiting request for nightly-bench exists
|
|
Nightly
Canceling since a higher priority waiting request for nightly-build-js exists
|
|
Nightly
Canceling since a higher priority waiting request for nightly-build-web exists
|
|
Checks / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Spell Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Toml format check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Check example manifest coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Check for wrong publish flags
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Check for too large files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Misc formatting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Lint markdown
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Check example thumbnails
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Rerun lints
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / C++ formatting check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Check uv.lock is up-to-date
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Check links
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Test Python Docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks / Python lints (ruff, mypy, …)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|