Skip to content
Continuous integration

feat(simd): re-export f32_to_bf16_batch_rne / f32_to_bf16_scalar_rne Makes the pure AVX-512-F RNE routines from commit c489d31 reachable as ndarray::simd::f32_to_bf16_batch_rne and ndarray::simd::f32_to_bf16_scalar_rne for consumer code in lance-graph. Without this re-export, callers would have to reach into the private simd_avx512 module path, which is not pub mod in lib.rs. Doc comment on the re-export explicitly pins the workspace-wide "never scalar ever" rule for F32→BF16: consumer hot loops use f32_to_bf16_batch_rne exclusively (500-20,000× faster than scalar via AMX/AVX-512-BF16 tiles), and f32_to_bf16_scalar_rne is exposed only as a unit-test reference implementation. Cross-references the Certification Process section in lance-graph/CLAUDE.md. Companion commit in lance-graph updates seven_lane_encoder.rs Lane 6 to call the batch primitive instead of its previous element-wise truncation loop. https://claude.ai/code/session_019RzHP8tpJu55ESTxhfUy1A #141

Sign in to view logs

feat(simd): re-export f32_to_bf16_batch_rne / f32_to_bf16_scalar_rne Makes the pure AVX-512-F RNE routines from commit c489d31 reachable as ndarray::simd::f32_to_bf16_batch_rne and ndarray::simd::f32_to_bf16_scalar_rne for consumer code in lance-graph. Without this re-export, callers would have to reach into the private simd_avx512 module path, which is not pub mod in lib.rs. Doc comment on the re-export explicitly pins the workspace-wide "never scalar ever" rule for F32→BF16: consumer hot loops use f32_to_bf16_batch_rne exclusively (500-20,000× faster than scalar via AMX/AVX-512-BF16 tiles), and f32_to_bf16_scalar_rne is exposed only as a unit-test reference implementation. Cross-references the Certification Process section in lance-graph/CLAUDE.md. Companion commit in lance-graph updates seven_lane_encoder.rs Lane 6 to call the batch primitive instead of its previous element-wise truncation loop. https://claude.ai/code/session_019RzHP8tpJu55ESTxhfUy1A

feat(simd): re-export f32_to_bf16_batch_rne / f32_to_bf16_scalar_rne Makes the pure AVX-512-F RNE routines from commit c489d31 reachable as ndarray::simd::f32_to_bf16_batch_rne and ndarray::simd::f32_to_bf16_scalar_rne for consumer code in lance-graph. Without this re-export, callers would have to reach into the private simd_avx512 module path, which is not pub mod in lib.rs. Doc comment on the re-export explicitly pins the workspace-wide "never scalar ever" rule for F32→BF16: consumer hot loops use f32_to_bf16_batch_rne exclusively (500-20,000× faster than scalar via AMX/AVX-512-BF16 tiles), and f32_to_bf16_scalar_rne is exposed only as a unit-test reference implementation. Cross-references the Certification Process section in lance-graph/CLAUDE.md. Companion commit in lance-graph updates seven_lane_encoder.rs Lane 6 to call the batch primitive instead of its previous element-wise truncation loop. https://claude.ai/code/session_019RzHP8tpJu55ESTxhfUy1A #141

Triggered via pull request April 11, 2026 20:50
@AdaWorldAPIAdaWorldAPI
opened #88
claude/risc-thought-engine-TCZw7
Status Failure
Total duration 1m 45s
Artifacts –

ci.yaml

on: pull_request
Pass MSRV values to other jobs
2s
Pass MSRV values to other jobs
Matrix: clippy
Matrix: cross_test
Matrix: nostd
format/stable
20s
format/stable
native-backend/stable
39s
native-backend/stable
miri
0s
miri
cargo-careful
0s
cargo-careful
docs/nightly
0s
docs/nightly
Matrix: tests
blas-msrv
56s
blas-msrv
conclusion
0s
conclusion
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 10 warnings
format/stable
Process completed with exit code 1.
clippy/stable
Process completed with exit code 1.
nostd/thumbv6m-none-eabi/stable
Process completed with exit code 101.
native-backend/stable
Process completed with exit code 101.
tests/stable
Process completed with exit code 101.
tests/beta
The strategy configuration was canceled because "tests.stable" failed
tests/beta
The operation was canceled.
tests/1.64.0
The strategy configuration was canceled because "tests.stable" failed
tests/1.64.0
The operation was canceled.
cross_test/i686-unknown-linux-gnu/stable
Process completed with exit code 101.
cross_test/s390x-unknown-linux-gnu/stable
The strategy configuration was canceled because "cross_test.stable_i686-unknown-linux" failed
cross_test/s390x-unknown-linux-gnu/stable
The operation was canceled.
format/stable
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/
clippy/stable
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/
nostd/thumbv6m-none-eabi/stable
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/
native-backend/stable
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/
tests/stable
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/
blas-msrv
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/
tests/beta
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/
tests/1.64.0
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/
cross_test/i686-unknown-linux-gnu/stable
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/
cross_test/s390x-unknown-linux-gnu/stable
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/