running bwoken from jenkins - jenkins

We're trying to set up continuous integration test on our iOS project and running into some issue running broken from Jenkins.
The error we are getting is the following:
iphone Add measurment from CNX.js
/Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script.rb:55:in `run': Test Script Failed (Bwoken::ScriptFailedError)
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open3.rb:86:in `popen3'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script.rb:53:in `run'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:1427:in `to_proc'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/simulator_runner.rb:21:in `each'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/simulator_runner.rb:21:in `execute'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script_runner.rb:33:in `execute_for_family'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script_runner.rb:28:in `execute_in_simulator'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script_runner.rb:27:in `each'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script_runner.rb:27:in `execute_in_simulator'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/script_runner.rb:20:in `execute'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/cli/test.rb:105:in `test'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/cli/test.rb:71:in `run'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/lib/bwoken/cli.rb:56
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /Library/Ruby/Gems/1.8/gems/bwoken-2.0.0.beta.2/bin/bwoken:3
from /usr/bin/bwoken:19:in `load'
from /usr/bin/bwoken:19
Recording cancelled : At least one target failed to launch; aborting run
Error Domain=com.apple.instruments Code=1 "Error Starting Recording" UserInfo=0x7fa5632b19f0 {NSLocalizedDescription=Error Starting Recording, NSLocalizedRecoverySuggestion=At least one target failed to launch; aborting run}[m
Failed to start trace.[m
Build step 'Execute shell' marked build as failure
Finished: FAILURE
I think the important part is here:
Recording cancelled : At least one target failed to launch; aborting run
mError Domain=com.apple.instruments Code=1 "Error Starting Recording" UserInfo=0x7fa5632b19f0 {NSLocalizedDescription=Error Starting Recording, NSLocalizedRecoverySuggestion=At least one target failed to launch; aborting run}
I can't make sense of it right now, so any help is appreciated.
Thanks, olivier

WE got it running using the jenkins app (https://github.com/stisti/jenkins-app). The issue is related to the fact that Jenkins runs as a deamon and thus does not have access to the window server.
There might be another way around this (changing the Jenkins user type), but running jenkins as an app works for us

Related

The 'Pods-Runner' target has transitive dependencies that include statically linked binaries: (.../ios/Flutter/Flutter.framework)

After upgrading to flutter version 1.17.4 when running flutter build ios I get following output:
[!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries: (.../ios/Flutter/Flutter.framework)
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/xcode/target_validator.rb:84:in `block (2 levels) in verify_no_static_framework_transitive_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/xcode/target_validator.rb:74:in `each_key'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/xcode/target_validator.rb:74:in `block in verify_no_static_framework_transitive_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/xcode/target_validator.rb:73:in `each'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/xcode/target_validator.rb:73:in `verify_no_static_framework_transitive_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/xcode/target_validator.rb:38:in `validate!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer.rb:590:in `validate_targets'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer.rb:158:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'
Error running pod install
What I tried:
Deleting ios/Flutter/Flutter.framework and running pod install as suggested here didn't help
Adding s.static_framework = true to Flutter.podspec - no luck
Deleting-recreating ios folder - no luck
Commenting out use_frameworks! in Podfile - leads to errors in plugins like fatal error: '..._plugin-Swift.h' file not found
I also tried to downgrade the flutter as I didn't have any problem with prev one. But running flutter version v1.17.2 resulted in error:
Error: ProcessException: Process exited abnormally:
error: unsupported sort specification 'creatordate'
I'm stuck with this.
If this issue occured while you trying to implement your own flutter plugin, then simply add this line below dependencies to .podspec
s.static_framework = true
I get same problem with this error output:
[!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries:
(/.../ios/Flutter/Flutter.framework)
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/xcode/target_validator.rb:84:in `block (2 levels) in
verify_no_static_framework_transitive_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/xcode/target_validator.rb:74:in `each_key'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/xcode/target_validator.rb:74:in `block in verify_no_static_framework_transitive_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/xcode/target_validator.rb:73:in `each'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/xcode/target_validator.rb:73:in `verify_no_static_framework_transitive_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/xcode/target_validator.rb:38:in `validate!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer.rb:595:in `validate_targets'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer.rb:162:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'
I have solved problem with tried this step:
Open your folder ios in your project and open Podfile and you will see code like this:
target 'Runner' do
use_frameworks!
use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
end
end
You can remove code use_frameworks! and use_modular_headers! and this is complete code:
target 'Runner' do
flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
end
end
If you have follow instruction you can save change file and hit flutter run
This is complete output:
Running pod install... 3.1s
Running Xcode build...
└─Compiling, linking and signing... 28.0s
Xcode build done. 73.0s
Waiting for iPhone 12 Pro Max to report its views... 19ms
Syncing files to device iPhone 12 Pro Max... 1,218ms
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h Repeat this help message.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
An Observatory debugger and profiler on iPhone 12 Pro Max is available at: http://127.0.0.1:50854/VhaUEREqLb0=/
*Disclaimer:
I'm quite new to programming & coding and Flutter is my first programming language. But having struggled with this for 3 days, I believe I have fixed my code. Hoping this helps. Please excuse if this doesn't make sense.
Other Newbies reading this: Do this only if you have a backup of your script, and all of above solutions failed for you.*
Background
My problem occurred when I upgraded Xcode to 12.0.1. Got the same error:
The 'Pods-Runner' target has transitive dependencies that include statically linked binaries:
I believe in the upgrade process, some link in an unknown location broke between Flutter, Cocoa-pods & Xcode. I wasn't sure whether something broke internally within my project or within the platforms. Hence, I launched a new flutter project and confirmed it was the latter when that brand new project failed to launch on the Simulator.
Solution
My solution was to rejig the whole platform architecture, rather than re-writing the whole app code.
Step 1: Take a backup of your code (I didn't; got lucky or was just tired with the multiple iterations & backups.)
Step 2: Uninstalled Flutter (Restarted the Mac) and then Reinstalled Flutter on VSCODE
Step 3: Completely Uninstalled Cocoa-pods & Reinstalled Cocoapods. Followed the steps mentioned here.
[Now in your Project]
Step 4: In the terminal, type 'flutter clean' to clean all caches pre-built for the project
Step 5: Delete (or Rename) '/ios' folder (to something else like '/111ios')
Step 6: Recreate a new /ios folder. In the terminal, type
flutter create -i swift
You might need to specify your root PWD for the command to build the ios folder in the right directory.
Step 7: Get packages
flutter pub get
Step 8: Flutter Run.
The above got my boat sailing again. Hopefully this helps the community!

Chef - Recipe package fails to find candidate version

I am installing and configuring a very basic Jenkins installation using Chef. When i attempt to run the following recipe:
include_recipe "apt::default"
apt_repository "jenkins" do
uri "http://pkg.jenkins-ci.org/debian"
key "http://pkg.jenkins-ci.org/debian/jenkins-ci.org"
components ["binary/"]
action :add
end
package "jenkins" do
version '2.62'
end
service "jenkins" do
supports [:stop, :start, :restart]
action [:start, :enable]
end
I receive the following errors (displayed in the terminal):
192.168.9.207 [2017-05-25T10:50:58-04:00] ERROR: Running exception handlers
192.168.9.207 Running handlers complete
192.168.9.207 [2017-05-25T10:50:58-04:00] ERROR: Exception handlers complete
192.168.9.207 Chef Client failed. 2 resources updated in 20 seconds
192.168.9.207 [2017-05-25T10:50:58-04:00] INFO: Sending resource update report (run-id: 2b59b80e-b787-4e93-805b-837b4d3264fb)
192.168.9.207 [2017-05-25T10:50:58-04:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
192.168.9.207 [2017-05-25T10:50:58-04:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
192.168.9.207 [2017-05-25T10:50:58-04:00] ERROR: apt_package[jenkins] (jenkins-installation::default line 21) had an error: Chef::Exceptions::Package: No candidate version available for jenkins
192.168.9.207 [2017-05-25T10:50:58-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
The error explains that there is no candidate version available for Jenkins. After the run fails, if I run sudo apt-get update on the managed node I receive the following error:
Err http://pkg.jenkins-ci.org trusty/binary/ amd64 Packages
404 Not Found
Err http://pkg.jenkins-ci.org trusty/binary/ i386 Packages
404 Not Found
Ign http://pkg.jenkins-ci.org trusty/binary/ Translation-en_US
Ign http://pkg.jenkins-ci.org trusty/binary/ Translation-en
Fetched 5,976 kB in 3s (1,528 kB/s)
W: Failed to fetch http://pkg.jenkins-ci.org/debian/dists/trusty/binary//binary-amd64/Packages 404 Not Found
W: Failed to fetch http://pkg.jenkins-ci.org/debian/dists/trusty/binary//binary-i386/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
I am fairly new to Chef. This error appears to be related to retrieving a Jenkins package, however I am not sure how to remedy this error. Please let me know if additional information is required to troubleshoot this issue.
Thank you to everybody in advance for any guidance you are able to provide. I have searched through the Chef documentation but haven't seen much aside from specifying the package version: https://docs.chef.io/resource_package.html.
Specify distribution 'binary/' instead of components 'binary/'. This will fix the 404s that you get because of trusty/binary/.
At least, this is what I see from the "official" Jenkins cookbook, which I btw. suggest to use.
EDIT: So the result would be:
apt_repository "jenkins" do
uri "http://pkg.jenkins-ci.org/debian"
key "http://pkg.jenkins-ci.org/debian/jenkins-ci.org"
distribution "binary/"
end

Can not generate openaplr.framework in mac by using OpenALPR library

I am using https://github.com/twelve17/openalpr-ios this library to analyse license plate images and get license number from it.
when i try to run ruby script in mac to generate openaplr.framework it gives me error.
This is the error i am getting.
"/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/utils.rb:44:in
execute': Child returned: pid 587 exit 1 (RuntimeError) from
/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/utils.rb:74:inlog_execute'
from
/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/package/automake.rb:141:in
do_autoconf_build' from
/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/package/automake.rb:58:inbuild_arch'
from
/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/package/base.rb:53:in
block in install' from
/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/package/base.rb:52:ineach'
from
/Volumes/DATA/Project_Stuff/openalpr-ios/lib/alpr/package/base.rb:52:in
install' from ./bin/build_frameworks.rb:53:in
Thanks.
I had the same issue and fixed it by comment line:
#opts[:exit_on_error] = true if !opts.has_key?(:exit_on_error)
in file utils.rb line number 24.
System Mac OSX10.10, xCode7.2.1

symbol lookup error when running the MoveIt! GUI

I am running Kubuntu 12.04.4 LTS and ROS Hydro.
When trying to complete the MoveIt! Setup Assistant Tutorial here
http://docs.ros.org/hydro/api/moveit_setup_assistant/html/doc/tutorial.html
everything is working fine until I try Step 4. When I click the "Add Group" button, the MoveIt! Setup Assistant GUI closes and I get the following error:
/opt/ros/hydro/lib/moveit_setup_assistant/moveit_setup_assistant: symbol lookup error: /opt/ros/hydro/lib/libmoveit_setup_assistant_widgets.so: undefined symbol: _ZN3ros7package10getPluginsERKSsS2_RSt6vectorISsSaISsEEb
================================================================================REQUIRED process [moveit_setup_assistant-2] has died!
process has died [pid 14775, exit code 127, cmd /opt/ros/hydro/lib/moveit_setup_assistant/moveit_setup_assistant __name:=moveit_setup_assistant __log:=/home/scratch/.ros/log/a83de36e-06f4-11e4-bcc4-001fd081bf4b/moveit_setup_assistant-2.log].
log file: /home/scratch/.ros/log/a83de36e-06f4-11e4-bcc4-001fd081bf4b/moveit_setup_assistant-2*.log
Initiating shutdown!
================================================================================
[moveit_setup_assistant-2] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
Does anyone know what's going on? Thanks

Specflow tests does not show results until finished

I am running a large amounts of specflow tests that take a while to run. I have these running on a build server - and I can see the output while these are running.
[10:59:13][Step 3/3] Results Top Level Tests
[10:59:13][Step 3/3] ------- ---------------
[10:59:13][Step 3/3] Passed Project.Web.Specflow.Specs.Account.ForgotPasswordsFeature.ExistingUserHasForgottenTheirPassword
[10:59:23][Step 3/3] Passed Project.Web.Specflow.Specs.Account.ForgotPasswordsFeature.Non_ExistingUserHasForgottenTheirPassword
[10:59:32][Step 3/3] Failed Project.Web.Specflow.Specs.Admin.AdminTabFeature.AdminUserLoggedIn
[10:59:45][Step 3/3] Failed
etc.
All I can see is whether a scenario has passed or failed. I would like to see the error message when these tests fail. These error messages are only revealed at the end of the test run. Is there a way to reveal the report during the test run rather at the end of the test run? This way I can start analysing the failures rather than having to wait 30 min.
Thanks!

Resources