|
|
Suite-level shard planning uses real per-suite timing
Selective test runs with suite-level sharding now fan out across the right number of shards. The historical timing lookup now joins suite ru
|
Tuist
|
Compute
|
server@1.219.3
|
GitHub
|
|
|
Suite-level test sharding now distributes shards using correct per-suite timing
Splits based on individual test suites were collapsing into a single shard even when the configured per-shard duration target should have pr
|
Tuist
|
Compute
|
server@1.219.3
|
GitHub
|
|
|
Runner-cache builds fall back to public cache when a Kura node becomes unready
When a private Kura (module cache) node was reachable but its /ready probe was failing, builds kept being routed to that dead endpoint and t
|
Tuist, Kura
|
Compute, Kura
|
xcresult-processor-image@0.30.2
|
GitHub
|
|
|
Runner-cache dispatch falls back to the public cache when a Kura node goes unready
When a private Kura cache node stops being ready, CI builds and macOS runner builds no longer time out trying to download modules. The runne
|
Kura, Tuist
|
Kura
|
xcresult-processor-image@0.30.2
|
GitHub
|
|
|
Kura runner-cache failures now fall back to the public cache instead of timing out
When a Kura cache node's readiness probe started returning 503 (for example, during a wedged cross-region replication mesh), builds kept bei
|
Kura, Tuist
|
Kura, Compute
|
server@1.219.2
|
GitHub
|
|
|
Runner-cache builds now fall back to the public cache when a private Kura node is unready
Fixed a bug where builds were routed to a dead private cache endpoint when the underlying Kura node went unready, causing module-cache downl
|
Kura, Tuist
|
Kura, Compute
|
server@1.219.2
|
GitHub
|
|
|
Kura now refuses to serve truncated artifact files
To prevent silent data corruption, the artifact serving path now verifies the backing segment or blob file covers the declared range before
|
Kura, Tuist
|
Kura
|
kura@0.10.11
|
GitHub
|
|
|
Fix Kura replication mesh deadlocks and speed up fresh-node bootstrap
The Kura replication mesh no longer deadlocks during a full-mesh cold-start. Previously, a 30-second total request timeout could abort large
|
Kura, Tuist
|
Kura
|
kura@0.10.11
|
GitHub
|
|
|
Report Oban job failures to Sentry only after all retries are exhausted
Hive now waits until an Oban job exhausts all of its retry attempts before reporting the failure to Sentry. Previously, a first-attempt time
|
Hive
|
Hive
|
0.35.1
|
GitHub
|
|
|
Only report Oban job failures to Sentry after all retries are exhausted
Hive now only reports Oban background job failures to Sentry after a job has exhausted all of its retry attempts, instead of reporting every
|
Hive
|
Hive
|
0.35.1
|
GitHub
|
Hive