Add JOTL (JAM On The Lisp) to conformance & performance testing

[polykrate]

Summary

• Add jotl-performance.yml workflow calling the reusable picofuzz workflow
• Docker image: ghcr.io/polykrate/jotl:latest
• Command: {TARGET_SOCK} (socket path passed as first argument)
• Readiness pattern: Listening on
• Memory: 2048m — SBCL needs a larger heap for 128 live states (fork support) and bounded GC pauses

About JOTL

JOTL is a Common Lisp (SBCL) implementation of the JAM protocol. It speaks the JAM Fuzz protocol v1 over Unix sockets. All 6 minifuzz suites pass locally (no_forks, forks, fallback, safrole, storage, storage_light).

Test plan

• All 6 minifuzz suites pass locally
• Trigger workflow_dispatch to verify on self-hosted runner

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 18c61a70-3cae-4f1d-bce9-a0e3f9acf67d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Added a new GitHub Actions workflow for performance testing of the "jotl" project, scheduled to run daily at 6 AM and on manual trigger. Also added a README file for the jotl team directory with a project title header.

Changes

Cohort / File(s)	Summary
Jotl Infrastructure and Documentation .github/workflows/jotl-performance.yml, teams/jotl/README.md	Added new GitHub Actions workflow that reuses an existing picofuzz workflow to run performance tests for jotl with specified Docker image and readiness pattern. Added README header for jotl team directory.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding JOTL to conformance and performance testing through the new workflow file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description is directly related to the changeset, describing the addition of a performance workflow for JOTL and providing relevant context about the implementation.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

Tip

You can customize the high-level summary generated by CodeRabbit.

Configure the reviews.high_level_summary_instructions setting to provide custom instructions for generating the high-level summary.

[tomusdrw]

Can you please add README.md badge for JOTL?

[polykrate]

Done.

BTW thanks for the tools in FluffyLabs it helped a lot.

[polykrate]

Could you also add JOTL to the dashboard's client-metadata.json (in the paritytech/jam-conformance-dashboard submodule)? Here's the entry:

"jotl": {
  "displayName": "JOTL",
  "language": "Common Lisp",
  "languageColor": "#3fb68b",
  "author": "Community",
  "url": "https://github.com/polykrate/JOTL"
}

Currently JOTL shows up on the leaderboard without a language label. Happy to open a separate PR to the dashboard repo if preferred.

[tomusdrw]

It's a submodule, so the fix needs to be in https://github.com/paritytech/jam-conformance-dashboard/ and then feel free to create a PR to just bump the submodule version. Thanks!