Skip to content

The test suite is centered about the CI #1080

@voxik

Description

@voxik

Trying to update rubygem-concurrent-ruby package in Fedora, I am facing issues like this:

An error occurred while loading ./spec/concurrent/atomic/atomic_boolean_spec.rb. Failure/Error: RSpec.describe CAtomicBoolean do it_should_behave_like :atomic_boolean end NameError: uninitialized constant Concurrent::CAtomicBoolean # ./spec/concurrent/atomic/atomic_boolean_spec.rb:146:in '<module:Concurrent>' # ./spec/concurrent/atomic/atomic_boolean_spec.rb:107:in '<top (required)>' An error occurred while loading ./spec/concurrent/atomic/atomic_fixnum_spec.rb. Failure/Error: RSpec.describe CAtomicFixnum do it_should_behave_like :atomic_fixnum end 

Looking into why this happes for 1.3.5 while it was working fine for 1.1.9, I have arrived at this commit. And this point out that no matter what, the test suite now expects to have the C extension around. However that is not the case for plain concurrent-ruby gem.

Is there a chance to somehow untangle the concurrent-ruby, concurrent-ruby-ext and concurrent-ruby-edge projects?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions