In my iOS project i have some run script files in my directory. When using the new Xcode 9 Server feature "Run test in parallel" the xcodebuild failes because it can not open so many times the same file.
The file to be called is here:
/my-ios-project/scripts/my-script.sh
I call it two times in my run script which was never a problem
"${SOURCE_ROOT}"/scripts/my-script.sh first-call-arg
"${SOURCE_ROOT}"/scripts/my-script.sh second-call-arg
Error message says "fork: Resource temporarily unavailable". As far as i know this is because it tries to open one file too many times.
/bin/sh -c \"/Users/xcodeserver/Library/Caches/XCSBuilder/Bots/4449e5bcbfaa89a18949b4b093185630/DerivedData/Build/Intermediates.noindex/my-ios-project.build/Release-iphonesimulator/my-scheme.build/Script-21A92E061D93E0B700C4948E.sh\"
/Users/xcodeserver/Library/Caches/XCSBuilder/Bots/4449e5bcbfaa89a18949b4b093185630/Source/my-ios-project/scripts/my-script.sh: fork: Resource temporarily unavailable
/Users/xcodeserver/Library/Caches/XCSBuilder/Bots/4449e5bcbfaa89a18949b4b093185630/Source/my-ios-project/scripts/my-script.sh: fork: Resource temporarily unavailable
Anyone experience with this?
Most probably there would be a recursive call involved. Check that you are not naming your bash functions and external functions the same.
Related
First of all, I'm using firebase crashreporting since February. Because of bitcode (for the prod versions), I need to download DSYMs and upload from terminal. It's all ok, but today, I faced that the script that I used not working anymore. I did NOT changed anything, nor in the service account files, nor in the script.
I'm getting a warning, that my service account file is not like a service account file
./Pods/FirebaseCrash/batch-upload /Project/ServiceAccount.json F3B……..5272
./Pods/FirebaseCrash/batch-upload:83: warning: The first argument does not look like a service account file.
./Pods/FirebaseCrash/batch-upload:127: warning: Running extract-keys on desktop.
I used this script previously, which not worked today:
./Pods/FirebaseCrash/batch-upload /ProjectName/Firebase_Crash.json B5CF...8A
And the working one...:
./Pods/FirebaseCrash/batch-upload ./ProjectName/Firebase_Crash.json B5CF...8A
This one also works:
./Pods/FirebaseCrash/batch-upload -i ./ProjectName/Info.plist -p ./ProjectName/GoogleService-Info.plist ./ProjectName/Firebase_Crash.json B5CF...8A
I see below error while packaging appium project for AWS.
Unknown lifecycle phase --DskipTests=true. You must specify a valid lifecycle phase or a goal in the format
Note:
Executing packaging command on mac terminal
Tried both --DskipTests=true & -DskipTests=true (see same error for both)
Looking forward for some help. Thanks!
I work for the AWS Device Farm team.
I have seen this error when users copy-paste the command from the documentation.
We are working on updating this as there seems to be some unknown characters that get introduced.
Users have got this to work by deleting -DskipTests=true and typing it instead of copy pasting it.
Since you are on a Mac terminal you will need to use a single dash '-' for the parameter.
Apologies for the inconvenience.
Hope this helps.
The error I'm seeing is as follows:
Test target PrototypeTests encountered an error (The operation couldn’t be completed. Too many open files in system. Too many open files in system)
Test target Prototype Integration Tests encountered an error (The operation couldn’t be completed. Too many open files in system. Too many open files in system)
I am able to run the analyze and archive actions with no problems but enabling the test action causes the above errors. I've even tried this with empty tests and the problem still persists.
The output of sudo launchctl limit maxfiles on my server is:
maxfiles 256 unlimited
Please let me know if I can provide any more information.
You need to increase your ulimit. You should add the line:
ulimit -n 4096
in your ~/.profile or similar.
The reason you have to add this line to your bash launch file is because just running sudo ulimit -n 4096 will only change the limit in current bash session.
I received this same message while trying to compile while low RAM, low disk space, and many open apps & files on my desktop. Closing most of them and emptying the trash resolved the issue.
Im trying to translate my chrome app to ios. I run the command cca create myapp --copy-from=manifest.json Some errors exist cp: copyFileSync: could not write to dest file (code=ENAMETOOLONG): $PATH_TO_PROJECT/project/platforms/ios/www/platform/..../www/platform/config.xml
where .... is 40 repeated directories of /www/platform
The translation succeeds and im able to run my project with android however, when trying to run in xcode i see an almost identical error saying File name too long.
Anyone have simmilar issues? Anyone able to get ios translations to run?
This is the result of a bug in the way we "import" your project when you specify --copy-from or --link-to arguments to cca create when your import directory is the same as your output directory.
Since the import in your example is a parent folder of the output, it copies itself over and over, recursively until the system kills the process. We have added protection against doing this (by warning during cca create if we detect this case), but that version hasn't released to npm just yet (sorry!).
The fix for the issue is simple: just create your project in another directory that is outside of your packaged app! i.e., either:
# From within packaged app directory
cca create ../myapp --copy-from=./manifest.json
or
# From outside packaged app directory
cca create myapp --copy-from=$APP_DIR/manifest.json
i am getting this
Windows could not start the SphinxSearch service on Local Computer.
Error 1067: The process terminated unexpectedly.
i got installation instruction from this .
http://blog.robbsnet.com/2011/07/how-to-install-and-implement-sphinx.html
build process is complete but when i start the sphinx search service i got errors .
Try running searchd manually from Command Prompt. Maybe it will give you a useful error message.
Try also looking in searchd.log
For anyone who is still having problems with the Windows service:
Make sure your configuration is correct for both database and paths and the needed folders & files are created.
Make sure that the service "command" matches the correct paths and files, to do so you have to:
Run administrative tools, click on local services, then find SphinxSearch. Click on its properties and read the line the service is trying to execute. If the configuration path doesn't match the service start command, it will fail to start.
FYI, this can also happen because your search data files are corrupt. Easy fix for that is to nuke the files and refill them.