Skip to content
This repository was archived by the owner on Nov 30, 2024. It is now read-only.

Cleanup Rubinius workaround #2799

Merged
merged 1 commit into from
Dec 15, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions features/command_line/warnings_option.feature
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@ Feature: `--warnings` option (run with warnings enabled)

You can use the `--warnings` option to run specs with warnings enabled

@unsupported-on-rbx
Scenario:
Given a file named "example_spec.rb" with:
"""ruby
Expand All @@ -15,7 +14,6 @@ Feature: `--warnings` option (run with warnings enabled)
When I run `rspec --warnings example_spec.rb`
Then the output should contain "warning"

@unsupported-on-rbx
Scenario:
Given a file named "example_spec.rb" with:
"""ruby
Expand Down
2 changes: 0 additions & 2 deletions features/core_standalone.feature
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,6 @@ Feature: Use rspec-core without rspec-mocks or rspec-expectations
available, but rspec-core can be used just fine without either of those
gems installed.

# Rubinius stacktrace includes kernel/loader.rb etc.
@unsupported-on-rbx
Scenario: Use only rspec-core when only it is installed
Given only rspec-core is installed
And a file named "core_only_spec.rb" with:
Expand Down
6 changes: 0 additions & 6 deletions features/support/rubinius.rb

This file was deleted.