|
|
Reliability alerts and analytics now stay within memory limits
Reliability-rate rolling evaluations previously read full project aggregates, peaking at several gigabytes and causing ClickHouse memory-lim
|
Once, Tuist
|
Testing
|
xcresult-processor-image@0.37.0
|
GitHub
|
|
|
Test runs now display runner and target errors in a dedicated Errors section
Instead of treating xctest runner errors as test failures, they are now modeled as run or target-level Errors and shown in their own card on
|
Once, Tuist
|
Testing
|
xcresult-processor-image@0.37.0
|
GitHub
|
|
|
Flaky test alerts evaluate faster on the default branch
The gate that checks whether a test has a successful, non-flaky run on the default branch used to scan millions of raw test runs per alert,
|
Once, Tuist
|
Testing
|
xcresult-processor-image@0.37.0
|
GitHub
|
|
|
Flaky-test alert validation is now backed by a fast marker lookup
The default-branch validation gate for flaky-test alerts now reads from a dedicated marker table instead of scanning raw test runs. This rep
|
Once, Tuist
|
Testing
|
xcresult-processor-image@0.37.0
|
GitHub
|
|
|
Stop reliability-rate alerts and dashboards from triggering ClickHouse out-of-memory failures
Reliability-rate flaky-test alerts were driving the production ClickHouse instance past its memory ceiling, which in turn killed unrelated a
|
Once, Tuist
|
Testing
|
xcresult-processor-image@0.37.0
|
GitHub
|
|
|
Surface xctest runner errors as a dedicated Errors section on test runs
xctest runner failures (e.g. .xctest bundle could not be loaded, app could not launch) are no longer masquerading as test cases. The process
|
Once, Tuist
|
Testing
|
xcresult-processor-image@0.37.0
|
GitHub
|
|
|
Fix deploy blocked by validated-on-branch backfill
Server deploys no longer fail because of a long-running migration backfill. The test_case_runs_validated_on_branch migration now creates onl
|
Once, Tuist
|
Testing
|
server@1.226.2
|
GitHub
|
|
|
Flaky-alert validation now reads from a marker table instead of scanning raw runs
The flaky-alert validation gate now uses a dedicated marker table to check whether a test case has passed on the default branch. The marker
|
Once, Tuist
|
Testing
|
server@1.226.2
|
GitHub
|
|
|
Stop blocking server deploys on the flaky-alert validation backfill
Fix that unblocks a server deploy by removing the long-running historical backfill from the new ClickHouse marker-table migration. The previ
|
Once, Tuist
|
Testing
|
server@1.226.2
|
GitHub
|
|
|
Faster, more stable flaky-alert validation under load
The server's flaky-alert validation no longer scans every test run to determine which triggered test cases are proven on the default branch.
|
Once, Tuist
|
Testing
|
server@1.226.1
|
GitHub
|
Hive