Increase pbnjam docker memory to 4096m

[tomusdrw]

Closes: #13

Summary

• Set docker_memory: '4096m' for both pbnjam fuzz and performance workflows
• The pbnjam target needs ~3.5 GB RAM for native bindings ring proof verification, which preloads and caches data in-memory
• Previously using defaults (2048m for fuzz, 512m for performance), which were insufficient

Test plan

• Verify pbnjam fuzz workflow runs without OOM kills
• Verify pbnjam performance workflow runs without OOM kills

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Increased Docker memory allocation to 4GB in fuzz testing and performance testing workflows.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fa84c3fb-2885-4adb-af76-1d2b41f2231e

📥 Commits

Reviewing files that changed from the base of the PR and between 8e13ce2 and 552b883.

📒 Files selected for processing (2)

• .github/workflows/pbnjam-fuzz.yml
• .github/workflows/pbnjam-performance.yml

---

📝 Walkthrough

Walkthrough

Two GitHub Actions workflow files are updated to allocate 4096m of memory to their Docker containers during CI execution. The pbnjam-fuzz.yml and pbnjam-performance.yml workflows each receive a new docker_memory parameter with this value.

Changes

Cohort / File(s)	Summary
Docker Memory Allocation .github/workflows/pbnjam-fuzz.yml, .github/workflows/pbnjam-performance.yml	Added docker_memory: '4096m' parameter to specify container memory limits for both the pbnjam fuzz job and the reusable-picofuzz workflow invocation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Standardize docker memory limit for all performance targets #7: This PR increases docker_memory to 4096m in two workflows, which conflicts with the proposed standardization approach mentioned in this issue.

Possibly related PRs

• JOTL: increase container memory to 2048m #5: Both PRs modify the docker_memory input parameter for reusable-picofuzz workflow invocations to increase container memory allocation.
• Add jamzilla and jamzilla-int performance workflows #3: Related through modification of GitHub Actions workflow invocations that call the reusable-picofuzz workflow with input parameters.

Poem

🐰 Fuzzing faster with more room to play,
4096 megabytes to save the day!
Docker containers breathing deep,
Better tests while developers sleep! 🔬✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and clearly describes the main change: increasing docker memory allocation to 4096m for pbnjam workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch pbnjam-memory-4g

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}