Skip to content

Kumo on

7b15ae8b6e4b as measured in this run

Grade F
severe divergence
answers 44.7% of the suite differently from real DynamoDB
67.6% covered · 623 unsupported
Tier 1 · Core 46.9% diverges
100.0% covered
238 of 507 attempted
Tier 2 · Complete 11.1% diverges
23.6% covered 407 unsupported
59 of 126 attempted
Tier 3 · Strict 63.7% diverges
75.5% covered 216 unsupported
561 of 664 attempted

How it got here

Kumo's history up to this run, ending on the figures above. Both are plotted because neither reads correctly alone: divergence falls when a target stops attempting an operation it used to get wrong, so a fall in the first plot is only an improvement if the second one holds. The target's own page carries the full history.

Divergence

Kumo divergence up to 2026-11-15 0% 25% 50% divergence - lower is better 20 Sep 29 Sep 9 Oct 11 Oct 18 Oct 22 Oct 25 Oct 27 Oct 2 Nov 8 Nov 15 Nov 44.7%
Diverging on 44.7% of the suite as of 15 Nov, at worst 45.2% on 20 Sep. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Kumo coverage up to 2026-11-15 65% 83% 100% coverage - higher is better 20 Sep 29 Sep 9 Oct 11 Oct 18 Oct 22 Oct 25 Oct 27 Oct 2 Nov 8 Nov 15 Nov 67.6%
Implementing 67.6% of the suite as of 15 Nov. Higher is better. This is the share of the suite's tests a target implements at all. A fail becoming a skip leaves both numerators over the same fixed denominator, so a fall here is matched point for point by a fall in divergence: withdrawal costs exactly as much coverage as it gains divergence.

Where it fell short on this date

The tests this run recorded as failing, each linked to its source at the commit that measured it. For the current picture, see this target's latest results, or every target in this run.