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

ci: update suppression to match new stack trace in Ruby 3.4-dev #3291

Merged
merged 1 commit into from
Jul 15, 2024

Conversation

flavorjones
Copy link
Member

What problem is this PR intended to solve?

I think the stack trace changed with ruby/ruby@51bd8165, see for example https://github.com/sparklemotion/nokogiri/actions/runs/9935752042/job/27442553528

I'm not sure why this is the only leak showing up now, but am deferring further study until I devote some time to cleaning up known leaks where we raise exceptions in Ruby callbacks (from libxml2), see #2096 and #1610

I think the stack trace changed with ruby/ruby@51bd8165.

I'm not sure why this is the only leak showing up now, but am
deferring further study until I devote some time to cleaning up known
leaks where we raise exceptions in Ruby callbacks (from libxml2).
@flavorjones
Copy link
Member Author

@flavorjones flavorjones merged commit 2d0afb8 into main Jul 15, 2024
148 checks passed
@flavorjones flavorjones deleted the flavorjones-update-suppression branch July 15, 2024 15:23
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.

1 participant