[DRE-maint] Bug#1094556: yard: FTBFS: ERROR: Test "ruby3.3" failed: cannot load such file -- rack/server

[Lucas Nussbaum]

Source: yard
Version: 0.9.36-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20250128 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>        cannot load such file -- rack/server
>      # ./lib/yard/server/rack_adapter.rb:12:in `rescue in <module:Server>'
>      # ./lib/yard/server/rack_adapter.rb:5:in `<module:Server>'
>      # ./lib/yard/server/rack_adapter.rb:4:in `<module:YARD>'
>      # ./lib/yard/server/rack_adapter.rb:3:in `<top (required)>'
>      # ./spec/server/rack_adapter_spec.rb:8:in `block (2 levels) in <top (required)>'
>      # ./spec/spec_helper.rb:123:in `block (2 levels) in <top (required)>'
>      # ------------------
>      # --- Caused by: ---
>      # LoadError:
>      #   cannot load such file -- rackup
>      #   ./lib/yard/server/rack_adapter.rb:6:in `<module:Server>'
> 
> Top 5 slowest examples (2.24 seconds, 30.5% of total time):
>   YARD::RegistryStore#save never saves as single object db if single_object_db is false
>     1.79 seconds ./spec/registry_store_spec.rb:152
>   YARD::CLI::Display wraps output with -l (defaulting to layout)
>     0.15155 seconds ./spec/cli/display_spec.rb:15
>   YARD::Registry Thread local maintains two Registries in separate threads
>     0.10264 seconds ./spec/registry_spec.rb:396
>   YARD::Registry Thread local allows setting of po_dir in separate threads
>     0.10084 seconds ./spec/registry_spec.rb:442
>   YARD::Registry Thread local allows setting of yardoc_file in separate threads
>     0.09925 seconds ./spec/registry_spec.rb:417
> 
> Top 5 slowest example groups:
>   YARD::Server::Commands::LibraryCommand
>     0.08785 seconds average (0.26356 seconds / 3 examples) ./spec/server/commands/library_command_spec.rb:4
>   YARD::CLI::Display
>     0.0701 seconds average (0.21029 seconds / 3 examples) ./spec/cli/display_spec.rb:3
>   YARD::RegistryStore
>     0.05892 seconds average (1.94 seconds / 33 examples) ./spec/registry_store_spec.rb:3
>   YARD::Templates::Engine::Template__build_reproducible_path_yard_0_9_36_templates_default_module
>     0.03549 seconds average (0.24845 seconds / 7 examples) ./spec/templates/module_spec.rb:4
>   YARD::Parser::C::CParser
>     0.03195 seconds average (0.57513 seconds / 18 examples) ./spec/parser/c_parser_spec.rb:3
> 
> Finished in 7.35 seconds (files took 0.80077 seconds to load)
> 1943 examples, 5 failures, 10 pending
> 
> Failed examples:
> 
> rspec ./spec/cli/server_spec.rb:200 # YARD::CLI::Server General options binds address with Rack adapter
> rspec ./spec/cli/server_spec.rb:222 # YARD::CLI::Server General options accepts -a rack to create Rack adapter
> rspec ./spec/cli/server_spec.rb:228 # YARD::CLI::Server General options defaults to Rack adapter if exists on system
> rspec ./spec/server/rack_adapter_spec.rb:13 # YARD::Server::RackMiddleware handles requests
> rspec ./spec/server/rack_adapter_spec.rb:17 # YARD::Server::RackMiddleware passes up to the next middleware on 404
> 
> /usr/bin/ruby3.3 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.3" failed: 


The full build log is available from:
http://qa-logs.debian.net/2025/01/28/yard_0.9.36-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250128;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250128&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.