Failed to publish the nuget package due to time out issue - build

Our builds on TFS fail intermittently with the following error . when the build step "Nuget publisher(version 0)" hits the default 5minutes timeout I get this error. This seems to be not relevant to a particular build machine or build agent.
System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at NuGet.CommandLine.Command.Execute() at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args) ---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.<--
I have tried to updated the nuget publish step to version 2.0 but it didn't resolved the issue.
Currently we are on TFS 2018 with build agent version 2.122.1
Please go to the following Image to see the error.
enter image description here
Any advice is highly appreciated ​

Related

mlUnitTest not working for MarkLogic Unit Testing

I have setup the UnitTetsing Framework for Marklogic using the below url-
https://github.com/marklogic-community/marklogic-unit-test
I am able to deploy my project using mlDeploy and able to load my Testing module using mlUnitTestLoadModules but while running the test cases from gradle mlUnitTest i am getting the below error-
Task ':mlUnitTest' is not up-to-date because:
Task has not declared any outputs.
Releasing connection
:mlUnitTest (Thread[Daemon worker Thread 16,5,main]) completed. Took 0.064 secs
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':mlUnitTest'.
> java.lang.NullPointerException (no error message)
* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to
get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
Any Suggestions ??
We had this issue come up recently when migrating to marklogic-unit-test-1.0.0. There is a work around thanks to one of the MarkLogic gurus. If this is still an
issue let us know.

Shiny deployment error

When I am trying to deploy my shiny app at shinyapps.io I get below error :
> deployApp()
Preparing to deploy application...DONE
Uploading bundle for application: 187055...DONE
Deploying bundle: 857060 for application: 187055 ...
Waiting for task: 416072120
building: Processing bundle: 857060
building: Parsing manifest
building: Building image: 849457
building: Installing system dependencies
################################ Begin Task Log ################################
[2017-06-07T17:28:40.200495546+0000] Execute script: packages/build/nloptr.sh
+ set -e
+ VERSION=2.4.2
+ cd /tmp
+ curl -O http://ab-initio.mit.edu/nlopt/nlopt-2.4.2.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0################################# End Task Log #################################
Error: Unhandled Exception: Child Task 416072122 failed: Error building image: Build exited with non-zero status: 56
Has anyone come across this error. Appreciate if someone help me on how to resolve this. I am using R version 3.4.0
Thanks,
It looks like your app require NLopt, but shinyapps.io failed to install the package. The package installation seemed to be some shell script which may not work in the shinyapps.io server(because of permission etc).
Basically the deployment process scan your file and environment, then try to duplicate the dependency packages in the server. If you used CRAN version the server will also install CRAN version, which should not need build from source or running some shell script. If you used github version server will also try to use github version or build from source, which could have more dependency requirement.
Another possibility is the R package is just the interface and you need to install the actual library, which failed to be installed in server.
R packages will often rely on operating system packages to be
installed on the server. If your application happens to use an R
package that requires a system library that is not installed by
default, please let us know by filing an issue, or a pull request, at
shinyapps-package-dependencies

Installing php5-openssl on Amazon SUSE SE 11 SP3

I have a SUSE ES 11 SP3 Amazon EC2 instance and I need to install the php5-openssl package, but I'm getting in trouble when using "zypper install". I should have upgraded the insance infrastructure update (more details here), but I missed the deadline and I am now with a useless instance, because I can not install anything .
Whenever I use zypper install I got:
Refreshing service 'susecloud'.
Problem retrieving the repository index file for service 'susecloud':
Download (curl) error for 'http://sa-east-1-ec2-update.susecloud.net/repo/repoindex.xml?cookies=0':
Error code: Connection failed
Error message: Couldn't resolve host 'sa-east-1-ec2-update.susecloud.net'
Check if the URI is valid and accessible.
Error building the cache:
[|] Valid metadata not found at specified URL(s)
Warning: Disabling repository 'php' because of the above error.
Download (curl) error for 'http://sa-east-1-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: Couldn't resolve host 'sa-east-1-ec2-update.susecloud.net'
Abort, retry, ignore? [a/r/i/? shows all options] (a): a
Problem retrieving files from 'SLE11-SDK-SP3-Pool'.
Download (curl) error for 'http://sa-east-1-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: Couldn't resolve host 'sa-east-1-ec2-update.susecloud.net'
Please see the above error message for a hint.
Warning: Disabling repository 'SLE11-SDK-SP3-Pool' because of the above error.
Download (curl) error for 'http://sa-east-1-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Updates/sle-11-x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: Couldn't resolve host 'sa-east-1-ec2-update.susecloud.net'
If I try updating the update infrascructure I got:
Adding repository 'tmp_instance_infrastructure_upgrade' [done]
Repository 'tmp_instance_infrastructure_upgrade' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: dir:///usr/share/instance_infrastructure_upgrade/repo
Repository 'tmp_instance_infrastructure_upgrade' priority has been set to 1.
Retrieving repository 'tmp_instance_infrastructure_upgrade' metadata [done]
Building repository 'tmp_instance_infrastructure_upgrade' cache [done]
Specified repositories have been refreshed.
Refreshing service 'susecloud'.
Problem retrieving the repository index file for service 'susecloud':
Download (curl) error for 'http://sa-east-1-ec2-update.susecloud.net/repo/repoindex.xml?cookies=0':
Error code: Connection failed
Error message: Couldn't resolve host 'sa-east-1-ec2-update.susecloud.net'
Check if the URI is valid and accessible.
Error building the cache:
[|] Valid metadata not found at specified URL(s)
Warning: Disabling repository 'php' because of the above error.
Download (curl) error for 'http://sa-east-1-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: Couldn't resolve host 'sa-east-1-ec2-update.susecloud.net'
...
--> Updating packages failed
I tried to install each php5-openssl dependency, downloading each RPM and installing with rpm -i, but every time I resolve one dependency another appears. I also tried the suse forum (post here) but with no success until now.
So my questions are:
Is there some way to fix zypper repositories manually? Even if only to install the php5-openssl package.
Is there some way to use RPM to manage the dependencies for php5-openssl?
Is there another alternative to install php5-openssl in my suse instance?
in short:
you cannot fix these repositories; since they don't exist anymore (try browsing to http://sa-east-1-ec2-update.susecloud.net/).
rpm cannot look for dependencies because rpm does not use repositories (that's where zypper comes in). You can look for rpms on the internet, and then install the manually using rpm; but rpm won't locate the missing rpms.
Yes; as said in point 2; you can look for the rpms; download them and install them manually; or else you can even look for repositories that contain the rpms you want, and add that repository. However be careful with that; since those repositories probably aren't made for Amazon EC2. If you do this; try to find a repository as close as possible to suse 11 EC2...

Fatal error while updating coldfusion

I'm receiving a fatal error while updating the coldfusion10 'C:\ColdFusion10\cfusion\db\slserver54\bin\libeay32.dll (The process cannot access the file because it is being used by another process)'. Following is the entire message,
Failed to copy hotfix files:C:\Documents and Settings\Default
User\762024.tmp\dist\cfusion
Status: FATAL ERROR
Additional Notes: FATAL ERROR - Failed to
copy the hotfix files to the target location:C:\ColdFusion10\cfusion
FATAL ERROR -
C:\ColdFusion10\cfusion\db\slserver54\bin\libeay32.dll (The process
cannot access the file because it is being used by another process)
If someone could let me know as how to resolve this & make the update a successful one I will be more than happy.
I received this exact error as well. To resolve it, I went into the Services Management Console and stopped all the ColdFusion services except the Application Server and restarted the installation process. After the successful update I restarted the services I stopped.

Jenkins - What is consoleFull?

I have a problem for building using Jenkins.
When I uploaded a patch code, build FAILED with this error.
jenkins 3:51 PM
Patch Set 1:
[FAILED] Ant Build -> http://jenkins.lge.com:8086/jenkins/job/AgentApp/1329/consoleFull
What the consoleFull means?
It's just a link - where you can find full console output (logs). Just open http://jenkins.lge.com:8086/jenkins/job/AgentApp/1329/consoleFull -> and check the errors.