FAILURE MAP
← Case archive

FA-99263 / Distributed training aggregation / Member archive

All-gather output follows arrival order · case 03

All-gather output follows arrival order.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Given rank-tagged payloads and world size, return payloads in rank order; missing ranks are omitted and duplicate rank uses last listed payload.

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
arrival shuffled["c", "a", "b"]["a", "b", "c"]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 ↗