Closed Graur closed 1 year ago
@yegor256 Previous pull request was with mistake in syntax and xcop
fail that build. I fixed it and create a new issue about failed rake
build #51 . Can you please take a look?
@rultor merge
@rultor merge
@yegor256 OK, I'll try to merge now. You can check the progress of the merge here
@rultor merge
@graur @yegor256 Oops, I failed. You can see the full log here (spent 2min)
\u001b[32mGiven I have a "\u001b[32m\u001b[1m.cobench\u001b[0m\u001b[0m\u001b[32m" file with content:\u001b[90m # features/step_definitions/steps.rb:41\u001b[0m\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32m --verbose\u001b[0m
\u001b[32m\u001b[0m
\u001b[32m --coder=john\u001b[0m
\u001b[32m """\u001b[0m
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
\u001b[32mWhen I run bin/cobench with "\u001b[32m\u001b[1m--dry\u001b[0m\u001b[0m\u001b[32m"\u001b[90m # features/step_definitions/steps.rb:46\u001b[0m\u001b[0m
\u001b[32mThen Stdout contains "\u001b[32m\u001b[1mXML saved to\u001b[0m\u001b[0m\u001b[32m"\u001b[90m # features/step_definitions/steps.rb:52\u001b[0m\u001b[0m
\u001b[32mAnd Exit code is zero\u001b[90m # features/step_definitions/steps.rb:60\u001b[0m\u001b[0m
Feature: Gem Package
As a source code writer I want to be able to
package the Gem into .gem file
Scenario: Gem can be packaged \u001b[90m# features/gem_package.feature:5\u001b[0m
\u001b[32mGiven I have a "\u001b[32m\u001b[1mexecs.rb\u001b[0m\u001b[0m\u001b[32m" file with content:\u001b[90m # features/step_definitions/steps.rb:41\u001b[0m\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32m #!/usr/bin/env ruby\u001b[0m
\u001b[32m require 'rubygems'\u001b[0m
\u001b[32m spec = Gem::Specification::load('./spec.rb')\u001b[0m
\u001b[32m if spec.executables.empty?\u001b[0m
\u001b[32m fail 'no executables: ' + File.read('./spec.rb')\u001b[0m
\u001b[32m end\u001b[0m
\u001b[32m """\u001b[0m
/tmp/test20230322-767-x82w97/cobench/lib/cobench/version.rb:26: warning: already initialized constant Cobench::VERSION
/home/r/repo/lib/cobench/version.rb:26: warning: previous definition of VERSION was here
\u001b[32mWhen I run bash with:\u001b[90m # features/step_definitions/steps.rb:74\u001b[0m\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32m cd cobench\u001b[0m
\u001b[32m gem build cobench.gemspec\u001b[0m
\u001b[32m gem specification --ruby cobench-*.gem > ../spec.rb\u001b[0m
\u001b[32m cd ..\u001b[0m
\u001b[32m ruby execs.rb\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32mThen Exit code is zero\u001b[90m # features/step_definitions/steps.rb:60\u001b[0m\u001b[0m
\u001b[31mFailing Scenarios:\u001b[0m
\u001b[31mcucumber features/cli.feature:18\u001b[0m\u001b[90m # Scenario: Simple report through real GitHub API\u001b[0m
6 scenarios (\u001b[31m1 failed\u001b[0m, \u001b[32m5 passed\u001b[0m)
18 steps (\u001b[31m1 failed\u001b[0m, \u001b[36m1 skipped\u001b[0m, \u001b[32m16 passed\u001b[0m)
1m0.967s
\u001b[1m\u001b[32m┌──────────────────────────────────────────────────────────────────────────────┐\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Share your Cucumber Report with your team at \u001b[4m\u001b[1m\u001b[36mhttps://reports.cucumber.io\u001b[0m\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Command line option: \u001b[36m--publish\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Environment variable: \u001b[36mCUCUMBER_PUBLISH_ENABLED\u001b[0m=\u001b[36mtrue\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m cucumber.yml: \u001b[36mdefault: --publish\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m More information at \u001b[4m\u001b[1m\u001b[36mhttps://cucumber.io/docs/cucumber/environment-variables/\u001b[0m\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m To disable this message, specify \u001b[1mCUCUMBER_PUBLISH_QUIET=true\u001b[0m or use the \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m--publish-quiet\u001b[0m option. You can also add this to your \u001b[1mcucumber.yml:\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1mdefault: --publish-quiet\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m└──────────────────────────────────────────────────────────────────────────────┘\u001b[0m\u001b[0m
Coverage report generated for Cucumber Features, Unit Tests to /home/r/repo/coverage. 0 / 0 LOC (100.0%) covered.
Stopped processing SimpleCov as a previous error not related to SimpleCov has been detected
container 2e3dcd3276a990f7e5fc6ee0f23e6803232d922896e9d157df90609fd6dcdefd is dead
Wed 22 Mar 2023 12:41:31 PM CET
@rultor merge
@rultor merge
@yegor256 OK, I'll try to merge now. You can check the progress of the merge here
@rultor merge
@graur @yegor256 Oops, I failed. You can see the full log here (spent 1min)
\u001b[32mGiven I have a "\u001b[32m\u001b[1m.cobench\u001b[0m\u001b[0m\u001b[32m" file with content:\u001b[90m # features/step_definitions/steps.rb:41\u001b[0m\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32m --verbose\u001b[0m
\u001b[32m\u001b[0m
\u001b[32m --coder=john\u001b[0m
\u001b[32m """\u001b[0m
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
\u001b[32mWhen I run bin/cobench with "\u001b[32m\u001b[1m--dry\u001b[0m\u001b[0m\u001b[32m"\u001b[90m # features/step_definitions/steps.rb:46\u001b[0m\u001b[0m
\u001b[32mThen Stdout contains "\u001b[32m\u001b[1mXML saved to\u001b[0m\u001b[0m\u001b[32m"\u001b[90m # features/step_definitions/steps.rb:52\u001b[0m\u001b[0m
\u001b[32mAnd Exit code is zero\u001b[90m # features/step_definitions/steps.rb:60\u001b[0m\u001b[0m
Feature: Gem Package
As a source code writer I want to be able to
package the Gem into .gem file
Scenario: Gem can be packaged \u001b[90m# features/gem_package.feature:5\u001b[0m
\u001b[32mGiven I have a "\u001b[32m\u001b[1mexecs.rb\u001b[0m\u001b[0m\u001b[32m" file with content:\u001b[90m # features/step_definitions/steps.rb:41\u001b[0m\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32m #!/usr/bin/env ruby\u001b[0m
\u001b[32m require 'rubygems'\u001b[0m
\u001b[32m spec = Gem::Specification::load('./spec.rb')\u001b[0m
\u001b[32m if spec.executables.empty?\u001b[0m
\u001b[32m fail 'no executables: ' + File.read('./spec.rb')\u001b[0m
\u001b[32m end\u001b[0m
\u001b[32m """\u001b[0m
/tmp/test20230322-767-1duw78/cobench/lib/cobench/version.rb:26: warning: already initialized constant Cobench::VERSION
/home/r/repo/lib/cobench/version.rb:26: warning: previous definition of VERSION was here
\u001b[32mWhen I run bash with:\u001b[90m # features/step_definitions/steps.rb:74\u001b[0m\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32m cd cobench\u001b[0m
\u001b[32m gem build cobench.gemspec\u001b[0m
\u001b[32m gem specification --ruby cobench-*.gem > ../spec.rb\u001b[0m
\u001b[32m cd ..\u001b[0m
\u001b[32m ruby execs.rb\u001b[0m
\u001b[32m """\u001b[0m
\u001b[32mThen Exit code is zero\u001b[90m # features/step_definitions/steps.rb:60\u001b[0m\u001b[0m
\u001b[31mFailing Scenarios:\u001b[0m
\u001b[31mcucumber features/cli.feature:18\u001b[0m\u001b[90m # Scenario: Simple report through real GitHub API\u001b[0m
6 scenarios (\u001b[31m1 failed\u001b[0m, \u001b[32m5 passed\u001b[0m)
18 steps (\u001b[31m1 failed\u001b[0m, \u001b[36m1 skipped\u001b[0m, \u001b[32m16 passed\u001b[0m)
0m13.851s
\u001b[1m\u001b[32m┌──────────────────────────────────────────────────────────────────────────────┐\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Share your Cucumber Report with your team at \u001b[4m\u001b[1m\u001b[36mhttps://reports.cucumber.io\u001b[0m\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Command line option: \u001b[36m--publish\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Environment variable: \u001b[36mCUCUMBER_PUBLISH_ENABLED\u001b[0m=\u001b[36mtrue\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m cucumber.yml: \u001b[36mdefault: --publish\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m More information at \u001b[4m\u001b[1m\u001b[36mhttps://cucumber.io/docs/cucumber/environment-variables/\u001b[0m\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m To disable this message, specify \u001b[1mCUCUMBER_PUBLISH_QUIET=true\u001b[0m or use the \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m--publish-quiet\u001b[0m option. You can also add this to your \u001b[1mcucumber.yml:\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1mdefault: --publish-quiet\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m└──────────────────────────────────────────────────────────────────────────────┘\u001b[0m\u001b[0m
Coverage report generated for Cucumber Features, Unit Tests to /home/r/repo/coverage. 0 / 0 LOC (100.0%) covered.
Stopped processing SimpleCov as a previous error not related to SimpleCov has been detected
container 0c495afb8d84bdf686bac6b9208f628f1f0b6f4bee1005abf9c79c003ba7051f is dead
Wed 22 Mar 2023 12:47:49 PM CET
What's done: