FAILURE MAP
← Case archive

FA-99332 / Distributed training aggregation / Member archive

Equal-offset shard fragments retain arrival order · case 02

Equal-offset shard fragments retain arrival order.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Rows [shard_index,worker_id,values]; sort by both keys and concatenate.

Why this case matters

A toy distributed-training contract makes replica and shard contribution rules explicit without claiming framework compatibility or performance.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
tie arrival reversed["b", "a"]["a", "b"]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗