Skip to main content

Foundational libraries

mgf-test-supervisor

A budget-aware, crash-survivable supervisor that drives pytest from the outside, so a hung or crashed test is recorded as an outcome instead of vanishing.

What it is

A test supervisor that runs pytest as a subprocess rather than living inside it as a plugin, so an interpreter deadlock or a crash in a native extension is named as an outcome instead of taking the whole run down with it, and a test that will not exit is flagged rather than left to hang. It packs a run into a wall-clock budget, resumes an interrupted run without repeating finished tests, quarantines flaky tests automatically and writes a self-contained diagnostic bundle for each failure. It is the federation's standard test infrastructure, which is why a green suite here means something.

It belongs to Foundational libraries — the floor everything else stands on. That cluster states its own boundaries on the work page, including what it deliberately does not own.

State

Status
Active development
Registered version
0.1.21
Category
foundational library
Cluster
Foundational libraries
Release wave
1
Language recorded
python

Versions shown here are the versions the registry records for the working tree. The package index is the publication contract, and the two are not guaranteed to agree — the index is what an install command actually resolves against. recorded at build · 2026-09-04

A project page is one row of the federation registry, read at build: the registered version, the projects it depends on, and the projects that depend on it — all of them the registry's own values. recorded at build · 2026-09-16

how it connects

Relations

Declared dependencies, by scope

Declared dependents, by scope

  • hrb-app optional
  • mgf-alembic optional
  • mgf-apiprobe optional
  • mgf-auth optional
  • mgf-brand-qt optional
  • mgf-brand-web optional
  • mgf-cloud optional
  • mgf-cloud-provision optional
  • mgf-cloud-web optional
  • mgf-coach optional
  • mgf-coach-qt optional
  • mgf-common optional
  • mgf-django optional
  • mgf-fastapi optional
  • mgf-fed optional
  • mgf-fed-web optional
  • mgf-fedres optional
  • mgf-hrb optional
  • mgf-http optional
  • mgf-livepush optional
  • mgf-logship optional
  • mgf-secrets optional
  • mgf-sqlalchemy optional
  • mgf-tele-core optional
  • mgf-tele-teltonika optional
  • mgf-uitest-desktop optional
  • mgf-uitest-web optional
  • mgf-vm-core optional
  • mgf-vm-firecracker optional
  • mgf-vm-forensics optional
  • mgf-vm-interchange optional
  • mgf-vm-libvirt optional
  • mgf-vm-sdk optional
  • ProofWarden runtime
  • TelePlasma optional
  • VManager optional
Left: what mgf-test-supervisor depends on. Right: what depends on it. The map draws at most 6 per side — 30 further dependents are named in the lists above. The lists name every relation this site publishes. A further 1 is a registry entry this site does not publish: counted here, never named. Relations are read from mgf-libraries.json, synced from mgf-standard at 87915ba on 2026-09-16.

A project's release wave is its position in the dependency order recorded upstream — a barrier that says what must be published first, never a date. recorded at build · 2026-09-16

under the hood

Engineering
Third-party packages declared
0
Optional extras
dev · standards
Requires Python
>=3.11

The registry records a direct third-party declaration count for each project. This site can sum those row counts, but it does not have the names needed to deduplicate them or describe a resolved installation. recorded at build · 2026-09-16

The rule families it is measured against

mgf-test-supervisor answers to the same corpus every registered project does: 323 anchored rules in 25 families, of which 313 are binding. This is the corpus, not a score — nothing on this page claims a conformance result for mgf-test-supervisor, because no durable per-project record of one is published. The corpus, family by family →

Counted from mgf-rules-index.json, synced from mgf-standard at 169b511 on 2026-09-04.

Every registered project is measured against the same corpus: the rule families, their sizes, and how many of their rules are binding come from the standard's own machine-readable index, not from prose about it. recorded at build · 2026-09-04

the record

Evidence

Read the declared runtime graph

Inside mgf-test-supervisor's declared runtime graph

  • mgf-test-supervisor itself.
  • no other Magogi library in its declared runtime graph. Optional and test declarations may still appear in the relations above.
  • no third-party declarations on mgf-test-supervisor or the rows in its declared runtime graph. This does not describe what a package resolver would install.

Outside this graph

  • the other 53 published components are not reached by these declared runtime relationships. The explorer counts the same graph. This graph is a registry model, not a package-resolver result.
  • anything from these clusters: VManager — the virtual-machine stack · Hardware resource broker · Telematics · Cloud & cost · Fleet engineering practice · Applications & ventures
  • a hosted service, an account, or a runtime the Foundation operates for you.

The design rules require a third-party dependency that performs input or output to sit behind an interface with both a production and a test implementation. The rule states the required design; the registry's dependency counts do not verify implementation conformance. recorded at build · 2026-09-04

A project's declared runtime graph, and what stays outside it, is computed only from registry edges scoped as runtime. Optional and test declarations remain outside that view; the graph is not a resolved installation. recorded at build · 2026-09-16