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

YJIT: Fix assert_no_exits #8579

Merged
merged 1 commit into from Oct 2, 2023
Merged

YJIT: Fix assert_no_exits #8579

merged 1 commit into from Oct 2, 2023

Conversation

k0kubun
Copy link
Member

@k0kubun k0kubun commented Oct 2, 2023

Currently, assert_no_exits tests nothing since exits.all? { |k, v| v === recorded_exits[k] } is true when exits is empty.

This PR changes it to also check their keys so that it will fail when exits is empty but recorded_exits is not.

@matzbot matzbot requested a review from a team October 2, 2023 20:25
@k0kubun k0kubun merged commit 492e943 into ruby:master Oct 2, 2023
93 checks passed
@k0kubun k0kubun deleted the yjit-no-exits branch October 2, 2023 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants