How it got here
Dynoxide (wasm)'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
Coverage
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.
-
PutItem - index write capacity reports the LSI write and folds it into the total
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
PutItem - index write capacity reports both arms when a write touches both index kinds
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
PutItem - index write capacity charges an identical overwrite no index writes at all
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
UpdateItem - index write-capacity ladder charges nothing on the index for a non-projected attribute
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:46
-
UpdateItem - index write-capacity ladder charges one index write for a projected non-key attribute
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
UpdateItem - index write-capacity ladder charges two index writes for a key change: delete plus insert
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
UpdateItem - index write-capacity ladder charges one index write to remove the key: delete only
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
UpdateItem - index write-capacity ladder walks the same ladder on the LSI key
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
DeleteItem - index write capacity charges one write per index the item occupied
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43
-
DeleteItem - index write capacity charges only the table write for a sparse item
Tier 1 putItem tests/tier1/putItem/indexConsumedCapacity.test.ts:43