fix: fix CI

[ascandone]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4a624543-a36c-4345-9a30-1c1a55e1bd16

📥 Commits

Reviewing files that changed from the base of the PR and between 93f89d1 and 05a9496.

📒 Files selected for processing (1)

• internal/interpreter/interpreter_test.go

---

Walkthrough

The duplicate remaining allotment test now expects interpreter.InvalidRemainingAllotment instead of machine.InvalidRemainingAllotment.

Changes

Duplicate allotment validation

Layer / File(s)	Summary
Update duplicate allotment assertion internal/interpreter/interpreter_test.go	The test now asserts interpreter.InvalidRemainingAllotment.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: azorlogh, flemzord

Poem

I’m a rabbit with a test to fix,
One error type now neatly clicks.
No duplicate paths remain,
The interpreter leads the train.
Hop, hop—green checks in the mix!

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (1 warning, 2 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title indicates a CI fix, but it is too generic to identify the specific test expectation change.	Use a specific title such as "fix: correct duplicate allotment error type in interpreter test".
Description check	❓ Inconclusive	The pull request has no description, so it does not provide meaningful context for the test change.	Add a brief description that states the expected error type was corrected in the duplicate allotment test.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/fix-red-build

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

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.}

[NumaryBot]

✅ Approve — automated review

The change updates the test expectation to reference the actual interpreter error type already defined and returned by the interpreter, resolving the compile/test issue without affecting production behavior.

No findings.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.20%. Comparing base (dc42b27) to head (05a9496).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #180      +/-   ##
==========================================
+ Coverage   71.03%   71.20%   +0.16%     
==========================================
  Files          58       58              
  Lines        5504     5511       +7     
==========================================
+ Hits         3910     3924      +14     
+ Misses       1358     1352       -6     
+ Partials      236      235       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.