Azure DevOps Publish to the App Store TestFlight track fails with exit code 1 - azure

We are trying to publish the IPA to App Store. but task is getting failed with error code 1.
2021-12-22T13:40:44.9828920Z ##[section]Starting: Publish to the App Store TestFlight track
2021-12-22T13:40:44.9841780Z ==============================================================================
2021-12-22T13:40:44.9842160Z Task : Apple App Store Release
2021-12-22T13:40:44.9842730Z Description : Release an app to TestFlight or the Apple App Store
2021-12-22T13:40:44.9843080Z Version : 1.189.0
2021-12-22T13:40:44.9843340Z Author : Microsoft Corporation
2021-12-22T13:40:44.9843860Z Help : More Information
2021-12-22T13:40:44.9844350Z ==============================================================================
2021-12-22T13:40:45.2032820Z [command]/usr/local/opt/ruby#2.7/bin/gem install fastlane
2021-12-22T13:41:12.7283020Z Successfully installed fastlane-2.199.0
2021-12-22T13:41:12.7285250Z Parsing documentation for fastlane-2.199.0
2021-12-22T13:41:12.7287270Z Installing ri documentation for fastlane-2.199.0
2021-12-22T13:41:12.7288910Z Done installing documentation for fastlane after 23 seconds
2021-12-22T13:41:12.7290200Z 1 gem installed
2021-12-22T13:41:12.7637580Z [command]/usr/local/opt/ruby#2.7/bin/gem update fastlane -i /Users/runner/.gem-cache
2021-12-22T13:41:15.6010280Z Updating installed gems
2021-12-22T13:41:15.6010960Z Nothing to update
2021-12-22T13:41:15.6330030Z [command]/usr/local/lib/ruby/gems/2.7.0/bin/fastlane pilot upload --api_key_path /Users/runner/work/_temp/api_key***.json -i /Users/runner/work/r1/a/_Calendar-Mobile-Build/Calendar-MobileApp/ExtractedFiles/in.store.calendar.ipa -a in.store.calendar --skip_submission true --skip_waiting_for_build_processing true -p 1596887926
2021-12-22T13:41:18.3757000Z [13:41:18]: �[33mGet started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile�[0m
2021-12-22T13:41:24.9984700Z [13:41:24]: Sending anonymous analytics information
2021-12-22T13:41:25.0084340Z [13:41:24]: Learn more at https://docs.fastlane.tools/#metrics
2021-12-22T13:41:25.0085930Z [13:41:24]: No personal or sensitive data is sent.
2021-12-22T13:41:25.0087420Z [13:41:24]: You can disable this by adding opt_out_usage at the top of your Fastfile
2021-12-22T13:41:25.0342540Z
2021-12-22T13:41:25.0347110Z Looking for related GitHub issues on fastlane/fastlane...
2021-12-22T13:41:25.0347960Z
2021-12-22T13:41:25.5644610Z ➡️ Pilot fails using environment variables on GitHub
2021-12-22T13:41:25.5646070Z https://github.com//issues/18655 [open] 11 💬
2021-12-22T13:41:25.5646810Z 2 weeks ago
2021-12-22T13:41:25.5647060Z
2021-12-22T13:41:25.5681000Z ➡️ Pilot and deliver fails with "string contains null byte"
2021-12-22T13:41:25.5682210Z https://github.com//issues/18312 [closed] 7 💬
2021-12-22T13:41:25.5685140Z 12 Jul 2021
2021-12-22T13:41:25.5685600Z
2021-12-22T13:41:25.5687110Z ➡️ Deliver step gets stuck while running Transporter
2021-12-22T13:41:25.5688670Z https://github.com//issues/19428 [closed] 0 💬
2021-12-22T13:41:25.5689470Z 2 weeks ago
2021-12-22T13:41:25.5689810Z
2021-12-22T13:41:25.5690920Z and 8 more at: https://github.com/fastlane/fastlane/search?q=string%20contains%20null%20byte&type=Issues&utf8=✓
2021-12-22T13:41:25.5691290Z
2021-12-22T13:41:25.5692440Z 🔗 You can ⌘ + double-click on links to open them directly in your browser.
2021-12-22T13:41:25.5693940Z /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in initialize': [!] string contains null byte (ArgumentError) 2021-12-22T13:41:25.5695490Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in new'
2021-12-22T13:41:25.5696930Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in create' 2021-12-22T13:41:25.5698560Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:49:in from_json_file'
2021-12-22T13:41:25.5700740Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:33:in from' 2021-12-22T13:41:25.5702140Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/manager.rb:23:in login'
2021-12-22T13:41:25.5703520Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/manager.rb:19:in start' 2021-12-22T13:41:25.5704920Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/build_manager.rb:17:in upload'
2021-12-22T13:41:25.5706370Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/commands_generator.rb:67:in block (2 levels) in run' 2021-12-22T13:41:25.5707770Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
2021-12-22T13:41:25.5709110Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 2021-12-22T13:41:25.5710430Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
2021-12-22T13:41:25.5711890Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:117:in run!' 2021-12-22T13:41:25.5713720Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
2021-12-22T13:41:25.5715210Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/commands_generator.rb:167:in run' 2021-12-22T13:41:25.5716630Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/commands_generator.rb:19:in start'
2021-12-22T13:41:25.5718090Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/fastlane/lib/fastlane/cli_tools_distributor.rb:114:in take_off' 2021-12-22T13:41:25.5719490Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/bin/fastlane:23:in <top (required)>'
2021-12-22T13:41:25.5720740Z from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in load' 2021-12-22T13:41:25.5721910Z from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in
'
2021-12-22T13:41:25.5723370Z /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in initialize': string contains null byte (ArgumentError) 2021-12-22T13:41:25.5724890Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in new'
2021-12-22T13:41:25.5727030Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in create' 2021-12-22T13:41:25.5728480Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:49:in from_json_file'
2021-12-22T13:41:25.5729920Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:33:in from' 2021-12-22T13:41:25.5731260Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/manager.rb:23:in login'
2021-12-22T13:41:25.5732610Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/manager.rb:19:in start' 2021-12-22T13:41:25.5734180Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/build_manager.rb:17:in upload'
2021-12-22T13:41:25.5735680Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/commands_generator.rb:67:in block (2 levels) in run' 2021-12-22T13:41:25.5737030Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
2021-12-22T13:41:25.5738370Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 2021-12-22T13:41:25.5739750Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
2021-12-22T13:41:25.5741190Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:117:in run!' 2021-12-22T13:41:25.5742590Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
2021-12-22T13:41:25.5744360Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/commands_generator.rb:167:in run' 2021-12-22T13:41:25.5745800Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/pilot/lib/pilot/commands_generator.rb:19:in start'
2021-12-22T13:41:25.5747260Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/fastlane/lib/fastlane/cli_tools_distributor.rb:114:in take_off' 2021-12-22T13:41:25.5748660Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/bin/fastlane:23:in <top (required)>'
2021-12-22T13:41:25.5749910Z from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in load' 2021-12-22T13:41:25.5751100Z from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in '
2021-12-22T13:41:25.5788050Z ##[error]Error: The process '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane' failed with exit code 1
2021-12-22T13:41:25.5806900Z ##[section]Finishing: Publish to the App Store TestFlight track

(nice if you could space the output.. :)
I was experiencing this issue in my pipeline. The culprit is
2021-12-22T13:41:25.5723370Z /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in initialize': string contains null byte (ArgumentError) 2021-12-22T13:41:25.5724890Z from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.199.0/spaceship/lib/spaceship/connect_api/token.rb:71:in new'
Fastlane requires the .p8 key file in your service connection to be base64 encoded to use in the AppStoreRelease#1 task.
The issue is described here: https://github.com/microsoft/app-store-vsts-extension/issues/219
Try updating your service connection Key Content with a base64 encoded key. You can use the tool https://www.base64encode.org/ to complete online

Related

cron.yaml key not found "cron" upon deployment of simple hello world app

I am trying to deploy an elasticbeanstalk worker environement for my laravel application using the eb cli bit facing same issue as this question (apologies I was not able to upvote or comment).
I followed step by step instructions to use the laravel-aws-dusterio package. Upon creating a new worker environment (eb create -t worker), I run into this deployment error:
2020-07-12 12:36:31 ERROR [Instance: i-xxxxxxx] Command failed on instance. An unexpected error has occurred [ErrorCode: 0000000001].
2020-07-12 12:36:31 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2020-07-12 12:37:34 ERROR Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.
Upon checking the logs I found the following:
init: initializing aws-sqsd 3.0.1 (2020-03-30)
init: Failed of parsing file 'cron.yaml', because: key not found: "cron" (AWS::EB::SQSD::ScheduleParser::ScheduleFileError)
at /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/schedule_parser.rb:99:in `rescue in v1_parser'
...
caused by: key not found: "cron" (KeyError)
The cron.yaml file is place into the main/root folder of the project and is the following:
version: 1
cron:
- name: "schedule"
url: "/worker/schedule"
schedule: "* * * * *"
If I remove the cron.yaml the deployment is successful, however the worker will not receive the jobs posted from the sqs daemon. The web application is working correctly being able to queue jobs.
I can ssh into the ec2 instance but not sure what I could do to troubleshoot.
I am really struggling to fix this issue. Thanks for your help.
EDIT
Trying to isolate the problem, I created a simple hello world application with a cron.yaml file as well.
This is the content of index.php
index.php
<?php echo("hello world"); ?>
This is the content of cron.yaml
version: 1
cron:
- name: "schedule"
url: "/worker/schedule"
schedule: "* * * * *"
Step1: deploy application
eb create testworker-dev
the application is create successfully
eb create -t worker
the application is deployed but get same error as before parsing the cron.yaml
init: initializing aws-sqsd 3.0.1 (2020-03-30)
2020-07-12T23:34:04Z init: Failed of parsing file 'cron.yaml', because: key not found: "cron" (AWS::EB::SQSD::ScheduleParser::ScheduleFileError)
at /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/schedule_parser.rb:99:in `rescue in v1_parser'
...
caused by: key not found: "cron" (KeyError)
at /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/schedule_parser.rb:82:in `fetch'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/schedule_parser.rb:82:in `v1_parser'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/schedule_parser.rb:59:in `load_schedule'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/schedule_parser.rb:131:in `load_schedule'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/cron.rb:26:in `initialize'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/daemon.rb:47:in `new'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/lib/aws-sqsd/daemon.rb:47:in `initialize'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/bin/aws-sqsd:34:in `new'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/bin/aws-sqsd:34:in `start'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/bin/aws-sqsd:83:in `launch'
from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.1/bin/aws-sqsd:111:in `<top (required)>'
from /opt/elasticbeanstalk/lib/ruby/bin/aws-sqsd:23:in `load'
from /opt/elasticbeanstalk/lib/ruby/bin/aws-sqsd:23:in `<main>'
So the issue appear to be not in the application code itself. The aws-sqs is throwing an error when parsing the cron.yaml.

Gitlab standalone installation failed

I'm using
Ubuntu 18.04 server
Trying to install Gitlab standalone using this blog and official one too
I am getting the below error:-
Running handlers:
There was an error running gitlab-ctl reconfigure:
bash[migrate gitlab-rails database] (gitlab::database_migrations line 49) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of "bash" "/tmp/chef-script20180927-7185-157g8fm" ----
STDOUT: rake aborted!
PG::ConnectionBad: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:51:in `block (3 levels) in <top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => gitlab:db:configure
(See full trace by running task with --trace)
STDERR:
---- End output of "bash" "/tmp/chef-script20180927-7185-157g8fm" ----
Ran "bash" "/tmp/chef-script20180927-7185-157g8fm" returned 1
Running handlers complete
Chef Client failed. 4 resources updated in 01 minutes 21 seconds
I thought I was messing up with the URL.
$grep "external" /etc/gitlab/gitlab.rb | head -n 3
##! For more details on configuring external_url see:
##! https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab
external_url 'http://192.168.4.215'
I tried varius options for external_url like
IP address
domain name
Let me know what is going wrong.
I had the same problem and found a workaround here:
gitlab.com/gitlab-org/omnibus-gitlab/issues/3744
Doing the following steps solved the problem:
sudo systemctl disable gitlab-runsvdir
sudo systemctl enable gitlab-runsvdir
sudo gitlab-ctl restart

"Element not found" exception in Jenkins box while script passing in local

Im trying to read the text from a popup and assert it.The element is defined as
div(:cta_description, :class => 'homepage-clicktoactiavte-description')
And the method as
def rewards_popup_description
return cta_description_element.when_present.text.gsub(/[^$,.A-Za-z0-9]/," ")
end
This script passes successfully while running in local, but fails with the following exception while running directly on Jenkins box which is another windows machine.
And the customer sees the overlay popup message "$10 reward activated"
features/step_definitions/Loyalty_steps.rb:7
timed out after 30 seconds, Element not present in 30 seconds (Watir::Wait::TimeoutError)
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/watir-6.12.0/lib/watir/wait.rb:49:in `until'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/watir-6.12.0/lib/watir/wait.rb:126:in `wait_until'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/elements/element.rb:133:in `when_present'
D:/Jenkins/workspace/cog-checkout-loyalty-nightly-cuke-tests/cuke-tests/features/support/pages/Frontend/Cotton_On/Loyalty_Page.rb:14:in `rewards_popup_description'
D:/Jenkins/workspace/cog-checkout-loyalty-nightly-cuke-tests/cuke-tests/features/step_definitions/Loyalty_steps.rb:9:in `block (2 levels) in '
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/page_factory.rb:75:in `on_page'
D:/Jenkins/workspace/cog-checkout-loyalty-nightly-cuke-tests/cuke-tests/features/step_definitions/Loyalty_steps.rb:8:in `block in '
C:/Ruby24-x64/bin/cucumber:23:in `load'
C:/Ruby24-x64/bin/cucumber:23:in `'
features/Loyalty-AU.feature:122:in `And the customer sees the overlay popup message "$10 reward activated"'
Both the machines have same version of following packages
page-object (2.2.4)
watir (6.12.0)
watir-scroll (0.2.0)
watir-webdriver (0.9.9)
Both the machines use same version of chromedriver as well
$ chromedriver.exe -v
ChromeDriver 2.41.578737 (49da6702b16031c40d63e5618de03a32ff6c197e)
C:\Program Files (x86)\Google\Chrome\Application>chromedriver.exe -v
ChromeDriver 2.41.578737 (49da6702b16031c40d63e5618de03a32ff6c197e)
Any idea what could be wrong?
Note:-
I ran the script directly from Jenkins box. Its a Windows Server 2016 edition.When the script runs I can see the popup appears and its stays for 10seconds(configured time) and then disappears. Then it fails complaining "Element no found".
The local is Windows 7 machine..

Why puppet beaker fails to resolve role "agent", whereas master/database/dashboard works just fine?

I have the nodeset definition as follows..
---------- Some of the attributes removed for clarity ----------------------
HOSTS:
kpointvm1.zencite.com:
roles:
- master
hypervisor : vagrant
kpointvm2.zencite.com:
roles:
- agent
hypervisor : vagrant
----------------------
When I run the tests it fails with following stack trace
----------------------
/opt/manish/kpoint_beaker/spec/spec_helper_acceptance.rb:28:in `<top (required)>': undefined local variable or method `agent' for main:Object (NameError)
from /usr/local/rvm/rubies/ruby-1.9.3-p545/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/local/rvm/rubies/ruby-1.9.3-p545/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /opt/manish/kpoint_beaker/spec/acceptance/001_basic_spec.rb:1:in `<top (required)>'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in `load'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in `block in load_spec_files'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in `each'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in `load_spec_files'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:96:in `setup'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:84:in `run'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:69:in `run'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:37:in `invoke'
from /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/exe/rspec:4:in `<main>'
/usr/local/rvm/rubies/ruby-1.9.3-p545/bin/ruby -I/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-support-3.1.0/lib:/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/exe/rspec spec/acceptance --color failed
----------------------
Following is the "on" call ...
on agent, "mkdir -p /tmp/I-am-the-agent"
Surprisingly, if I change role to either master/dashboard/database it runs without
any problem.
I thought "agent" may be a reserved word, though documentation uses it,
I tried with other roles, but that fails too.
My environment is
----------------------
ruby 1.9.3p545 (2014-02-24 revision 45159) [x86_64-linux] (Running in RVM)
beaker (1.19.1)
----------------------
Any idea?
As per Josh on puppet-user google group it seems that I should be using agents and not agent.
There could be more than one agent and hence agents.
The wiki has one example which has correct example of "on agents".
However, some of the DSL call refers to agent and I was tripped by one of these calls.
Update:
After some trial and error I could also use the custom role. The trick is to specify custom role as symbol when referring them in "on" call, e.g. "on :customerole 'do something'".
Looking at the code, it looks likes that Beaker should define methods for these custom roles but somehow it is not doing so.

Script running on Firefox showing error

Showing Error while running script by using Firefox
With user of Roo & test/unit
I call information from excel sheet & user in executing but showing error
Showing Error as below
C:/Ruby193/lib/ruby/gems/1.9.1/gems/ffi-1.0.9-x86-mingw32/lib/ffi/platform.rb:2
: Use RbConfig instead of obsolete and deprecated Config.
Started ChromeDriver
port=52228
version=20.0.1133.0
log=D:\chromedriver.log
C:/Ruby193/lib/ruby/1.9.1/net/protocol.rb:141:in `read_nonblock': An existing c
nnection was forcibly closed by the remote host. (Errno::ECONNRESET)
from C:/Ruby193/lib/ruby/1.9.1/net/protocol.rb:141:in `rbuf_fill'
from C:/Ruby193/lib/ruby/1.9.1/net/protocol.rb:122:in `readuntil'
from C:/Ruby193/lib/ruby/1.9.1/net/protocol.rb:132:in `readline'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:2562:in `read_status_line'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:2551:in `read_new'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1319:in `block in transport_
equest'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1316:in `catch'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1316:in `transport_request'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1293:in `request'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1064:in `head'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.21.2/lib/
elenium/webdriver/chrome/service.rb:62:in `block in stop'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:745:in `start'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:557:in `start'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.21.2/lib/
elenium/webdriver/chrome/service.rb:58:in `stop'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.21.2/lib/
elenium/webdriver/chrome/service.rb:52:in `block in start'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.21.2/lib/
elenium/webdriver/common/platform.rb:124:in `block in exit_hook'
Please check whether you have latest ffi gem installed.
gem install ffi
Then give it a shot.

Resources