Skip to content

Stress expected rows do not record the engine build that produced them #14

Open

Description

@johnml1135

The stress fixtures' expected rows do not record which engine build produced them. stress/README.md says the original parses came from master (three identical runs) and that the FLEx-style null-affix rows were later updated against a newer engine. Neither build is named, so a parity failure cannot be traced to a known baseline.

Status: open. No fixture is known to be wrong; the expected rows pass today.

What we know:

  • stress/ holds 16 fixtures whose expected output is parity, not conformance.
  • PROVENANCE.md records the conformance oracle builds, not the stress ones.
  • 16 is the count after 2 of the original 18 were removed. The README explains the removal, not the change of count.

Not known: which master commit and which later engine build produced each set of rows.

Proposed change: recover both builds from the machine history, and add a stress section to PROVENANCE.md as plain text. If a build cannot be recovered, regenerate the rows on one named build and record that instead. Add one line to stress/README.md for the 18 to 16 history.

Related: sillsdev/machine#578 (origin); #1 (witnesses); #10 (environment density).

Next: find the master commit the stress rows were captured from.

🤖 Generated with Claude Code

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