Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
We had a Kerberos failure on our build mac due to clock drift because we hadn't enabled NTP. This took a bit longer to find that it needed to because the task that caught the failure on the msbuild didn't report any errors, so the only indication of the problem was that at the end of the build msbuild exited with code 1 and we ended up having to pore through detailed logs to find the problem.
Specifically, in this snippet of logs, I would expect an error statement to be output to the log:
Using "DetectSdkLocationsTask" task from assembly "<XXX>\MSBuild\Xamarin\iOS\Xamarin.iOS.Tasks.dll".
Task "DetectSdkLocationsTask" (TaskId:12)
Executing task: Xamarin.iOS.Tasks.DetectSdkLocationsTask (TaskId:12)
Server returned an error. The remote server returned an error: (429).
Server error code: 429
This request has already been processed
Remote task execution failed. (TaskId:12)
Done executing task "DetectSdkLocationsTask" -- FAILED. (TaskId:12)
10:19:43.767 13>Done building target "_DetectSdkLocations" in project "<XXX>.csproj" -- FAILED.: (TargetId:14)
This is similar to bug 23072 in that there was an error due to a time mismatch between the Windows and OSX machines, but the error is manifesting differently (and likely warrants a different fix).
We hit the same problem in the target _CompiledToNative; our Mac had frozen and was not responding to calls, so the build failed, but since nothing was explicitly logged as an error all we saw on the build server was that msbuild exited with code 1, had to go through the logs to find out what had actually failed and why.
The current alpha version contains several improvements which should fix this problem.