The Xamarin Studio build is failing nearly all the time with this error:
It can be seen in the top few builds on the 'Sierra' group in this lane: https://wrench.internalx.com/Wrench/index.aspx?lane=monodevelop-mdaddins-decriptor-msbuild
The latest build on that lane is using Mono JIT compiler version 220.127.116.11 (2017-02/d15985c Mon Mar 27 13:52:01 EDT 2017)
The 'Sierra' group is macos sierra bots, so this is a sierra failure.
We can't get results on El Capitan because the bots are broken again.
There is nothing I can do about this - it's some obscure error on some bot.
And the lane that you linked doesn't even show the problem anywhere.
How do I reproduce this?
Looks like I have the exact same Mono from the 2017-02 lane and my nugget works fine.
This is my Mono:
$ mono --version
Mono JIT compiler version 18.104.22.168 (2017-02/d15985c Mon Mar 27 13:52:01 EDT 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
GC: sgen (concurrent by default)
If anyone needs a nugget to try:
$ git clone email@example.com:xamarin/web-tests.git web-tests-stable
$ cd web-tests-stable
$ git checkout -f jenkins
$ nuget restore Xamarin.WebTests.iOS.sln
(the master branch should work as well)
Can we try that on that bot after installing that Mono and see what happens?
My Mac is macOS Sierra 10.12.3.
In discussions with akoeplinger and jo shields I'm told this is a recurring error with parallel nuget restore with nuget 3 running on mono. It occurs on all three of legacytls, btls and appletls and it is not obviously a problem with tls at all (that is, it could be a bug in our threadpool or socket implementation). Jo just tested and reports he is able to reproduce this on 4.8.
The solution is to invoke nuget with -DisableParallelProcessing , which works around the issue. We should schedule time to fix the underlying issue but not for 15.2.
Assigning to David to fix on the XS build script side
Reassigning since this bug needs to be fixed in Mono, independently of the workaround we can use in XS. Filed bug #54154 to keep track of the application of the workaround.
The underlying issue here is not a 15.2 bug and *probably* is not a Martin bug
Ludovic, can you look at this one, I think this is most likely threadpool or sockets acting out. If you are able to establish TLS is at fault please assign back over to Martin.
Parallel nuget restore was fixed, marking this one too.
Bug bug #54154 is in verified state. Should we mark this defect as Verified as well as per the above comment?
Or do we need to verify this defect in some other build?
Kindly advise on how we should proceed on this.