Merge ChangedProjectFixture and GateCommandsProjectFixture into one WorkingTreeChangesFixture #1269
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1269
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
tests/support/changed_project_fixture.rb and tests/support/gate_commands_project_fixture.rb each build a throwaway git project whose changed files a test writes. GateCommandsProjectFixture is a near subset of ChangedProjectFixture: the same seed, and writers with the same bodies under other names (write_diffed_file, write_changed_file). Two copies drift apart.
Reproduce
n/a: design duplication, nothing fails.
Approach
One fixture,
WorkingTreeChangesFixture(the name R13 and S14 give the concept). The tests of both fixtures include it. The CRC run 4 final judgment round predicted this merge at 85%. The run did not apply it, because a merge is never a CRC verdict.Origin
123ac007)VERDICT: CREATE
Work started on branch fast-batch-22: merged with the #1463 rename into WorkingTreeChangesScenario (a Scenario, because it writes disk and git).
Resolution
Done: ChangedProjectFixture and GateCommandsProjectFixture merged into one WorkingTreeChangesScenario (Scenario, because it writes disk and git; the predicted merge plus the #1463 rename).
Evidence: fast-batch-22 merged to main
5f32ca8f; commitsaf7f61df,4ae19f04(commit now fails loudly),d065d473(locals renamed). Seeds were byte-identical; write_diffed_file folded into write_changed_file. Full suite 2904 runs, 0 failures.Follow-ups: none