Skip to content

test(blockifier): test secp_get_point_from_x #6366

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

Open
wants to merge 1 commit into
base: aner/snos_secp_syscalls
Choose a base branch
from

Conversation

aner-starkware
Copy link
Contributor

No description provided.

@aner-starkware aner-starkware self-assigned this May 7, 2025
@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link

github-actions bot commented May 7, 2025

@aner-starkware aner-starkware changed the base branch from main to aner/snos_secp_syscalls May 7, 2025 11:39
@aner-starkware aner-starkware changed the title Aner/test new point x coordinate test(blockifier): test secp_get_point_from_x May 7, 2025
Copy link
Collaborator

@dorimedini-starkware dorimedini-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @ilyalesokhin-starkware)


crates/blockifier_test_utils/resources/feature_contracts/cairo1/test_contract.cairo line 401 at r1 (raw file):

        assert(x_coord == x && y_coord == expected_y, 'Unexpected coordinates');
        let (x_coord, y_coord) = starknet::secp256k1::secp256k1_get_xy_syscall(p1).unwrap_syscall();
        assert(x_coord == x && y_coord != expected_y, 'Unexpected coordinates');

why not define an expected_p1_y value?

Code quote:

y_coord != expected_y

@aner-starkware aner-starkware force-pushed the aner/snos_secp_syscalls branch from 9a509b6 to fdf37da Compare May 7, 2025 15:05
@aner-starkware aner-starkware force-pushed the aner/test_new_point_x_coordinate branch from f59dde3 to af88988 Compare May 7, 2025 15:18
@aner-starkware aner-starkware force-pushed the aner/test_new_point_x_coordinate branch from af88988 to 9f9a210 Compare May 7, 2025 15:21
@aner-starkware
Copy link
Contributor Author

crates/blockifier_test_utils/resources/feature_contracts/cairo1/test_contract.cairo line 401 at r1 (raw file):

Previously, dorimedini-starkware wrote…

why not define an expected_p1_y value?

Done.

Copy link
Collaborator

@dorimedini-starkware dorimedini-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 4 of 4 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @ilyalesokhin-starkware)

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.

3 participants