Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #306312 > unrolled thread

Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:      RuntimeError: Antonio Terceiro <terceiro@debian.org> - 2021-10-15 02:10 +0200
    Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Diederik de Haas <didi.debian@cknow.org> - 2021-10-22 10:00 +0200
    Processed: Re: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0"  failed: RuntimeError: "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-10-22 10:00 +0200
    Bug#996529: marked as done (vagrant: FTBFS with ruby3.0: ERROR:  Test "ruby3.0" failed:      RuntimeError:) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-11-15 14:00 +0100

#306312 — Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

[Multipart message — attachments visible in raw view] — view raw

Source: vagrant
Version: 2.2.14+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-ruby@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, vagrant was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
>      RuntimeError:
>        class variable access from toplevel
>      # /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:10:in `block (3 levels) in <top (required)>'
>      # /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in `initialize'
>      # /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in `new'
>      # /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in `block (2 levels) in <top (required)>'
>      # /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:34:in `block (4 levels) in <top (required)>'
> 
> Finished in 14 minutes 32 seconds (files took 5.03 seconds to load)
> 2824 examples, 7 failures, 9 pending
> 
> Failed examples:
> 
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/commands/cloud/provider/upload_test.rb:88 # VagrantPlugins::CloudCommand::ProviderCommand::Command::Upload#upload_provider with direct option should use direct upload
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/commands/cloud/search_test.rb:59 # VagrantPlugins::CloudCommand::Command::Search#search with valid options should use options when performing search
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/commands/cloud/search_test.rb:72 # VagrantPlugins::CloudCommand::Command::Search#search with valid options with invalid options should only pass supported options to search
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/kernel_v2/config/disk_test.rb:120 # VagrantPlugins::Kernel_V2::VagrantConfigDisk#add_provider_config normalizes provider config
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:21 # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with no override should split options into individual options
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:28 # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with overrides should merge all options
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:33 # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with overrides should override options defined in base
> 
> /usr/bin/ruby3.0 -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 test/unit/\{plugins\}/\*\*/\*_test.rb  --exclude-pattern \{test/unit/vagrant/action/builtin/box_add_test.rb,test/unit/plugins/communicators/winrm/\*_test.rb,test/unit/plugins/pushes/ftp/\*_test.rb\} -I/<<PKGBUILDDIR>>/debian/lib failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/vagrant/vagrant_2.2.14+dfsg-1+rebuild1633400150_amd64.build.txt

[toc] | [next] | [standalone]

#306758 — Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 upstream fixed-upstream

On 14 Oct 2021 20:57:27 -0300 Antonio Terceiro <terceiro@debian.org> wrote:
> Source: vagrant
> Version: 2.2.14+dfsg-1
> Severity: serious
> Justification: FTBFS
> Usertags: ruby3.0

https://github.com/hashicorp/vagrant/pull/12427 is titled "Updates for Ruby 
3.0" and is part of vagrant (upstream) since v2.2.17.

So it looks like uploading a new upstream version >= 2.2.17 would fix this 
issue.

[toc] | [prev] | [next] | [standalone]

#306759 — Processed: Re: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

Processing control commands:

> tag -1 upstream fixed-upstream
Bug #996529 [src:vagrant] vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:      RuntimeError:
Added tag(s) fixed-upstream and upstream.

-- 
996529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996529
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#309242 — Bug#996529: marked as done (vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 15 Nov 2021 12:48:51 +0000
with message-id <E1mmbPn-000H0b-U0@fasolo.debian.org>
and subject line Bug#996529: fixed in vagrant 2.2.19+dfsg-1
has caused the Debian Bug report #996529,
regarding vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:      RuntimeError:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
996529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996529
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web