bench: govern benchmark IDs with registry and CI validation #76
ci.yml
on: push
Benchmark Registry
4s
ASan + UBSan (Ubuntu)
4m 24s
TSan (Ubuntu)
3m 24s
UBSan (Ubuntu)
2m 28s
Build & Test (Windows / MSVC)
5m 0s
Server Codecs (Ubuntu)
4m 48s
Full Suite 394/394 (Ubuntu)
4m 48s
Post-Quantum PQ (Ubuntu)
4m 23s
Fuzz (Ubuntu, Clang-18)
30m 59s
Coverage (Ubuntu, Clang-18)
3m 27s
Secrets Scan (gitleaks)
4s
Python SAST (bandit)
9s
License Compliance
1m 34s
Mutation Testing Baseline (Ubuntu)
2m 24s
Matrix: build-test
Benchmarks (Ubuntu)
2m 15s
Annotations
2 errors and 6 warnings
|
Benchmarks (Ubuntu)
No benchmark found for bench suite. Possibly mangled output from Catch2:
Filters: [bench]
Randomness seeded to: 2795792524
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
signet_benchmarks is a Catch2 v3.7.1 host application.
Run with -? for options
-------------------------------------------------------------------------------
Write throughput — int64 column 10K rows
-------------------------------------------------------------------------------
/home/runner/work/SIGNET_FORGE/SIGNET_FORGE/benchmarks/bench_write.cpp:25
...............................................................................
benchmark name samples iterations est run time
mean low mean high mean
std dev low std dev high std dev
-------------------------------------------------------------------------------
write_int64_10k_uncompressed 50 1 38.1067 ms
764.249 us 760.212 us 776.222 us
23.045 us 9.08877 us 49.2301 us
-------------------------------------------------------------------------------
Write throughput — double column 10K rows
-------------------------------------------------------------------------------
/home/runner/work/SIGNET_FORGE/SIGNET_FORGE/benchmarks/bench_write.cpp:54
...............................................................................
benchmark name samples iterations est run time
mean low mean high mean
std dev low std dev high std dev
-------------------------------------------------------------------------------
write_double_10k_bss_uncompressed 50 1 38.2974 ms
770.659 us 765.795 us 782.479 us
25.7997 us 13.2835 us 51.8972 us
-------------------------------------------------------------------------------
Write throughput — mixed schema 5 columns 10K rows
-------------------------------------------------------------------------------
/home/runner/work/SIGNET_FORGE/SIGNET_FORGE/benchmarks/bench_write.cpp:86
...............................................................................
benchmark name samples iterations est run time
mean low mean high mean
std dev low std dev high std dev
-------------------------------------------------------------------------------
write_mixed5_10k_uncompressed 50 1 184.443 ms
3.7067 ms 3.69938 ms 3.72127 ms
35.7815 us 21.1772 us 61.7181 us
-------------------------------------------------------------------------------
Write throughput — 100K rows 10 row groups
-------------------------------------------------------------------------------
/home/runner/work/SIGNET_FORGE/SIGNET_FORGE/benchmarks/bench_write.cpp:135
...............................................................................
benchmark name samples iterations est run time
mean low mean high mean
std dev low std dev high std dev
-------------------------------------------------------------------------------
write_int64_double_100k_10_row_gro-
ups 50 1 698.935 ms
|
|
Build & Test (Windows / MSVC)
Process completed with exit code 1.
|
|
Python SAST (bandit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (Ubuntu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (macos-14)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
Coverage (Ubuntu, Clang-18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: codecov/codecov-action@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Fuzz (Ubuntu, Clang-18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Fuzz (Ubuntu, Clang-18)
Fuzz timeouts detected (non-fatal — expected with short budgets):
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
fuzz-crash-artifacts
Expired
|
249 Bytes |
sha256:048249b7216a27bf0d952a976ce1bb67c19168425f48a58c6524543257fe20c2
|
|