tag:help.appveyor.com,2012-11-13:/discussions/problems/1994-build-failuresAppVeyor: Discussion 2018-10-19T08:17:09Ztag:help.appveyor.com,2012-11-13:Comment/365995342015-04-16T16:32:41Z2015-04-16T16:32:41ZBuild failures<div><p>Hi,</p>
<p>We just switched to a paying plan after trying it for a week,
and we just experienced some weird build timeouts / failures, which
did not happen during our evaluation.<br>
For example this build failed to restore nuget packages (<a href="https://ci.appveyor.com/project/TechABC/zebus/build/1.2.4">https://ci.appveyor.com/project/TechABC/zebus/build/1.2.4</a>)
and some others timed out in performance tests (that usually work)
(<a href="https://ci.appveyor.com/project/TechABC/zebus/build/1.2.8">https://ci.appveyor.com/project/TechABC/zebus/build/1.2.8</a>).</p>
<p>Is there any issue at the moment on your infrastructure ?</p>
<p>Thanks</p></div>Kévin Lovatotag:help.appveyor.com,2012-11-13:Comment/365995342015-04-16T16:41:34Z2015-04-16T16:41:34ZBuild failures<div><p>For nuget restore try adding <code>-verbosity detailed</code> to
see actual error. There are sometimes intermittent issues on
nuget.org side - unfortunately, this is something we can't always
easily fix from here. Use cache for NuGet packages: <a href="http://www.appveyor.com/docs/build-cache">http://www.appveyor.com/docs/build-cache</a></p>
<p>Regarding performance tests - I'm not sure about the reason of
their failure without looking into them.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/365995342015-04-16T16:48:11Z2015-04-16T16:48:11ZBuild failures<div><p>Alright, I'll look into it more seriously if it continues.</p></div>Alprematag:help.appveyor.com,2012-11-13:Comment/365995342015-04-17T05:27:04Z2015-04-17T05:27:04ZBuild failures<div><p>Hi,</p>
<p>The NuGet issue happened again today (<br>
<a href="https://ci.appveyor.com/project/TechABC/zebus/build/1.2.13">https://ci.appveyor.com/project/TechABC/zebus/build/1.2.13</a>)
that's twice in<br>
two days where it never happened to me on AppVeyor before for
weeks, are<br>
you sure everything is alright ?</p>
<p>Kévin</p></div>Alprematag:help.appveyor.com,2012-11-13:Comment/365995342015-04-17T06:21:57Z2015-04-17T06:21:57ZBuild failures<div><p>NuGet has been really unstable recently: <a href="http://status.nuget.org/">http://status.nuget.org/</a></p>
<p>When you do something locally it usually takes packages from
your local cache, so you can't see most ongoing issues from there.
On AppVeyor you test not only your code, but indirectly test all
external services you depend on, like NuGet, npm, bower, even
GitHub.</p>
<p>I periodically clean NuGet cache on my dev machine (to verify
customer issues) and I can confirm I experienced some lags today
too - adding xunit 2.0 nuget packages to a new project took around
2 minutes! I guess VS, unlike nuget console, has either retry logic
or greater timeout.</p>
<p>To minimize your dependency from availability of external
services we recommend using build cache (where applicable):
<a href="http://www.appveyor.com/docs/nuget#use-build-cache-for-nuget-packages">
http://www.appveyor.com/docs/nuget#use-build-cache-for-nuget-packages</a></p>
<p>I don't know what else to say to make you feel better. Maybe we
should setup kind of monitoring for nuget and other services, if
that helps...</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/365995342015-04-17T06:28:33Z2015-04-17T06:28:33ZBuild failures<div><p>Ok, I reproduced the issue locally too, it was totally a
NuGet.org issue,<br>
so I took your advice and enabled the build cache.</p>
<p>Thank you for your quick support,</p>
<p>Kévin</p></div>Alprema