Skip to content

Fix -Werror=comment in profile_stress.cc (unblock fork main CI) - #45

Merged
jayakasadev merged 1 commit into
mainfrom
fix/profile-stress-comment-werror
Jun 12, 2026
Merged

jayakasadev merged 1 commit into
mainfrom
fix/profile-stress-comment-werror

Conversation

@jayakasadev

Copy link
Copy Markdown
Owner

Summary

  • Drop trailing backslashes from // comment lines at src/test/perf/profile_stress/profile_stress.cc:13,19,20
  • They were shell continuations in the example commands but in C++ they line-continue the // into the next source line, which gcc rejects under -Werror=comment
  • Fix unblocks ubuntu-24.04 Release / build, ubuntu-24.04 Debug / build, and all downstream jobs that depend on a clean library build (~20 failing jobs on current fork main)

Diagnosis

Failing job: https://github.com/jayakasadev/snmalloc/actions/runs/27385175943/job/80995619632

src/test/perf/profile_stress/profile_stress.cc:13:1: error: multi-line comment [-Werror=comment]
src/test/perf/profile_stress/profile_stress.cc:19:1: error: multi-line comment [-Werror=comment]

This was introduced in fork PR #24 (Phase 7.4 stress test) but missed by CI because the stress test was only built in the post-merge sanitizer matrix that does not gate.

Test plan

  • Local build: cmake -B build -DSNMALLOC_PROFILE=ON && cmake --build build --target perf-profile_stress-fast builds clean
  • No semantic change — comment text reads the same
  • CI on this PR turns the ~20 inherited failures green (verify after push)

Trailing backslashes on // comment lines line-continued the comment
into the next source line, which gcc -Werror=comment flags. They were
intended as shell continuations in the example commands but have no
meaning inside a C++ comment. Drop the backslashes; the example reads
the same.

Unblocks ubuntu-24.04 Release / Debug builds on fork main.
@jayakasadev
jayakasadev merged commit 6ceed2e into main Jun 12, 2026
147 of 211 checks passed
@jayakasadev
jayakasadev deleted the fix/profile-stress-comment-werror branch June 12, 2026 14:28
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.

1 participant