mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-02 14:32:45 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
43 lines
1.9 KiB
TOML
43 lines
1.9 KiB
TOML
# The k3s integration tests each boot a privileged single-node Kubernetes
|
|
# cluster in docker. Their #[serial] attributes only lock within a process,
|
|
# and nextest runs one process per test, so without this group the clusters
|
|
# boot concurrently and starve each other (and the runner) — the K8s-aware
|
|
# assignment paths then stall on a slow API server and time out. max-threads
|
|
# serializes them across processes; threads-required keeps the rest of the
|
|
# suite from saturating the runner while a cluster is up.
|
|
[test-groups]
|
|
k3s = { max-threads = 1 }
|
|
# The two-partition double-zombie models are the stateright suite's long
|
|
# pole (roughly 15x anything else in it). Their checkers explore
|
|
# multi-threaded, so each gets the whole thread budget to itself instead
|
|
# of contending with the rest of the suite mid-explore.
|
|
stateright-heavy = { max-threads = 1 }
|
|
|
|
[[profile.default.overrides]]
|
|
filter = 'binary(k3s_integration)'
|
|
test-group = 'k3s'
|
|
threads-required = 4
|
|
|
|
[[profile.default.overrides]]
|
|
filter = 'package(personinsights-stateright) & test(two_partitions_double_zombie)'
|
|
test-group = 'stateright-heavy'
|
|
threads-required = "num-cpus"
|
|
|
|
# CI profile: emits JUnit XML (target/nextest/ci/junit.xml) so test results can be
|
|
# uploaded to Trunk for flaky-test detection.
|
|
[profile.ci]
|
|
# Run the whole suite even after a failure, so the JUnit output captures every
|
|
# failing/flaky test for Trunk instead of stopping at the first one.
|
|
fail-fast = false
|
|
|
|
[profile.ci.junit]
|
|
path = "junit.xml"
|
|
|
|
# The two-partition double-zombie model checks each saturate every core
|
|
# (stateright spawn_bfs); running them concurrently on a small CI runner
|
|
# roughly doubles both. Requiring all test threads runs them one at a
|
|
# time with the full machine each.
|
|
[[profile.ci.overrides]]
|
|
filter = 'package(personinsights-stateright) and (test(two_partitions_double_zombie_loses_acked_writes) or test(epoch_fenced_two_partitions_double_zombie_is_safe))'
|
|
threads-required = "num-cpus"
|