Skip to content

ci: classify Bazel-mapped crate test-data before binding crate globs #474

Description

@DecisionNerd

Summary

In scripts/ci/classify-changes.sh, the crates/graphforge-api/* | crates/graphforge-bindings-py/* | crates/graphforge-bindings-node/* arm precedes the Bazel-mapped test-data arm (crates/*/tests/*goldens/*, **/*.snap, fixtures, corpus). A change such as crates/graphforge-api/tests/fixtures/x.json currently sets only bindings=true and skips the authoritative Rust/Bazel suite.

Acceptance criteria

  • Bazel-mapped test-data arm is evaluated before the three binding crate globs
  • Paths under those crates' goldens/fixtures/corpus/snaps still set rust=true and bazel=true
  • Binding crates' test-data also keep bindings=true when appropriate (binding suites may consume it)
  • Regression cases in scripts/ci/test-classify-changes.sh (at least crates/graphforge-api/tests/fixtures/x.json → rust+bazel)

Non-goals

  • Broader classifier redesign
  • Suite-membership / pin / timeout work

Source

Devinfra Audit Recheck Wave E / PR-C

Validation

  • bash scripts/ci/test-classify-changes.sh

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions