Skip to content
CI

Factor out the mdtest crate #69566

Sign in to view logs

Factor out the mdtest crate

Factor out the mdtest crate #69566

Triggered via pull request April 16, 2026 13:06
@ntBrentBre
synchronize #24616
brent/mdtest-crate
Status Success
Total duration 12m 59s
Artifacts 3

ci.yaml

on: pull_request
Determine changes
24s
Determine changes
cargo fmt
20s
cargo fmt
python package
1m 30s
python package
prek
1m 7s
prek
mkdocs
2m 48s
mkdocs
benchmarks instrumented ty (build)
2m 22s
benchmarks instrumented ty (build)
benchmarks walltime (build)
2m 27s
benchmarks walltime (build)
cargo clippy
2m 1s
cargo clippy
cargo test (linux)
4m 11s
cargo test (linux)
cargo test (wasm)
3m 8s
cargo test (wasm)
cargo build (msrv)
1m 48s
cargo build (msrv)
test scripts
1m 8s
test scripts
cargo test (linux, release)
3m 8s
cargo test (linux, release)
cargo fuzz build
4m 47s
cargo fuzz build
fuzz parser
7m 52s
fuzz parser
ecosystem
6m 1s
ecosystem
Fuzz for new ty panics
2m 48s
Fuzz for new ty panics
cargo shear
22s
cargo shear
ty completion evaluation
1m 30s
ty completion evaluation
formatter instabilities and black similarity
3m 5s
formatter instabilities and black similarity
test ruff-lsp
2m 44s
test ruff-lsp
check playground
check playground
benchmarks instrumented (ruff)
4m 3s
benchmarks instrumented (ruff)
Matrix: cargo-test-other
Matrix: benchmarks-instrumented-ty-run
Matrix: benchmarks-walltime-run
all required checks passed
4s
all required checks passed
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
cargo build (msrv)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SebRollen/toml-action@b1b3628f55fc3a28208d4203ada8b737e9687876. 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/
cargo test (wasm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jetli/wasm-pack-action@0d096b08b4e5a7de8c28de67e11e945404e9eefa. 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/
benchmarks instrumented (ruff)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks instrumented ty (memory: attrs|hydra|datetype)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks instrumented ty (simulation: attrs|hydra|datetype)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks instrumented ty (memory: check_file|micro|anyio)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks walltime (colour_science)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks walltime (pydantic|multithreaded|freqtrade)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks walltime (pandas|tanjun|altair)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks walltime (static_frame|sympy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
benchmarks instrumented ty (simulation: check_file|micro|anyio)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/

Artifacts

Produced during runtime
Name Size Digest
benchmarks-instrumented-ty-binary Expired
72.4 MB
sha256:dfd7164124441e54d78053a6d58d753c9cf5455da5b0f11a4c5183b84dddee48
benchmarks-walltime-binary Expired
68 MB
sha256:1301cb60fee56e87e0b2cbafca6355330b2953f826a5da3fc3ebbb12e21fddda
ecosystem-result
245 Bytes
sha256:9b76e35ac1778b76640b85ef65697cea55cf1ee1fa3f81b47f3920279c9705a4
⚡