Skip to content

test(search-eval): corpus chunk count stale after #2256 (declared 1993, observed 2002) #2275

Description

@ScriptedAlchemy

On a tree at 24eef04, tracedecay-search-eval lib fails 11 tests deterministically, whether run by cargo test or directly:

candidate_output.rs:2550: generate: Contract("eligible chunk count mismatch for 1x corpus: declared 1993, observed 2002")

Failing tests: candidate_output::tests::{candidate_bytes_match_direct_production_calls, direct_outputs_cover_train_and_validation, historical_candidates_require_product_repository_identity, published_corpus_maps_production_source_occurrences, query_phrase_and_historical_queries_reach_their_checked_in_anchors, resource_evidence_enforces_state_and_exact_catalog_without_size_caps, scoped_projections_partition_chunks_into_every_admitting_scope_set_only}, packaged_assets::tests::packaged_evaluator_compares_the_fallback_profile_from_its_own_root, and report_tests::{baseline_report_is_self_validating_and_refuses_conceptual_misses, baseline_report_retains_raw_fallback_current_and_exact_ten_x_samples, direct_report_is_evidence_only_and_owns_its_candidate_schema}.

The same suite passed at 6a4635f (#2243). In between, #2256 changed extraction ("resolve cfg variants and item-list macro bodies"), which plausibly yields the 9 extra eligible chunks. The declared corpus count, or the extraction change, needs reconciling.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions