Skip to content

Improve performance of set_bits by avoiding to set individual bits #6788

Improve performance of set_bits by avoiding to set individual bits

Improve performance of set_bits by avoiding to set individual bits #6788

Triggered via pull request August 24, 2024 07:37
Status Failure
Total duration 1m 22s
Artifacts

arrow.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Build wasm32
Process completed with exit code 101.
Clippy
Process completed with exit code 101.
Check Compilation
Process completed with exit code 101.
Test
Process completed with exit code 101.
Build wasm32
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Clippy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Check Compilation
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/