Created Started Cancelled
By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Leave a child without a baseline file when the run has none An empty baseline map is not the same as no baseline map. A child reorders its covering tests cheapest-first whenever it finds a map, and a map with no costs is not order-preserving: 'reorderTestForestByTiming' scores a pending or leafless node 'maxBound', so those sort last while every leaf sorts equal. The previous commit read the run's baselines with a 'fromMaybe mempty' and wrote a file unconditionally, so a run whose augmented-manifest directory holds no baselines started reordering its children's forests. Both callers in this repository write baselines before the mutation phase, so nothing in it was affected, but the child's own rule -- no map, no reordering -- is worth keeping exactly.