Skip to content

Run the textsearch app's tests in CI - #62

Merged
sadit merged 2 commits into
mainfrom
ci-app-tests
Sep 28, 2026
Merged

sadit merged 2 commits into
mainfrom
ci-app-tests

Conversation

@sadit

@sadit sadit commented Sep 28, 2026

Copy link
Copy Markdown
Owner

apps/textsearch is its own project ([sources] TextSearch = {path = "../.."}), and julia-runtest only tests the package at the root. So no CI job ran the app's tests: #58 (lazy loading of CSV/Parquet2) and #59 (all the LSI handling in the CLI) went green on checks that covered none of their changes.

Change

A new app-test job in ci.yml, on Ubuntu and Windows, which runs:

julia --project=apps/textsearch -e 'using Pkg; Pkg.instantiate(); Pkg.test()'
  • Since no Manifest is committed for the app, it gets resolved from scratch, the same way pkg"app develop apps/textsearch" does on a user's machine. That also catches a compat that stops resolving.
  • It passes GITHUB_TOKEN, since the app's tests list releases through the API (Send GITHUB_TOKEN to the GitHub API when listing a release #60).
  • It has its own artifact cache, falling back to the one from the test job.

Verified

I ran that same command on a clean worktree with no Manifest: 279/279. Windows only gets tested with this PR's CI. The library's file:// tests already pass on Windows, but this is the first time the app's run there.

🤖 Generated with Claude Code

sadit and others added 2 commits September 28, 2026 09:24
apps/textsearch is its own project, and julia-runtest tests only the
package at the root, so no CI job ran the app's 279 tests: #58 and #59
went green on checks that covered none of their changes. A new app-test
job resolves the app fresh (no Manifest is committed, as on a user's
machine) and runs Pkg.test() on Ubuntu and Windows, with GITHUB_TOKEN for
the release listings its tests make.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
write_fit_config substituted raw paths into TOML basic strings, where a
Windows path's backslashes start escapes (\U...) and the parser fails with
"invalid unicode scalar". Every fit test failed on Windows, and the tests
built on their profiles with them. The app itself writes no paths into
TOML; only the test helper did.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@sadit
sadit merged commit 0aa44b5 into main Sep 28, 2026
5 checks passed
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