When the Assayer isn't working as it should

Its page shows only one line#

"The Assayer is for people who write software": developer features are off, because no developer agent is hired. Hire the Assayer in Castellan, from the Aletaster's card. While they're off, it runs no rounds.

A repository isn't tested#

It tests the repositories in Castellan's Settings > Repositories whose checkout is on this PC and whose origin is that GitHub repository. Check that it's listed there, and that git remote get-url origin in the checkout names it.

A branch isn't tested, or wasn't opened as a pull request#

• It was committed to less than 2 hours ago: Leave a branch alone for waits, in case you're still working on it.
• It's checked out with uncommitted changes. Commit or set them aside.
• It already has a pull request, or you closed or merged one at this same commit.
• It has nothing that isn't on origin.
• A case failed: it's under Didn't pass, with the output. It's tested again once the branch moves.
• The round was full: at most 3 test runs a round. The rest come in the next rounds.

A case is missing, or runs the wrong command#

Under Settings > Test cases you set, add the case, or give the found one another Command, by the project's name as Castellan's Settings have it. Some found cases (cargo clippy and build, dotnet build) are off until you turn them on there.

Tests pass on your PC but fail in its run#

Its run is in a clean worktree at the commit, so what's only on your PC isn't there:

• Uncommitted or untracked files the tests need.
• Packages: a Node project borrows your node_modules only when the commit's package-lock.json matches the checkout's. Otherwise make the case install them first: npm ci && npm test.
• Environment variables set in your own shell.

The failing output on the page says which.

A run stops at 20 minutes#

That's Stop a test run after. Raise it under Advanced, or let the branch run only what its change reaches (Test only what a change reaches).

A test is marked flaky#

It passed and failed on the same commit with the same tools. It's the test, or what it depends on (time, order, the network), not the change.

Release ready fails#

Each check says what it found: versions that disagree, a pull request without its changelog line, a checksum that doesn't match, or CI that isn't green. Fix it in the repository: the Assayer only reads.

A tool was put back, and something else broke#

Put back used your version manager, or winget. Put the newer version back the same way, by hand.

Its page won't open#

Its page is http://assayer.localhost:20909/. Open on the Aletaster's card in Castellan starts it if it's down.

Still stuck?#

Write to us at support@castellan-software.com with the Assayer's version (on its card in Castellan), the repository and case, and what its page says.