Skip to content

Check claims in the extension conformance harness - #11604

Draft
connortsui20 wants to merge 3 commits into
ct/ext-claim-checksfrom
ct/ext-claim-conformance
Draft

connortsui20 wants to merge 3 commits into
ct/ext-claim-checksfrom
ct/ext-claim-conformance

Conversation

@connortsui20

@connortsui20 connortsui20 commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

The dtype constructor can only check that the storage dtype holds each declared claim. It can't tell whether a claim is true, for example when the storage orders two values differently from the values themselves. The conformance harness now takes a reference order from the caller and compares every pair of fixture values against it, which catches a claim that the storage doesn't keep.

Stacked on #11600. The diff also includes the validation harness from #11601 that this builds on.

AI assisted with this change.

Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
@connortsui20 connortsui20 added the changelog/skip Do not list PR in the changelog label Nov 18, 2026
@connortsui20
connortsui20 force-pushed the ct/ext-claim-conformance branch 2 times, most recently from b6e305c to c573ef6 Compare November 18, 2026 18:21
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>

This branch has not been deployed

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

Labels

changelog/skip Do not list PR in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant