spec/console/output_spec.rb fails under some environment

I've tried to build ruby-console Debian package and its test failed with some tools like git-buildpackage + cowbuilder (build deb package under chroot). But this ./spec/console/output_spec.rb file runs fine with manual exec. I'm not sure, but something wrong with the prerequisite for TTY or so.

┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.7 from debian/ruby-tests.rake                            │
└──────────────────────────────────────────────────────────────────────────────┘

RUBYLIB=. GEM_PATH=/build/ruby-console-1.13.1/debian/ruby-console/usr/share/rubygems-integration/all:/build/ruby-console-1.13.1/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation
{"time":"2021-09-01T12:56:02+00:00","severity":"info","class":"String","oid":1960,"pid":25639,"subject":"Dear maintainer:","message":"Once you are done trying to 'optimize' this routine, and have realized what a terrible mistake that was, please increment the following counter as a warning to the next guy:\ntotal_hours_wasted_here = 42\n"}
{"time":"2021-09-01T12:56:02+00:00","severity":"warn","class":"String","oid":1980,"pid":25639,"subject":"Something didn't work as expected!"}
{"time":"2021-09-01T12:56:02+00:00","severity":"error","class":"String","oid":2000,"pid":25639,"subject":"There be the dragons!","arguments":["Bits have been rotated incorrectly!"]}
{"time":"2021-09-01T12:56:02+00:00","severity":"info","class":"Module","oid":2020,"pid":25639,"subject":"MyModule","message":"#<Console::Event::Spawn:0x0000563851c19898>"}
{"time":"2021-09-01T12:56:02+00:00","severity":"info","class":"Object","oid":2040,"pid":25639,"subject":"#<Object:0x0000563851c18d08>","message":"Where would we be without Object.new?"}

Console::Capture
  #buffer
    can access log buffer

(snip)
Console
  has a version number

Failures:

  1) Console::Output.new when output to $stderr should set the default to Terminal::Logger
     Failure/Error: expect(Console::Output.new($stderr)).to be_a Console::Terminal::Logger
       expected #<Console::Serialized::Logger:0x0000563851e8d200 @io=#<IO:<STDERR>>, @start=2021-09-01 12:56:02.506641128 +0000, @format=JSON, @verbose=false> to be a kind of Console::Terminal::Logger
     # ./spec/console/output_spec.rb:33:in `block (4 levels) in <top (required)>'

Finished in 0.03638 seconds (files took 0.10485 seconds to load)
61 examples, 1 failure

Failed examples:

rspec ./spec/console/output_spec.rb:32 # Console::Output.new when output to $stderr should set the default to Terminal::Logger

Could you give me any suggestions, please?

socketry / console

spec/console/output_spec.rb fails under some environment #26