Repository navigation
Explain duplicate checks and regression candidates in run history - #977
Merged
Merged
Conversation
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Build this guide with the documentation application used by previews. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Fenced memory inserts require a lease table in the selected schema. Give each fixture database its own Keeper root while preserving the replicated content checks. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The fixture repair is on main. Its standalone regression remains in #1077; the feature diff retains its original tests. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The documentation branch needs the shared workflow checks and checkout credential controls before its final CI qualification. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.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.
Changelog category
Changelog entry
Explain duplicate bug checks and regression candidate ranking in the run-history guide and its agent-readable summary.
Why
The run-history opening describes recording but omits duplicate checking and regression candidate ranking. It also asks which change introduced a regression without distinguishing candidates from proof.
Scope and risk
State both existing capabilities in the opening and its generated
llms.txtentry. Keep the recording switches, registered tracker and namespace access prerequisites explicit. Link the existing bug-draft walkthrough and state that ranking neither runs a bisect nor proves causation.The documentation changes the use-case opening, factual search title/description and corresponding agent-readable summary. The metadata names run history, duplicate checks and regression candidates without claiming proven causation. The existing operation details, measurements and setup links remain. There are no API, storage, permission, provider, package or generated translation changes.
Compatibility, rollout and rollback
Tests
llms.txtentry from this page; all other entries are unchanged.The prior
b22f161471full CI failed during the initial memory write in an integration fixture, before its restore step. The cancellation cause remains unestablished. The metadata is not claimed as a fix; the fixture prerequisite below resolves a separate diagnosed missing-table failure. Complete new-head CI is required. No unchanged-head CI rerun was requested.Main includes the replicated-erasure fixture's lease-table repair from #1076. This PR uses main's exact fixture and changes no test or erasure source; the standalone fixture regression remains in #1077. The use-case page and this PR's
llms.txtrow match the previously reviewed feature; all other index rows are inherited from main. Full CI and fresh independent reviews must qualify this new composition.The
c057f2f592composition failed the existing Python lane-linearity check; its largest sample did not finish. The translations check passed in that job. No parser, timing guard or parse limit changes here, and this main composition is not claimed as a repair.AI assistance in the code
AI-generated: Codex drafted the wording and checked it against the tracker and PR-history documentation.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist