Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix pilcom proof fail test functions #2558

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

qwang98
Copy link
Collaborator

@qwang98 qwang98 commented Mar 18, 2025

Depends on #2535 and #2557. Split assert_proofs_fail_for_invalid_witnesses_pilcom into assert_proofs_fail_for_invalid_witnesses_pilcom_composite and assert_proofs_fail_for_invalid_witnesses_pilcom_monolithic. These two APIs are needed because we might generate different witnesses for pilcom composite vs pilcom monolithic under two scenarios:

  1. The two backends can have different witnesses to start with. This hasn't been an issue because most of our test cases are very simple machines.
  2. After updates in PoC for two passes of pilopt #2535, if we eventually implement different optimizations for the two different backends, they might compute two different witnesses.

@qwang98 qwang98 requested a review from Schaeff March 18, 2025 11:36
@qwang98 qwang98 marked this pull request as ready for review March 18, 2025 11:36
@Schaeff Schaeff merged commit 33f767c into split-with-backend Mar 18, 2025
16 checks passed
@Schaeff Schaeff deleted the pilcom-proof-fail-test branch March 18, 2025 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants