Issues

• Per-shard coverage artifacts ship 8 copies of the source tree — 85.7% of the payload is text collect already has checked out

  QAtlasHub/TestShards.jl#74 · Filter by author sotashimozono opened on Aug 19, 2026
  3

• The depot cache has a 0% hit rate: N shards save the SAME key, each uploading the whole depot, and the repo quota evicts everything

  QAtlasHub/TestShards.jl#72 · Filter by author sotashimozono opened on Aug 5, 2026

• Shards precompiling into one shared depot can race, and sharding the whole fleet made it likely

  QAtlasHub/TestShards.jl#60 · Filter by author sotashimozono opened on Aug 3, 2026
  1

• A caller cannot give the shards env, or collect artifacts from them

  QAtlasHub/TestShards.jl#59 · Filter by author sotashimozono opened on Aug 3, 2026
  1

• Nothing here exercises the paths a FRESH consumer takes

  QAtlasHub/TestShards.jl#55 · Filter by author sotashimozono opened on Aug 3, 2026
  1

• Adopting this asks for write access, every secret, and an unpinned ref — and granting less fails with no log

  QAtlasHub/TestShards.jl#45 · Filter by author sotashimozono opened on Jul 31, 2026

• Compose with Pinax: a unit-testset provider, so a sharded suite reports margins instead of counts

  enhancement
  QAtlasHub/TestShards.jl#22 · Filter by author sotashimozono opened on Jul 27, 2026
  5

• Build once and distribute, instead of every shard building for itself

  cienhancement
  QAtlasHub/TestShards.jl#14 · Filter by author sotashimozono opened on Jul 27, 2026
  4