Skip to content

Test CI PR workflow - for fix/auto regression test#388

Open
peterchave wants to merge 9 commits into
mainfrom
fix/auto-regression-test
Open

Test CI PR workflow - for fix/auto regression test#388
peterchave wants to merge 9 commits into
mainfrom
fix/auto-regression-test

Conversation

@peterchave

@peterchave peterchave commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Testing the perf test is triggered on PR.


This change is Reviewable

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

⚡ Performance Results

Results for 30d53a7 (no baseline data available yet).

Metric This Run Baseline Δ
Peak Subscribers 100
Throughput 47.2 Mbps
Throughput/Core 11.8 Mbps
Subscribers/Core 25
Delivery Success 100.0 %
Relay CPU 21.9 %
Relay RSS 26.3 MB
RSS/Session 269.0 KB
Total Resets 0
UDP Errors/s 0
Test parameters & full results
  • Result: Test stopped
  • Subscribers: 100 (ramp 100/s)
  • Duration: 120s
  • IO threads: 4
  • Client threads: 4
  • Transport: quic
  • Baseline window: 10 runs (0 available)

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

⚡ Performance Results

Results for c905e27 (no baseline data available yet).

Metric This Run Baseline Δ
Peak Subscribers 100
Throughput 47.2 Mbps
Throughput/Core 11.8 Mbps
Subscribers/Core 25
Delivery Success 100.0 %
Relay CPU 22.5 %
Relay RSS 27.2 MB
RSS/Session 278.8 KB
Total Resets 0
UDP Errors/s 0
Test parameters & full results
  • Result: Test stopped
  • Subscribers: 100 (ramp 100/s)
  • Duration: 120s
  • IO threads: 4
  • Client threads: 4
  • Transport: quic
  • Baseline window: 10 runs (0 available)

afrind added a commit that referenced this pull request Jun 6, 2026
…ind-package

The auto Boost-linking probe from #388 used
`cmake --find-package ... -DMODE=EXIST -DBoost_USE_STATIC_LIBS=ON`,
which is a false positive: that mode only checks whether Boost is
locatable at all and ignores Boost_USE_STATIC_LIBS. On distros that ship
only libboost_*.so (CentOS/RHEL), it reports "static found", the script
selects static linking, and the build dies at ninja time with
`libboost_context.a ... missing` -- the exact failure #388 meant to fix.

Replace the probe with one that asks the compiler driver to resolve each
static archive moxygen actually links (context, filesystem,
program_options, regex) via `c++ -print-file-name`. That returns an
absolute path only when the .a exists in the compiler's own search
paths -- definitive, no hardcoded paths, no distro sniffing.

Also always pass -DBoost_USE_STATIC_LIBS explicitly (ON or OFF) instead
of omitting it for shared. A re-run of `setup` reuses the existing build
dir; omitting would leave a stale Boost_USE_STATIC_LIBS=ON in
CMakeCache.txt in force.

Verified: clean build picks shared and links; a poisoned =ON cache is
overridden to OFF and still builds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants