Skip to content

fix(tests): skip vernier on Ruby head due to compilation issues#2856

Closed
mjq wants to merge 1 commit intomasterfrom
fix-ruby-head-vernier-issue
Closed

fix(tests): skip vernier on Ruby head due to compilation issues#2856
mjq wants to merge 1 commit intomasterfrom
fix-ruby-head-vernier-issue

Conversation

@mjq
Copy link
Member

@mjq mjq commented Feb 17, 2026

It seemed better to me to temporarily skip vernier on Ruby head so that we still get the actual test runs, rather than have them fail upfront when vernier fails to load.


Summary

  • Skip loading the vernier gem on Ruby head (>= 4.1) to fix test failures
  • The vernier gem's native extension currently fails to compile on Ruby head (4.1.0+1)

Root Cause

The vernier gem (v1.9.0) has a native C extension that fails to load on Ruby head:

LoadError: cannot load such file -- /path/to/gems/vernier-1.9.0/lib/vernier/vernier

This was causing all "Ruby head" test matrix runs to fail on master.

Solution

Updated sentry-ruby/spec/spec_helper.rb to skip requiring vernier when RUBY_VERSION >= "4.1".

This is a temporary workaround until vernier is updated to support Ruby 4.1 development versions.

Test Plan

✅ All existing tests on Ruby 2.7 - 4.0 should continue to pass (vernier still loads)
✅ Ruby head tests should now pass (vernier is skipped)

Fixes the Ruby head test failures seen in #2855 and on master branch.

🤖 Generated with Claude Code

The vernier gem (v1.9.0) fails to load its native extension on Ruby
head (4.1.0+1). Skip loading vernier on Ruby >= 4.1 until the gem
is updated to support the development Ruby version.

This fixes the test failures for Ruby head with Rack 2, 3, and 3.1.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@mjq mjq force-pushed the fix-ruby-head-vernier-issue branch from 299e9c1 to 0b1a0a2 Compare February 17, 2026 17:54
@mjq mjq closed this Feb 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments