Skip to content

Conversation

@flavorjones
Copy link
Contributor

rubyspec-capiext is only needed for running specs, not for building/installing Ruby. Building it as part of exts breaks --with-ext= builds because some spec extensions (e.g., digest_spec.c) depend on extension headers that aren't installed.

[Bug #21792]

@launchable-app
Copy link

launchable-app bot commented Dec 17, 2025

2/67081 Tests Failed

test/fiber/test_scheduler.rb#test_close_at_exit
Error:
TestFiberScheduler#test_close_at_exit:
Test::Unit::ProxyError: Bad file descriptor
    /home/runner/work/ruby/ruby/src/tool/lib/envutil.rb:273:in 'IO#close'
    /home/runner/work/ruby/ruby/src/tool/lib/envutil.rb:273:in 'block in EnvUtil.invoke_ruby'
    /home/runner/work/ruby/ruby/src/tool/lib/envutil.rb:272:in 'Array#each'
    /home/runner/work/ruby/ruby/src/tool/lib/envutil.rb:272:in 'EnvUtil.invoke_ruby'

test/ruby/test_io.rb#test_autoclose_true_closed_by_finalizer
Failure:
TestIO#test_autoclose_true_closed_by_finalizer [/Users/runner/work/ruby/ruby/src/test/ruby/test_io.rb:2574]:
[ruby-core:26222].
Errno::EBADF expected but nothing was raised.

[-> View Test suite health in main branch]

@flavorjones flavorjones force-pushed the flavorjones/with-ext-shared-issue-fix1 branch 2 times, most recently from 68b01b4 to d17ac27 Compare December 18, 2025 15:30
rubyspec-capiext is only needed for running specs, not for building/installing Ruby.
Building it as part of `exts` breaks `--with-ext=` builds because some spec extensions
(e.g., digest_spec.c) depend on extension headers that aren't installed.

[Bug #21792]
@flavorjones flavorjones force-pushed the flavorjones/with-ext-shared-issue-fix1 branch from d17ac27 to d661217 Compare December 19, 2025 17:32
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