All issues

Search results

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

Status: Open.

#74 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Aug 19, 2026

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

Status: Open.

#72 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Aug 5, 2026

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

Status: Open.

#60 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Aug 3, 2026

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

Status: Open.

#59 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Aug 3, 2026

Nothing here exercises the paths a FRESH consumer takes

Status: Open.

#55 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Aug 3, 2026

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

Status: Open.

#45 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Jul 31, 2026

After registration: what runs automatically, what to do by hand, and what changes from now on

chore

ci

Status: Open.

#43 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Jul 29, 2026

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

enhancementNew feature or requestNew feature or request

Status: Open.

#22 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Jul 27, 2026

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

ci

enhancementNew feature or requestNew feature or request

Status: Open.

#14 In QAtlasHub/TestShards.jl;

· sotashimozono opened on Jul 27, 2026