Skip to content

ci: build qs2/stringfish from source (RcppParallel 6.2.0 oneTBB ABI break) - #211

Open
seonghobae wants to merge 1 commit into
masterfrom
ci/tbb-abi-source-build
Open

ci: build qs2/stringfish from source (RcppParallel 6.2.0 oneTBB ABI break)#211
seonghobae wants to merge 1 commit into
masterfrom
ci/tbb-abi-source-build

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

The check job fails during dependency setup while building SimDesign:

unable to load shared object '.../stringfish/libs/stringfish.so':
undefined symbol: _ZN3tbb8internal25concurrent_vector_base_v316internal_grow_byEmmPFvPvPKvmES4_

Root cause: RcppParallel 6.2.0 migrated to oneTBB and dropped the legacy tbb::internal symbols. The cached/prebuilt stringfish (and qs2) binaries still link those symbols, so anything loading them under the freshly built RcppParallel 6.2.0 fails. Pre-existing repo-wide breakage, unrelated to PR diffs (seen on #209, job 91893493500).

Fix: force stringfish=?source and qs2=?source in setup-r-dependencies and bump cache-version to 2 to discard poisoned caches. Same fix as ContextualWisdomLab/kaefa#76, where the previously failing macOS/Windows release jobs already went green. Revert once CRAN/PPM rebuild binaries against RcppParallel 6.2.0.

Unblocks #209 and every other open aFIPC PR.

🤖 Generated with Claude Code

…reak)

RcppParallel 6.2.0 switched to oneTBB and dropped the tbb::internal
symbols that prebuilt/cached qs2/stringfish binaries link against, so
dependency setup fails while building SimDesign (dyn.load of
stringfish.so: undefined symbol). Force both packages to build from
source against the current RcppParallel and bump cache-version to
discard poisoned caches. Same fix as kaefa#76.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a18f193f-917e-4979-8d45-4925586266d4

📥 Commits

Reviewing files that changed from the base of the PR and between 35e4498 and b772a7c.

📒 Files selected for processing (1)
  • .github/workflows/r.yml

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae enabled auto-merge (squash) August 4, 2026 07:27
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