Repository navigation
Conversation
- Assign release-schedule unit test to the workflows area - Drop removed JS repository discovery from inventory ingestion test - Assert the removed validation report job stays absent - Verify only the remaining dashboard runtime bundle - Remove the CI job for the deleted issueOrPullRequest test Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Use control.mjs control-settings instead of activity/control-settings.mjs, drop the activity/cao.mjs smoke check, and assert only surviving runtime files. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The massive-scale stress test now normalizes synthetic shards in-process through dashboard/report/normalized-payloads.mjs, the production module the retired command wrapped. Also import the stat helper the test already used, and drop the stale hash-payloads step from the Value event-ledger reference. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
PostgreSQL timestamptz stores microseconds and rounds, so a nanosecond retry time (Linux clocks) never round-trips. The fencing test failed deterministically on CI comparing RetryAt; fencing itself was correct. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…edundant fixtures Since the SQLite removal, every testutil.Postgres fixture provisions a full canonical store (~360 daily partitions, ~5s), pushing internal/server past the 10m go test timeout. Provision one template database per test process through the production store and clone it per test (CREATE DATABASE ... TEMPLATE), falling back to a private schema when the role cannot create databases. Reclaim databases left by exited processes. Also share one app across TestSessionArchiveResponseClosesReader subtests and stop re-executing repository queries already covered by the full dashboard corpus test. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The storage shard timeout log showed only the test running at the 10m deadline, not which tests consumed the budget. Run Go unit tests with -v so every shard log records per-test durations and the next slow shard can be attributed directly. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the failing
Workflow contractsrun on main (run 43253801007), caused by #20648, #20651 and #20690.release-schedule.test.mjsnow belongs to theworkflowsarea inscripts/run-unit-area.mjs.dashboard-inventory-ingestionno longer imports the deleted JSdiscoverRepositories. Repository discovery now runs natively in Go, so the test passes discovered repositories as explicit inputs.reportjob stays absent.dashboardruntime bundle because theactivitybundle was retired. The same change is applied tocampaign-lifecycle.The
CAO efficiencyfailure is an agentreport_incompleteresult (tracked in #20653), not a code failure.