chore(flawd): bring config current and pin coverage to the image tree - #65
Merged
Conversation
- [coverage.per_test] auto block per current flawd defaults (flawd auto-disables it here anyway: the assert_cmd suite is subprocess-shaped and per-test attribution can't see into spawned binaries) - [test] build_command for schemata batches (compile-once; prevents batch compile failures scoring as kills) - [pare] batch-split caps per the Rust playbook - [docker] coverage_source = "image": this Dockerfile embeds the source and warm caches at /app; bind-mount coverage delivered the host target/ into the container (wrong-arch binaries on PATH broke the subprocess tests, and container builds wrote into the host cargo cache) Part of the flawd-CI dogfooding effort; the mutation gate lands separately, report-only, once rehearsed.
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
1 participant
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.
Brings
flawd.tomlup to current flawd defaults and pins container coverage to the image tree:[coverage.per_test]auto block per current flawd defaults (flawd auto-disables it here anyway: the assert_cmd suite is subprocess-shaped and per-test attribution can't see into spawned binaries)[test] build_commandfor schemata batches (compile-once; prevents batch compile failures scoring as kills)[pare]batch-split caps per the Rust playbook[docker] coverage_source = "image": this Dockerfile embeds the source and warm caches at /app; bind-mount coverage delivered the hosttarget/into the container (wrong-arch binaries on PATH broke the subprocess tests, and container builds wrote into the host cargo cache)Part of the flawd-CI dogfooding effort — validated by a full local run today (score 99.2%, 400-mutant budget). The mutation-gate workflow lands separately, report-only, once rehearsed.