Attachment 1254176 Details for Bug 1424300 – build.log

build.log

<fdopen> (text/plain), 49.23 KB, created by Fedora Release Engineering on 2017-02-17 16:38:23 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Fedora Release Engineering

Created: 2017-02-17 16:38:23 UTC

Size: 49.23 KB

patch

obsolete

>Mock Version: 1.3.3
>Mock Version: 1.3.3
>ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target noarch --nodeps /builddir/build/SPECS/rubygem-cucumber-wire.spec'], gid=425shell=Falseuser='mockbuild'uid=1000printOutput=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fe8d7ed2390>env={'PS1': '<mock-chroot> \\s-\\v\\$ ', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'LANG': 'en_US.UTF-8', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'}timeout=172800chrootPath='/var/lib/mock/f26-build-7654990-694572/root')
>Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target noarch --nodeps /builddir/build/SPECS/rubygem-cucumber-wire.spec'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'LANG': 'en_US.UTF-8', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'} and shell False
>Building target platforms: noarch
>Building for target noarch
>Wrote: /builddir/build/SRPMS/rubygem-cucumber-wire-0.0.1-2.fc26.src.rpm
>Child return code was: 0
>ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target noarch --nodeps /builddir/build/SPECS/rubygem-cucumber-wire.spec'], gid=425private_network=Trueshell=Falseuser='mockbuild'uid=1000printOutput=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fe8d7ed2390>env={'PS1': '<mock-chroot> \\s-\\v\\$ ', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'LANG': 'en_US.UTF-8', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'}timeout=172800chrootPath='/var/lib/mock/f26-build-7654990-694572/root')
>Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target noarch --nodeps /builddir/build/SPECS/rubygem-cucumber-wire.spec'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'LANG': 'en_US.UTF-8', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'} and shell False
>Building target platforms: noarch
>Building for target noarch
>Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.V1BY3x
>+ umask 022
>+ cd /builddir/build/BUILD
>+ gem unpack /builddir/build/SOURCES/cucumber-wire-0.0.1.gem
>Unpacked gem: '/builddir/build/BUILD/cucumber-wire-0.0.1'
>+ cd /builddir/build/BUILD
>+ cd cucumber-wire-0.0.1
>+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
>+ gem spec /builddir/build/SOURCES/cucumber-wire-0.0.1.gem -l --ruby
>+ exit 0
>Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iZksYM
>+ umask 022
>+ cd /builddir/build/BUILD
>+ cd cucumber-wire-0.0.1
>+ gem build cucumber-wire.gemspec
>WARNING:  pessimistic dependency on cucumber (~> 2.1.0, development) may be overly strict
>  if cucumber is semantically versioned, use:
>    add_development_dependency 'cucumber', '~> 2.1', '>= 2.1.0'
>WARNING:  open-ended dependency on bundler (>= 1.3.5, development) is not recommended
>  if bundler is semantically versioned, use:
>    add_development_dependency 'bundler', '~> 1.3', '>= 1.3.5'
>WARNING:  open-ended dependency on rake (>= 0.9.2, development) is not recommended
>  if rake is semantically versioned, use:
>    add_development_dependency 'rake', '~> 0.9', '>= 0.9.2'
>WARNING:  See http://guides.rubygems.org/specification-reference/ for help
>  Successfully built RubyGem
>  Name: cucumber-wire
>  Version: 0.0.1
>  File: cucumber-wire-0.0.1.gem
>+ mkdir -p ./usr/share/gems
>+ CONFIGURE_ARGS='--with-cflags='\''-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m32 -march=i686 -fasynchronous-unwind-tables'\'' '
>+ gem install -V --local --build-root . --force --document=ri,rdoc cucumber-wire-0.0.1.gem
>WARNING:  You build with buildroot.
>  Build root: /builddir/build/BUILD/cucumber-wire-0.0.1
>  Bin dir: /builddir/build/BUILD/cucumber-wire-0.0.1/usr/bin
>  Gem home: /builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/.rspec
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/.travis.yml
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/Gemfile
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/README.md
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/Rakefile
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/cucumber-wire.gemspec
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/erb_configuration.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/handle_unexpected_response.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/invoke_message.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/readme.md
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/snippets_message.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/step_definitions/aruba_steps.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/step_definitions/wire_steps.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/step_matches_message.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/support/fake_wire_server.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/table_diffing.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/tags.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/timeouts.feature
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/add_hooks_filter.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/configuration.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/connection.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/connections.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/data_packet.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/exception.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/plugin.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/protocol.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/protocol/requests.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/request_handler.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/snippet.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/step_definition.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/lib/cucumber/wire/version
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/spec/cucumber/wire/configuration_spec.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/spec/cucumber/wire/connection_spec.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/spec/cucumber/wire/connections_spec.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/spec/cucumber/wire/data_packet_spec.rb
>/builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/spec/cucumber/wire/exception_spec.rb
>Successfully installed cucumber-wire-0.0.1
>Parsing documentation for cucumber-wire-0.0.1
>Parsing sources...
>  7% [ 1/14]  lib/cucumber/wire.rb
> 14% [ 2/14]  lib/cucumber/wire/add_hooks_filter.rb
> 21% [ 3/14]  lib/cucumber/wire/configuration.rb
> 28% [ 4/14]  lib/cucumber/wire/connection.rb
> 35% [ 5/14]  lib/cucumber/wire/connections.rb
> 42% [ 6/14]  lib/cucumber/wire/data_packet.rb
> 50% [ 7/14]  lib/cucumber/wire/exception.rb
> 57% [ 8/14]  lib/cucumber/wire/plugin.rb
> 64% [ 9/14]  lib/cucumber/wire/protocol.rb
> 71% [10/14]  lib/cucumber/wire/protocol/requests.rb
> 78% [11/14]  lib/cucumber/wire/request_handler.rb
> 85% [12/14]  lib/cucumber/wire/snippet.rb
> 92% [13/14]  lib/cucumber/wire/step_definition.rb
>100% [14/14]  lib/cucumber/wire/version
>Installing ri documentation for cucumber-wire-0.0.1
>Installing darkfish documentation for cucumber-wire-0.0.1
>Done installing documentation for cucumber-wire after 0 seconds
>1 gem installed
>+ exit 0
>Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.nI7lm4
>+ umask 022
>+ cd /builddir/build/BUILD
>+ '[' /builddir/build/BUILDROOT/rubygem-cucumber-wire-0.0.1-2.fc26.noarch '!=' / ']'
>+ rm -rf /builddir/build/BUILDROOT/rubygem-cucumber-wire-0.0.1-2.fc26.noarch
>++ dirname /builddir/build/BUILDROOT/rubygem-cucumber-wire-0.0.1-2.fc26.noarch
>+ mkdir -p /builddir/build/BUILDROOT
>+ mkdir /builddir/build/BUILDROOT/rubygem-cucumber-wire-0.0.1-2.fc26.noarch
>+ cd cucumber-wire-0.0.1
>+ mkdir -p /builddir/build/BUILDROOT/rubygem-cucumber-wire-0.0.1-2.fc26.noarch/usr/share/gems
>+ cp -a ./usr/share/gems/build_info ./usr/share/gems/cache ./usr/share/gems/doc ./usr/share/gems/extensions ./usr/share/gems/gems ./usr/share/gems/specifications /builddir/build/BUILDROOT/rubygem-cucumber-wire-0.0.1-2.fc26.noarch/usr/share/gems/
>+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 /builddir/build/BUILD/cucumber-wire-0.0.1
>+ /usr/lib/rpm/check-buildroot
>+ /usr/lib/rpm/brp-compress
>+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
>+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
>+ /usr/lib/rpm/brp-python-hardlink
>Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.lRE6pn
>+ umask 022
>+ cd /builddir/build/BUILD
>+ cd cucumber-wire-0.0.1
>~/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1 ~/build/BUILD/cucumber-wire-0.0.1
>+ pushd ./usr/share/gems/gems/cucumber-wire-0.0.1
>+ LANG=C.UTF-8
>+ rspec spec
>....................
>Finished in 0.01894 seconds (files took 0.22262 seconds to load)
>20 examples, 0 failures
>+ sed -i '/(Timeout::Error)/ a\            /usr/share/ruby/timeout.rb:106:in `timeout'\''' features/timeouts.feature
>+ cucumber
>Feature: ERB configuration
>  As a developer on server with multiple users
>  I want to be able to configure which port my wire server runs on
>  So that I can avoid port conflicts
>  Background:                                         # features/erb_configuration.feature:7
>    Given a file named "features/wired.feature" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: High strung
>        Scenario: Wired
>          Given we're all wired
>      """
>  Scenario: ERB is used in the wire file which references an environment variable that is not set # features/erb_configuration.feature:16
>    Given a file named "features/step_definitions/server.wire" with:                              # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: <%= ENV['PORT'] || 12345 %>
>      """
>    And there is a wire server running on port 12345 which understands the following protocol:    # features/step_definitions/wire_steps.rb:1
>      | request                                              | response       |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[]] |
>    When I run `cucumber --dry-run --no-snippets -f progress`                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then it should pass with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      U
>      1 scenario (1 undefined)
>      1 step (1 undefined)
>      """
>The use of "#set_env" is deprecated. Please use "set_environment_variable" instead. But be careful, this method uses a different kind of implementation. Called by /builddir/build/BUILD/cucumber-wire-0.0.1/usr/share/gems/gems/cucumber-wire-0.0.1/features/step_definitions/wire_steps.rb:17:in `block in <top (required)>'
>  Scenario: ERB is used in the wire file which references an environment variable              # features/erb_configuration.feature:36
>    Given I have environment variable PORT set to "16816"                                      # features/step_definitions/wire_steps.rb:16
>    And a file named "features/step_definitions/server.wire" with:                             # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: <%= ENV['PORT'] || 12345 %>
>      """
>    And there is a wire server running on port 16816 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response       |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[]] |
>    When I run `cucumber --dry-run --no-snippets -f progress`                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then it should pass with:                                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      U
>      1 scenario (1 undefined)
>      1 step (1 undefined)
>      """
>Feature: Handle unexpected response
>  When the server sends us back a message we don't understand, this is how Cucumber will behave.
>  Background:                                                                 # features/handle_unexpected_response.feature:5
>    Given a file named "features/wired.feature" with:                         # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: High strung
>        Scenario: Wired
>          Given we're all wired
>      """
>    And a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>  Scenario: Unexpected response                                                                  # features/handle_unexpected_response.feature:20
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["begin_scenario"]                                   | ["yikes"]                           |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>    When I run `cucumber -f pretty`                                                              # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the output should contain:                                                              # aruba-0.14.2/lib/aruba/cucumber/command.rb:205
>      """
>      undefined method `handle_yikes'
>      """
>Feature: Invoke message
>  Assuming a StepMatch was returned for a given step name, when it's time to
>  invoke that step definition, Cucumber will send an invoke message.
>  The invoke message contains the ID of the step definition, as returned by
>  the wire server in response to the the step_matches call, along with the
>  arguments that were parsed from the step name during the same step_matches
>  call.
>  The wire server will normally reply one of the following:
>  * `success`
>  * `fail`
>  * `pending` - optionally takes a message argument
>  This isn't quite the whole story: see also table_diffing.feature
>  Background:                                                                 # features/invoke_message.feature:19
>    Given a file named "features/wired.feature" with:                         # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: High strung
>        Scenario: Wired
>          Given we're all wired
>      """
>    And a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>  @spawn
>  Scenario: Invoke a step definition which is pending                                            # features/invoke_message.feature:36
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>      | ["begin_scenario"]                                   | ["success"]                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["pending", "I'll do it later"]     |
>      | ["end_scenario"]                                     | ["success"]                         |
>    When I run `cucumber -f pretty -q`                                                           # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    And it should pass with exactly:                                                             # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      Feature: High strung
>        Scenario: Wired
>          Given we're all wired
>            I'll do it later (Cucumber::Pending)
>            features/wired.feature:3:in `Given we're all wired'
>      1 scenario (1 pending)
>      1 step (1 pending)
>      """
>  Scenario: Invoke a step definition which passes                                                # features/invoke_message.feature:58
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>      | ["begin_scenario"]                                   | ["success"]                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
>      | ["end_scenario"]                                     | ["success"]                         |
>    When I run `cucumber -f progress`                                                            # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    And it should pass with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      .
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>  @spawn
>  Scenario: Invoke a step definition which fails                                                 # features/invoke_message.feature:76
>    If an invoked step definition fails, it can return details of the exception
>    in the reply to invoke. This causes a Cucumber::WireSupport::WireException to be
>    raised.
>    Valid arguments are:
>    - `message` (mandatory)
>    - `exception`
>    - `backtrace`
>    See the specs for Cucumber::WireSupport::WireException for more details
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                                                                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]]                                                 |
>      | ["begin_scenario"]                                   | ["success"]                                                                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["fail",{"message":"The wires are down", "exception":"Some.Foreign.ExceptionType"}] |
>      | ["end_scenario"]                                     | ["success"]                                                                         |
>    When I run `cucumber -f progress`                                                            # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should fail with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      F
>      (::) failed steps (::)
>      The wires are down (Some.Foreign.ExceptionType from localhost:54321)
>      features/wired.feature:3:in `Given we're all wired'
>      Failing Scenarios:
>      cucumber features/wired.feature:2 # Scenario: Wired
>      1 scenario (1 failed)
>      1 step (1 failed)
>      """
>  Scenario: Invoke a step definition which takes string arguments (and passes)                   # features/invoke_message.feature:115
>    If the step definition at the end of the wire captures arguments, these are
>    communicated back to Cucumber in the `step_matches` message.
>    Cucumber expects these StepArguments to be returned in the StepMatch. The keys
>    have the following meanings:
>    - `val` - the value of the string captured for that argument from the step
>      name passed in step_matches
>    - `pos` - the position within the step name that the argument was matched
>      (used for formatter highlighting)
>    The argument values are then sent back by Cucumber in the `invoke` message.
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                                                     |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[{"val":"wired", "pos":10}]}]] |
>      | ["begin_scenario"]                                   | ["success"]                                                  |
>      | ["invoke",{"id":"1","args":["wired"]}]               | ["success"]                                                  |
>      | ["end_scenario"]                                     | ["success"]                                                  |
>    When I run `cucumber -f progress`                                                            # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should pass with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      .
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>  Scenario: Invoke a step definition which takes regular and table arguments (and passes)      # features/invoke_message.feature:147
>    If the step has a multiline table argument, it will be passed with the
>    invoke message as an array of array of strings.
>    In this scenario our step definition takes two arguments - one
>    captures the "we're" and the other takes the table.
>    Given a file named "features/wired_on_tables.feature" with:                                # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: High strung
>        Scenario: Wired and more
>          Given we're all:
>            | wired |
>            | high  |
>            | happy |
>      """
>    And there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                                               | response                                                    |
>      | ["step_matches",{"name_to_match":"we're all:"}]                       | ["success",[{"id":"1", "args":[{"val":"we're", "pos":0}]}]] |
>      | ["begin_scenario"]                                                    | ["success"]                                                 |
>      | ["invoke",{"id":"1","args":["we're",[["wired"],["high"],["happy"]]]}] | ["success"]                                                 |
>      | ["end_scenario"]                                                      | ["success"]                                                 |
>    When I run `cucumber -f progress features/wired_on_tables.feature`                         # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should pass with:                                                                   # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      .
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>  Scenario: Invoke a scenario outline step                                                     # features/invoke_message.feature:181
>    Given a file named "features/wired_in_an_outline.feature" with:                            # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature:
>        Scenario Outline:
>          Given we're all <arg>
>          Examples:
>            | arg   |
>            | wired |
>      """
>    And there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>      | ["begin_scenario"]                                   | ["success"]                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
>      | ["end_scenario"]                                     | ["success"]                         |
>    When I run `cucumber -f progress features/wired_in_an_outline.feature`                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should pass with:                                                                   # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      .
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>    And the wire server should have received the following messages:                           # features/step_definitions/wire_steps.rb:20
>      | step_matches   |
>      | begin_scenario |
>      | invoke         |
>      | end_scenario   |
>Feature: Snippets message
>  If a step doesn't match, Cucumber will ask the wire server to return a snippet of code for a
>  step definition.
>  Background:                                                                 # features/snippets_message.feature:6
>    Given a file named "features/wired.feature" with:                         # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: High strung
>        Scenario: Wired
>          Given we're all wired
>      """
>    And a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>  @spawn
>  Scenario: Wire server returns snippets for a step that didn't match                            # features/snippets_message.feature:22
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                                                                          | response                         |
>      | ["step_matches",{"name_to_match":"we're all wired"}]                                             | ["success",[]]                   |
>      | ["snippet_text",{"step_keyword":"Given","multiline_arg_class":"","step_name":"we're all wired"}] | ["success","foo()\n  bar;\nbaz"] |
>      | ["begin_scenario"]                                                                               | ["success"]                      |
>      | ["end_scenario"]                                                                                 | ["success"]                      |
>    When I run `cucumber -f pretty`                                                              # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should pass with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      Feature: High strung
>        Scenario: Wired         # features/wired.feature:2
>          Given we're all wired # features/wired.feature:3
>      1 scenario (1 undefined)
>      1 step (1 undefined)
>      """
>    And the output should contain:                                                               # aruba-0.14.2/lib/aruba/cucumber/command.rb:205
>      """
>      foo()
>        bar;
>      baz
>      """
>Feature: Step matches message
>  When the features have been parsed, Cucumber will send a `step_matches`
>  message to ask the wire server if it can match a step name. This happens for
>  each of the steps in each of the features.
>  The wire server replies with an array of StepMatch objects.
>  When each StepMatch is returned, it contains the following data:
>  * `id` - identifier for the step definition to be used later when if it
>  needs to be invoked. The identifier can be any string value and
>  is simply used for the wire server's own reference.
>  * `args` - any argument values as captured by the wire end's own regular
>  expression (or other argument matching) process.
>  Background:                                                                 # features/step_matches_message.feature:17
>    Given a file named "features/wired.feature" with:                         # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: High strung
>        Scenario: Wired
>          Given we're all wired
>      """
>    And a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>  Scenario: Dry run finds no step match                                                          # features/step_matches_message.feature:32
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response       |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[]] |
>    When I run `cucumber --dry-run --no-snippets -f progress`                                    # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    And it should pass with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      U
>      1 scenario (1 undefined)
>      1 step (1 undefined)
>      """
>  Scenario: Dry run finds a step match                                                           # features/step_matches_message.feature:46
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>    When I run `cucumber --dry-run -f progress`                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    And it should pass with:                                                                     # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      -
>      1 scenario (1 skipped)
>      1 step (1 skipped)
>      """
>  Scenario: Step matches returns details about the remote step definition                        # features/step_matches_message.feature:60
>    Optionally, the StepMatch can also contain a source reference, and a native
>    regexp string which will be used by some formatters.
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                                                                           |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[], "source":"MyApp.MyClass:123", "regexp":"we.*"}]] |
>    When I run `cucumber -f stepdefs --dry-run`                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then it should pass with:                                                                    # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      -
>      we.*   # MyApp.MyClass:123
>      1 scenario (1 skipped)
>      1 step (1 skipped)
>      """
>    And the stderr should not contain anything                                                   # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>Feature: Wire protocol table diffing
>  In order to use the amazing functionality in the Cucumber table object
>  As a wire server
>  I want to be able to ask for a table diff during a step definition invocation
>  Background:                                                                 # features/table_diffing.feature:7
>    Given a file named "features/wired.feature" with:                         # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: Hello
>        Scenario: Wired
>          Given we're all wired
>      """
>    And a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>  @spawn
>  Scenario: Invoke a step definition tries to diff the table and fails                           # features/table_diffing.feature:23
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                                                                                             |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]]                                                                  |
>      | ["begin_scenario"]                                   | ["success"]                                                                                          |
>      | ["invoke",{"id":"1","args":[]}]                      | ["diff",[[["a","b"],["c","d"]],[["x","y"],["z","z"]]]]                                               |
>      | ["diff_failed"]                                      | ["fail",{"message":"Not same", "exception":"DifferentException", "backtrace":["a.cs:12","b.cs:34"]}] |
>      | ["end_scenario"]                                     | ["success"]                                                                                          |
>    When I run `cucumber -f progress --backtrace -q`                                             # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                  # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should fail with exactly:                                                             # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      F
>      (::) failed steps (::)
>      Not same (DifferentException from localhost:54321)
>      a.cs:12
>      b.cs:34
>      features/wired.feature:3:in `Given we're all wired'
>      Failing Scenarios:
>      cucumber features/wired.feature:2
>      1 scenario (1 failed)
>      1 step (1 failed)
>      """
>  Scenario: Invoke a step definition tries to diff the table and passes                          # features/table_diffing.feature:52
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                               |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]]    |
>      | ["begin_scenario"]                                   | ["success"]                            |
>      | ["invoke",{"id":"1","args":[]}]                      | ["diff",[[["a"],["b"]],[["a"],["b"]]]] |
>      | ["diff_ok"]                                          | ["success"]                            |
>      | ["end_scenario"]                                     | ["success"]                            |
>    When I run `cucumber -f progress -q`                                                         # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then it should pass with exactly:                                                            # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      .
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>  @spawn
>  Scenario: Invoke a step definition which successfully diffs a table but then fails             # features/table_diffing.feature:71
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                                                      |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]]                           |
>      | ["begin_scenario"]                                   | ["success"]                                                   |
>      | ["invoke",{"id":"1","args":[]}]                      | ["diff",[[["a"],["b"]],[["a"],["b"]]]]                        |
>      | ["diff_ok"]                                          | ["fail",{"message":"I wanted things to be different for us"}] |
>      | ["end_scenario"]                                     | ["success"]                                                   |
>    When I run `cucumber -f progress -q`                                                         # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then it should fail with exactly:                                                            # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      F
>      (::) failed steps (::)
>      I wanted things to be different for us (Cucumber::Wire::Exception)
>      features/wired.feature:3:in `Given we're all wired'
>      Failing Scenarios:
>      cucumber features/wired.feature:2
>      1 scenario (1 failed)
>      1 step (1 failed)
>      """
>  @spawn
>  Scenario: Invoke a step definition which asks for an immediate diff that fails                 # features/table_diffing.feature:98
>    Given there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>      | ["begin_scenario"]                                   | ["success"]                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["diff!",[[["a"]],[["b"]]]]         |
>      | ["end_scenario"]                                     | ["success"]                         |
>    When I run `cucumber -f progress -q`                                                         # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    And it should fail with exactly:                                                             # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      F
>      (::) failed steps (::)
>      Tables were not identical:
>        | (-) a | (+) b |
>       (Cucumber::MultilineArgument::DataTable::Different)
>      features/wired.feature:3:in `Given we're all wired'
>      Failing Scenarios:
>      cucumber features/wired.feature:2
>      1 scenario (1 failed)
>      1 step (1 failed)
>      """
>Feature: Wire protocol tags
>  In order to use Before and After hooks in a wire server, we send tags with the
>  scenario in the begin_scenario and end_scenario messages
>  Background:                                                                   # features/tags.feature:6
>    Given a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>  Scenario: Run a scenario                                                                     # features/tags.feature:14
>    Given a file named "features/wired.feature" with:                                          # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>        @foo @bar
>        Feature: Wired
>          @baz
>          Scenario: Everybody's Wired
>            Given we're all wired
>      """
>    And there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>      | ["begin_scenario", {"tags":["bar","baz","foo"]}]     | ["success"]                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
>      | ["end_scenario", {"tags":["bar","baz","foo"]}]       | ["success"]                         |
>    When I run `cucumber -f pretty -q`                                                         # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should pass with:                                                                   # aruba-0.14.2/lib/aruba/cucumber/command.rb:299
>      """
>      @foo @bar
>      Feature: Wired
>        @baz
>        Scenario: Everybody's Wired
>          Given we're all wired
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>  Scenario: Run a scenario outline example                                                     # features/tags.feature:47
>    Given a file named "features/wired.feature" with:                                          # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>        @foo @bar
>        Feature: Wired
>          @baz
>          Scenario Outline: Everybody's Wired
>            Given we're all <something>
>          Examples:
>            | something |
>            | wired     |
>      """
>    And there is a wire server running on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                            |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
>      | ["begin_scenario", {"tags":["bar","baz","foo"]}]     | ["success"]                         |
>      | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
>      | ["end_scenario", {"tags":["bar","baz","foo"]}]       | ["success"]                         |
>    When I run `cucumber -f pretty -q`                                                         # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                                # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should pass with exactly:                                                           # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      @foo @bar
>      Feature: Wired
>        @baz
>        Scenario Outline: Everybody's Wired
>          Given we're all <something>
>          Examples: 
>            | something |
>            | wired     |
>      1 scenario (1 passed)
>      1 step (1 passed)
>      """
>Feature: Wire protocol timeouts
>  We don't want Cucumber to hang forever on a wire server that's not even there,
>  but equally we need to give the user the flexibility to allow step definitions
>  to take a while to execute, if that's what they need.
>  Background:                                         # features/timeouts.feature:7
>    Given a file named "features/wired.feature" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      Feature: Telegraphy
>        Scenario: Wired
>          Given we're all wired
>      """
>  Scenario: Try to talk to a server that's not there                            # features/timeouts.feature:16
>    Given a file named "features/step_definitions/some_remote_place.wire" with: # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      """
>    When I run `cucumber -f progress`                                           # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should contain:                                             # aruba-0.14.2/lib/aruba/cucumber/command.rb:205
>      """
>      Unable to contact the wire server at localhost:54321
>      """
>  @spawn
>  Scenario: Invoke a step definition that takes longer than its timeout                # features/timeouts.feature:30
>    Given a file named "features/step_definitions/some_remote_place.wire" with:        # aruba-0.14.2/lib/aruba/cucumber/file.rb:23
>      """
>      host: localhost
>      port: 54321
>      timeout:
>        invoke: 0.1
>      """
>    And there is a wire server on port 54321 which understands the following protocol: # features/step_definitions/wire_steps.rb:1
>      | request                                              | response                                                     |
>      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[{"val":"wired", "pos":10}]}]] |
>      | ["begin_scenario"]                                   | ["success"]                                                  |
>      | ["invoke",{"id":"1","args":["wired"]}]               | ["success"]                                                  |
>      | ["end_scenario"]                                     | ["success"]                                                  |
>    And the wire server takes 0.2 seconds to respond to the invoke message             # features/step_definitions/wire_steps.rb:11
>    When I run `cucumber -f pretty -q`                                                 # aruba-0.14.2/lib/aruba/cucumber/command.rb:13
>    Then the stderr should not contain anything                                        # aruba-0.14.2/lib/aruba/cucumber/command.rb:341
>    And it should fail with exactly:                                                   # aruba-0.14.2/lib/aruba/cucumber/command.rb:313
>      """
>      Feature: Telegraphy
>        Scenario: Wired
>          Given we're all wired
>            Timed out calling wire server with message 'invoke' (Timeout::Error)
>            /usr/share/ruby/timeout.rb:106:in `timeout'
>            features/wired.feature:3:in `Given we're all wired'
>      Failing Scenarios:
>      cucumber features/wired.feature:2
>      1 scenario (1 failed)
>      1 step (1 failed)
>      """
>      expected "Feature: Telegraphy\n\n  Scenario: Wired\n    Given we're all wired\n      Timed out calling wire se...\nFailing Scenarios:\ncucumber features/wired.feature:2\n\n1 scenario (1 failed)\n1 step (1 failed)" to have output: output string is eq: "Feature: Telegraphy\n\n  Scenario: Wired\n    Given we're all wired\n      Time...Failing Scenarios:\ncucumber features/wired.feature:2\n\n1 scenario (1 failed)\n1 step (1 failed)\n"
>      Diff:
>      @@ -1,2 +1,14 @@
>      -(output string is eq: "Feature: Telegraphy\n\n  Scenario: Wired\n    Given we're all wired\n      Timed out calling wire se...Failing Scenarios:\ncucumber features/wired.feature:2\n\n1 scenario (1 failed)\n1 step (1 failed)\n")
>      +Feature: Telegraphy
>      +
>      +  Scenario: Wired
>      +    Given we're all wired
>      +      Timed out calling wire server with message 'invoke' (Timeout::Error)
>      +      /usr/share/ruby/timeout.rb:108:in `timeout'
>      +      features/wired.feature:3:in `Given we're all wired'
>      +
>      +Failing Scenarios:
>      +cucumber features/wired.feature:2
>      +
>      +1 scenario (1 failed)
>      +1 step (1 failed)
>       (RSpec::Expectations::ExpectationNotMetError)
>      features/timeouts.feature:48:in `And it should fail with exactly:'
>Failing Scenarios:
>cucumber features/timeouts.feature:30 # Scenario: Invoke a step definition that takes longer than its timeout
>21 scenarios (1 failed, 20 passed)
>120 steps (1 failed, 119 passed)
>0m9.484s
>error: Bad exit status from /var/tmp/rpm-tmp.lRE6pn (%check)
>    Bad exit status from /var/tmp/rpm-tmp.lRE6pn (%check)
>RPM build errors:
>Child return code was: 1
>EXCEPTION: [Error()]
>Traceback (most recent call last):
>  File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py", line 89, in trace
>    result = func(*args, **kw)
>  File "/usr/lib/python3.5/site-packages/mockbuild/util.py", line 578, in do
>    raise exception.Error("Command failed. See logs for output.\n # %s" % (command,), child.returncode)
>mockbuild.exception.Error: Command failed. See logs for output.
> # bash --login -c /usr/bin/rpmbuild -bb --target noarch --nodeps /builddir/build/SPECS/rubygem-cucumber-wire.spec

Actions: View

Attachments on bug 1424300: 1254176 | 1254177 | 1254178