HypervibeDocs
SearchCtrl K Menu

Test builds

Internal test builds of Hypervibe, each named by its digest and source revision, with how far it gets. None is a release.

Release
No public release yet
Last verified
On this page

A test build is one set, named by one digest #

A test build is one installable set of Hypervibe's programs, built together and named by the SHA-256 digest of its manifest, and numbered C0, C1 and so on. C0's set holds six builds of four programs; a local install uses three of them: hyper, hv-agent and hv-inferenced. Each test build runs the same thirteen steps, from building the set to a paid run inside a spending limit. The first step that fails is the test build's frontier, and how far the frontier moves is how progress is measured.

A test build is unsigned and carries no support promise. It is not a release: Releases lists those, and there are none yet. Each test build's programs are built for Linux on x86-64.

Test builds so far #

Test buildDigestSource revisionTargetFrontierLabel
C0sha256:6a86148e7d107f36905634df8742c86464f66fe8564bc37068a97c8cf9d1925698914dd044ec75d76268f0c78f316e984d3df023Linux x86-64Step 2, setupInternal test build, unsigned, not a release
C1sha256:a73be86cc24e63d457507354db2a5478e50232b44d88b4ea7efe736643c9736f8245cdcabcf932d3ffc3657975e1f45e61c31706Linux x86-64Step 2, setupInternal test build, unsigned, not a release
C2sha256:7db7dea6f87f40fefe51e4ba156453661333db8965f5f5f0bf47e2dfdb2519a24ddf76c07d77fae09b1ddd6ca358a4c2cfb941a8Linux x86-64Step 5, connect a recordingInternal test build, unsigned, not a release

No test build is published for download yet. When one is, this table gives its download beside its digest, and the install page says how to check the digest before anything runs.

C0, step by step #

StepWhat it checksC0
1The set builds and its digest is recordedPassed
2hyper setup installs the set into an empty home folderUnavailable Setup refuses with state_owner_migration_not_composed: this build's setup cannot yet run the stored-state migrations of the programs it installs. Nothing is changed, and setup ends with exit code 3
3The installed services start and the model service is readyNot reached: nothing is installed
4hyper setup status reports a healthy installationUnavailable It reports that nothing is installed, and ends with exit code 4
5A model account or a recording is connectedUnknown The test connected no account and no recording, so this build's connection was not tried
6hyper exec runs one task on a test repositoryUnavailable This build doesn't have it. It says so in one sentence and ends with exit code 69
7hyper session attach shows the sessionUnavailable There is no session to attach to without step 6
8 to 10Recovery after an interruption, an approval bound to its exact change, and a receipt with the run's costNot reached: they need a run from step 6
11An update that fails its health check goes back to the earlier versionNot tried: it needs a second test build
12hyper uninstall removes the installationNot reached: nothing is installed
13One paid run with a real account, inside its spending limitNot tried: no real account is used for a test build yet

What this build serves #

C0's hyper serves 17 of its 415 named commands: hyper version, hyper completion, hyper setup, hyper setup status, hyper update, hyper uninstall, hyper inference account connect, hyper session attach, hyper build recipe, hyper build run, and the build-job commands hyper job status, logs, wait, fetch, cancel, list and explain. Serving a command does not mean it succeeds on C0: the steps above say what each install step does.

The other 398 are not in this build. Run without arguments, 69 of them say so in one sentence, "hyper … is planned but not available in this build", and end with exit code 69. The other 329 stop sooner in C0: they print a usage error for the missing argument and end with exit code 2. Later test builds are planned to reach the sentence for every command that isn't in the build.

Where to go next #

  • Install gives the tester steps and what the newest test build does at each.
  • Releases lists public releases, which test builds are not.
  • Standings explains Unavailable, Unknown and the other standings.

Search the docs