Skip to content

Run

9 emulators 1054 tests

Results as of this run. The arrow shows each target's movement since the previous run it was tested in.

What changed in the suite this run

Suite on

ExtendDB's SQLite backend joins the run, built from the same release as the PostgreSQL one and held to the same TLS, SigV4 and IAM posture, so the storage engine is the only thing that differs between them.

A project's other builds now sit behind a disclosure on its row. Every build is measured in full and has a row of its own with its own figures; the disclosure starts closed only when every build under it reads the same grade, divergence and coverage as the row above, and only when each of them was measured in that run: a carried row on either side opens it, and so does a run the suite declined to score. It is read from each run, so a build can start closed on one and open on the next. The README table has no disclosure to offer, so it lists every build outright.

Every target in the data endpoints gains two fields. collapsedIntoProject is true when the board starts that build's row closed. standsForProject says which row the board treats as a project's own, which isVariant cannot answer: on a run where a project's reference build recorded nothing, a build is promoted to stand for it and every row of that project reads isVariant: true. Both are additive, so schemaVersion is unchanged, and /data/index.json gains a projects block documenting them.

/data/index.json also gains a schema block saying what the version number entitles a consumer to: a field you already read will not change type or meaning while schemaVersion stays put, and new fields can appear at any version. The grading criteria are named there as a separate axis, since a change to the bands changes what a letter means without the schema moving.

The coverage description said a partial run was carried forward on its last clean measurement. It is not: the row stays in the run, publishes null for both figures and reads carried: false, because the target did report. Carrying forward is what happens to the baseline's unobserved lanes. Corrected, along with Dynoxide's build label, which now names its storage (native SQLite) like every other build in the registry rather than its compile target.

  1. live (AWS)

    Runs via: AWS service

    Grade baseline

    no divergence in all 33 regions · covers 100.0% of the suite

    ground truth
    Tier breakdown
    Tier 1 · Core 0.0% diverges
    100.0% covered
    Tier 2 · Complete 0.0% diverges
    100.0% covered
    Tier 3 · Strict 0.0% diverges
    100.0% covered
  2. Runs via: npx, Docker, Homebrew, binary, npm, cargo, embedded, GitHub Action, source

    Disclosure: maintained by this board's author

    Grade A

    low divergence (0.9%) in 5 regions · up to 1.3% in the other 28 · covers 94.7% of the suite

    unchanged
    Tier breakdown
    Tier 1 · Core 2.0% diverges
    100.0% covered
    Tier 2 · Complete 0.0% diverges
    82.2% covered 40 unsupported
    Tier 3 · Strict 0.0% diverges
    95.3% covered 16 unsupported
    Also built for WebAssembly / OPFS
    • Grade B

      low divergence (0.9%) in 5 regions · up to 1.3% in the other 28 · covers 83.4% · coverage lowers this row to B

  3. Grade B

    low divergence (1.9%) in 11 regions · up to 2.1% in the other 22 · covers 87.8% of the suite · coverage lowers this row to B

    diverged 0.1 percentage points less
    Tier breakdown
    Tier 1 · Core 0.8% diverges
    100.0% covered
    Tier 2 · Complete 1.8% diverges
    51.6% covered 109 unsupported
    Tier 3 · Strict 3.5% diverges
    94.1% covered 20 unsupported
    Also built for SQLite
    • SQLite
      Grade B

      low divergence (1.8%) in 11 regions · up to 2.0% in the other 22 · covers 87.8% · coverage lowers this row to B

  4. Runs via: pip, Docker, source

    Grade B

    moderate divergence (11.9%) in 11 regions · up to 12.0% in the other 22 · covers 96.0% of the suite

    unchanged
    Tier breakdown
    Tier 1 · Core 5.7% diverges
    100.0% covered
    Tier 2 · Complete 15.1% diverges
    88.4% covered 26 unsupported
    Tier 3 · Strict 18.5% diverges
    95.3% covered 16 unsupported
  5. Grade C

    moderate divergence (12.8%) in 25 regions · up to 13.0% in the other 8 · covers 77.0% of the suite · coverage lowers this row to C

    diverged 0.2 percentage points less
    Tier breakdown
    Tier 1 · Core 10.8% diverges
    100.0% covered
    Tier 2 · Complete 12.4% diverges
    17.8% covered 185 unsupported
    Tier 3 · Strict 15.9% diverges
    83.2% covered 57 unsupported
  6. Runs via: Docker, pip, Homebrew, binary

    Grade C

    moderate divergence (14.8%) in 25 regions · up to 14.9% in the other 8 · covers 95.3% of the suite · coverage lowers this row to C

    diverged 0.1 percentage points less
    Tier breakdown
    Tier 1 · Core 6.3% diverges
    100.0% covered
    Tier 2 · Complete 16.0% diverges
    84.9% covered 34 unsupported
    Tier 3 · Strict 26.2% diverges
    95.3% covered 16 unsupported
  7. Grade C

    high divergence (15.1%) in 25 regions · up to 15.2% in the other 8 · covers 94.0% of the suite

    diverged 0.1 percentage points less
    Tier breakdown
    Tier 1 · Core 7.6% diverges
    100.0% covered
    Tier 2 · Complete 14.2% diverges
    79.1% covered 47 unsupported
    Tier 3 · Strict 26.5% diverges
    95.3% covered 16 unsupported
  8. Runs via: Docker, Homebrew, install script, Scoop, binary, JAR

    Grade C

    high divergence (21.0%) in 11 regions · up to 21.2% in the other 22 · covers 95.2% of the suite

    unchanged
    Tier breakdown
    Tier 1 · Core 10.8% diverges
    100.0% covered
    Tier 2 · Complete 32.4% diverges
    84.4% covered 35 unsupported
    Tier 3 · Strict 27.9% diverges
    95.3% covered 16 unsupported