.iw/commands/test.scala first PURPOSE line leaves out the lint and contract suites #654

Open
opened 2026-09-29 11:37:49 +00:00 by claude · 3 comments
Member

.iw/commands/test.scala line 1 says:

// PURPOSE: Run project tests (unit tests, integration tests, command compilation, and E2E tests)

The command also runs the lint and contract suites (// USAGE: iw test [lint|unit|itest|compile|e2e|contract]), so the first PURPOSE line does not name all the suites it runs.

Found during IW-636 (PR #653), which added the second PURPOSE line to this file.

`.iw/commands/test.scala` line 1 says: ``` // PURPOSE: Run project tests (unit tests, integration tests, command compilation, and E2E tests) ``` The command also runs the `lint` and `contract` suites (`// USAGE: iw test [lint|unit|itest|compile|e2e|contract]`), so the first PURPOSE line does not name all the suites it runs. Found during IW-636 (PR #653), which added the second PURPOSE line to this file.
Author
Member

Intake: agent-ready
Workflow: diagnostic
Reason: all gates passed
Analysis: project-management/issues/IW-654/analysis.md on branch IW-654

Intake: agent-ready Workflow: diagnostic Reason: all gates passed Analysis: project-management/issues/IW-654/analysis.md on branch IW-654
Author
Member

Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin did not compile against the core of this branch, so no phase ran. ForgeCatchUp.requestOnPhaseBranch expects Either[String, …] from fetchPullRequestForBranch, and core on main now returns Either[TrackerError, …] (#778). This stops every batch-implement run in iw-cli until the plugin is updated; it is not a defect of this issue. batch-implement.log was not written.

[error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7
[error] Found:    Either[iw.core.model.TrackerError, Option[batch.ForgeState]]
[error] Required: Either[String, Option[batch.ForgeState]]
Compilation failed
Implement: needs-human Reason: batch-implement exit 1 — the kanon plugin did not compile against the core of this branch, so no phase ran. `ForgeCatchUp.requestOnPhaseBranch` expects `Either[String, …]` from `fetchPullRequestForBranch`, and core on `main` now returns `Either[TrackerError, …]` (#778). This stops every batch-implement run in iw-cli until the plugin is updated; it is not a defect of this issue. batch-implement.log was not written. ``` [error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7 [error] Found: Either[iw.core.model.TrackerError, Option[batch.ForgeState]] [error] Required: Either[String, Option[batch.ForgeState]] Compilation failed ```
Author
Member

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
iterative-works/iw-cli#654
No description provided.