Skip to content

Partition Intel conformance after one same-run construction #449

Closed

Description

@afflom

Release/v0.4's full CI run 42647185072 for #444 passed 44 jobs but cancelled Intel macOS at its unchanged 240-minute limit, after 401/478 conformance cases had passed. Repeating the monolith or raising its timeout is not a useful qualification strategy.

Implement a bounded Intel-only execution split while retaining the other three supported-host jobs unchanged:

  • Construct the exact locked, all-feature workspace test products once on Intel. Execute every ordinary/library/meta/future non-conformance harness and all workspace doctests on that producer.
  • Transfer only the conformance executable and its measured runtime library closure, plus dependency data needed by offline nested tests. Restore the exact checked-out source at the original absolute path. Never transfer credentials or a whole home directory.
  • Group existing BDD ownership parts into four disjoint execution lanes. Prove their union against the actual harness inventory, retaining ignored-test semantics and all current/future tests. Continue after failures and aggregate them.
  • Bind construction and results to repository, checked-out source/tree, same run/attempt, native target, pinned toolchain, profile/features/lock, plan/inventory, artifact hashes and exact invocations. Reject missing, duplicate, foreign, failed or incomplete parts.
  • Retain exactly four existing supported-host aggregate status names. Update SPEC §8.3 and RP-13/RP-14/RP-18/release evidence checks together, with focused negative tests.

This is execution scheduling, not cross-run caching or evidence reuse. #448 separately removes unused BS-07 preparation; it does not establish that the Intel timeout is fixed. Keep #442's count-writer ownership and #405's forward-integration ownership unchanged. Final runtime qualification must run real Intel artifact/loader/offline behavior and one combined final release gate; local unit tests or a draft run do not establish completion or a measured speedup.

Activity

  1. afflom commented on Nov 10, 2026

    @afflom
    MemberAuthor

    Completed in #450, merged into release/v0.4 as cf76090. The actual landed tree is 0c24b969dcc5c02d9afb7616f97736827b7b09e6, exactly the reviewed and fully tested tree. Full CI https://github.com/UOR-Foundation/LexLean/actions/runs/42710839907 passed all 50 expected jobs; exact-head reproducibility https://github.com/UOR-Foundation/LexLean/actions/runs/42710413660 passed. Independent Intel receipt review verified actual native execution and complete coverage of all 478 conformance cases. No gate, test coverage, timeout or protection was weakened. Forward integration remains in #405.

  2. added this to the LexLean v0.4.1 milestone on Nov 10, 2026
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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions