Skip to content

test(notes): cut isOllamaUnreachable's tests to the three that pin its rule - #702

Merged
goosewobbler merged 1 commit into
mainfrom
test/trim-ollama-unreachable-tests
Oct 23, 2026
Merged

goosewobbler merged 1 commit into
mainfrom
test/trim-ollama-unreachable-tests

Conversation

@goosewobbler

@goosewobbler goosewobbler commented Oct 23, 2026 •

Copy link
Copy Markdown
Owner

Description

isOllamaUnreachable decides whether the live Ollama test fails or skips. If it calls too much an outage, the live test just skips with a warning and CI stays green, so the only protection is a unit test. But seven tests was more than the rule needs.

Down to one table of the three cases that pin the rule:

  • a retryable error Ollama classified itself (no cause): outage
  • a socket error under fetch failed: outage
  • a retryable error caused by our own TypeError: not an outage

The third is the one that matters: the tempting simplification "retryable means outage" breaks it, because the provider marks any unknown error retryable. The dropped tests restated obvious branches (not an LLMError, not retryable) or repeated the third case with a different error.

Related Issue(s)

Follow-up to #618.

Type of Change

  • feat — New feature
  • fix — Bug fix
  • docs — Documentation change
  • refactor — Code refactoring
  • test — Adding or updating tests
  • chore — Maintenance, dependencies, tooling
  • Breaking change — Requires major version bump

Scope

  • @releasekit/version
  • @releasekit/notes
  • @releasekit/publish
  • @releasekit/release
  • @releasekit/config
  • @releasekit/core
  • CI / workflows
  • Root / monorepo

Checklist

  • Lint passes (pnpm lint)
  • Tests pass (pnpm test)
  • Typecheck passes (pnpm typecheck)
  • Documentation updated (if applicable)
  • Breaking changes noted in description

Testing Notes

Replacing the predicate with "retryable means outage" fails the third case; the other two pass, as they should.

🤖 Generated with Claude Code

RetriggerView in GreptileConfidence Score: 5/5

This PR appears safe to merge.

Summary

Replaces seven isOllamaUnreachable tests with three table-driven cases.

  • Three Ollama test cases pin when a live run skips.

No actionable issues found.

Reviews (1) · Last reviewed commit: "test(notes): cut isOllamaUnreachable's t..." · Reviewed by Greptile

…s rule

The live test can't catch a predicate that calls too much an outage: it
just skips. What's worth pinning is the rule a simplification would break,
so keep three cases: a self-classified retryable error and a socket error
in the cause chain are outages; a retryable error caused by our own code
isn't. The rest restated obvious branches.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Standing release PR: #614 · v0.42.0 queued (4 packages) · open 82d 6h 56m · ✅ ready to merge

Release Preview — v0.41.2 → v0.41.3

Note: Labels on this PR are advisory in standing-pr mode. Bumps come from conventional commits in the standing PR; override by editing labels on the standing PR itself. Add release:immediate to bypass the standing PR and release this PR directly.

These changes will be added to the release PR (#614) when merged:

Changelog

monorepo 0.41.2 → 0.41.3

Changed

  • cut isOllamaUnreachable's tests to the three that pin its rule (notes)

All packages → 0.41.3 (sync versioning)

  • @releasekit/version
  • @releasekit/notes
  • @releasekit/publish
  • @releasekit/release

After merge — predicted release

No version escalation — this PR's changes will be included in the queued release without affecting the projected versions.

Package Standing PR This PR After merge
monorepo 0.42.0 0.41.3 0.42.0

Updated automatically by ReleaseKit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant