Source: ruby-delayed-job-active-record
Version: 4.1.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-delayed-job-active-record with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>      Failure/Error:
>        expect do
>          YAML.load(Story.create.to_yaml)
>        end.not_to raise_error
> 
>        expected no Exception, got #<Psych::DisallowedClass: Tried to load 
> unspecified class: Story> with backtrace:
>          # ./spec/delayed/serialization/active_record_spec.rb:8:in `block (3 
> levels) in <top (required)>'
>          # ./spec/delayed/serialization/active_record_spec.rb:7:in `block (2 
> levels) in <top (required)>'
>      # ./spec/delayed/serialization/active_record_spec.rb:7:in `block (2 
> levels) in <top (required)>'
> 
> Finished in 1.4 seconds (files took 0.51816 seconds to load)
> 101 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/delayed/serialization/active_record_spec.rb:6 # ActiveRecord 
> loads classes with non-default primary key
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-delayed-job-active-record/ruby-delayed-job-active-record_4.1.6-3+rebuild1663007492_amd64-2022-09-12T18:31:33Z.build

To reproduce this, you need ruby-all-dev >= 1:3.0+2.  Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

Attachment: signature.asc
Description: PGP signature

Reply via email to