Home → Problems →

Build failures

• Edit

Kévin Lovato

16 Apr, 2015 04:32 PM

Hi,

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.
For example this build failed to restore nuget packages (https://ci.appveyor.com/project/TechABC/zebus/build/1.2.4) and some others timed out in performance tests (that usually work) (https://ci.appveyor.com/project/TechABC/zebus/build/1.2.8).

Is there any issue at the moment on your infrastructure ?

Thanks

1. Support Staff 1 Posted by Feodor Fitsner on 16 Apr, 2015 04:41 PM

   

   For nuget restore try adding -verbosity detailed 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: http://www.appveyor.com/docs/build-cache

   Regarding performance tests - I'm not sure about the reason of their failure without looking into them.

   • Edit

2. 2 Posted by Alprema on 16 Apr, 2015 04:48 PM

   

   Alright, I'll look into it more seriously if it continues.

   • Edit

3. 3 Posted by Alprema on 17 Apr, 2015 05:27 AM

   

   Hi,

   The NuGet issue happened again today (
   https://ci.appveyor.com/project/TechABC/zebus/build/1.2.13) that's twice in
   two days where it never happened to me on AppVeyor before for weeks, are
   you sure everything is alright ?

   Kévin

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 17 Apr, 2015 06:21 AM

   

   NuGet has been really unstable recently: http://status.nuget.org/

   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.

   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.

   To minimize your dependency from availability of external services we recommend using build cache (where applicable): http://www.appveyor.com/docs/nuget#use-build-cache-for-nuget-packages

   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...

   • Edit

5. 5 Posted by Alprema on 17 Apr, 2015 06:28 AM

   

   Ok, I reproduced the issue locally too, it was totally a NuGet.org issue,
   so I took your advice and enabled the build cache.

   Thank you for your quick support,

   Kévin

   • Edit

6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:55 AM.