Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 672814 - dev-util/cucumber-3.0.2: fails 51 tests w. ruby24 on ppc64
Summary: dev-util/cucumber-3.0.2: fails 51 tests w. ruby24 on ppc64
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC64 Linux
: Normal normal (vote)
Assignee: Hans de Graaff
URL:
Whiteboard:
Keywords: TESTFAILURE
Depends on:
Blocks:
 
Reported: 2018-12-09 14:01 UTC by ernsteiswuerfel
Modified: 2018-12-11 20:25 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (cucumber-3.0.2:20181209-131919.log,71.97 KB, text/plain)
2018-12-09 14:01 UTC, ernsteiswuerfel
Details
emerge --info (file_672814.txt,6.31 KB, text/plain)
2018-12-09 14:01 UTC, ernsteiswuerfel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ernsteiswuerfel archtester 2018-12-09 14:01:07 UTC
Created attachment 557392 [details]
build.log

Failing Scenarios:
cucumber features/docs/cli/fail_fast.feature:8 # Scenario: When a scenario fails
cucumber features/docs/cli/fail_fast.feature:30 # Scenario: When all the scenarios pass
cucumber features/docs/cli/randomize.feature:61 # Scenario: Run scenarios randomized
cucumber features/docs/cli/randomize.feature:105 # Scenario: Run scenarios randomized with some skipped
cucumber features/docs/cli/specifying_multiple_formatters.feature:22 # Scenario: Multiple formatters and outputs
cucumber features/docs/cli/specifying_multiple_formatters.feature:50 # Scenario: Two formatters to stdout
cucumber features/docs/cli/specifying_multiple_formatters.feature:58 # Scenario: Two formatters to stdout when using a profile
cucumber features/docs/defining_steps/printing_messages.feature:80 # Scenario: Delayed messages feature
cucumber features/docs/exception_in_after_hook.feature:25 # Scenario: Handle Exception in standard scenario step and carry on
cucumber features/docs/exception_in_after_hook.feature:58 # Scenario: Handle Exception in scenario outline table row and carry on
cucumber features/docs/exception_in_before_hook.feature:18 # Scenario: Handle Exception in standard scenario step and carry on
cucumber features/docs/formatters/json_formatter.feature:108 # Scenario: one feature, one passing scenario, one failing scenario
cucumber features/docs/formatters/json_formatter.feature:199 # Scenario: one feature, one passing scenario, one failing scenario with prettyfied json
cucumber features/docs/formatters/json_formatter.feature:399 # Scenario: scenario outline
cucumber features/docs/formatters/json_formatter.feature:545 # Scenario: scenario outline expanded
cucumber features/docs/formatters/junit_formatter.feature:63 # Scenario: one feature, one passing scenario, one failing scenario
cucumber features/docs/formatters/junit_formatter.feature:105 # Scenario: one feature in a subdirectory, one passing scenario, one failing scenario
cucumber features/docs/formatters/junit_formatter.feature:251 # Scenario: strict mode, one feature, one scenario outline, four examples: one passing, one failing, one pending, one undefined
cucumber features/docs/formatters/junit_formatter.feature:333 # Scenario: strict mode with --expand option, one feature, one scenario outline, four examples: one passing, one failing, one pending, one undefined
cucumber features/docs/formatters/junit_formatter.feature:415 # Scenario: run test cases from different features interweaved
cucumber features/docs/getting_started.feature:7 # Scenario: Run Cucumber in an empty directory
cucumber features/docs/gherkin/background.feature:299 # Scenario: run a feature with a background that fails
cucumber features/docs/gherkin/background.feature:328 # Scenario: run a feature with scenario outlines that has a background that fails
cucumber features/docs/gherkin/background.feature:387 # Scenario: background passes with first scenario but fails with second
cucumber features/docs/gherkin/background.feature:416 # Scenario: background passes with first outline scenario but fails with second
cucumber features/docs/gherkin/background.feature:452 # Scenario: background passes with first outline scenario but fails with second (--expand)
cucumber features/docs/gherkin/outlines.feature:47 # Scenario: Run scenario outline with filtering on outline name
cucumber features/docs/gherkin/outlines.feature:79 # Scenario: Run scenario outline steps only
cucumber features/docs/gherkin/outlines.feature:112 # Scenario: Run single failing scenario outline table row
cucumber features/docs/gherkin/outlines.feature:139 # Scenario: Run all with progress formatter
cucumber features/docs/gherkin/unicode_table.feature:9 # Scenario: 
cucumber features/docs/rake_task.feature:20 # Scenario: rake task with a defined profile
cucumber features/docs/rake_task.feature:46 # Scenario: rake task without a profile
cucumber features/docs/rake_task.feature:71 # Scenario: rake task with a defined profile and cucumber_opts
cucumber features/docs/rake_task.feature:98 # Scenario: respect requires
cucumber features/docs/rake_task.feature:122 # Scenario: feature files with spaces
cucumber features/docs/raketask.feature:38 # Scenario: Passing feature
cucumber features/docs/raketask.feature:43 # Scenario: Failing feature
cucumber features/docs/work_in_progress.feature:41 # Scenario: Pass with Failing Scenarios
cucumber features/docs/work_in_progress.feature:68 # Scenario: Pass with Undefined Scenarios
cucumber features/docs/work_in_progress.feature:88 # Scenario: Pass with Undefined Scenarios
cucumber features/docs/work_in_progress.feature:111 # Scenario: Fail with Passing Scenarios
cucumber features/docs/work_in_progress.feature:134 # Scenario: Fail with Passing Scenario Outline
cucumber features/docs/writing_support_code/around_hooks.feature:9 # Scenario: A single Around hook
cucumber features/docs/writing_support_code/around_hooks.feature:43 # Scenario: Multiple Around hooks
cucumber features/docs/writing_support_code/around_hooks.feature:90 # Scenario: Mixing Around, Before, and After hooks
cucumber features/docs/writing_support_code/around_hooks.feature:138 # Scenario: Around hooks with tags
cucumber features/docs/writing_support_code/around_hooks.feature:193 # Scenario: Around hooks with scenario outlines
cucumber features/docs/writing_support_code/around_hooks.feature:237 # Scenario: Around Hooks and the Custom World
cucumber features/docs/writing_support_code/hook_order.feature:50 # Scenario: Around hooks cover background steps
cucumber features/docs/writing_support_code/hook_order.feature:58 # Scenario: All hooks execute in expected order

202 scenarios (51 failed, 151 passed)
1191 steps (51 failed, 15 skipped, 1125 passed)
0m10.026s
Comment 1 ernsteiswuerfel archtester 2018-12-09 14:01:27 UTC
Created attachment 557394 [details]
emerge --info
Comment 2 Hans de Graaff gentoo-dev Security 2018-12-10 07:49:12 UTC
This looks like an issue with your ruby setup. Perhaps a mismatch between "eselect ruby" and RUBY_TARGETS?
Comment 3 ernsteiswuerfel archtester 2018-12-11 20:25:51 UTC
(In reply to Hans de Graaff from comment #2)
> This looks like an issue with your ruby setup. Perhaps a mismatch between
> "eselect ruby" and RUBY_TARGETS?

You were correct. Sorry for the noise!

However now the ruby24 tests fail just like in bug #661022 (wrong dependency on diff-lcs and bundle (Aruba::LaunchError)).