Bug 58642 - A Xamarin.iOS build from msbuild windows should fail fast if the mac agent fails
Summary: A Xamarin.iOS build from msbuild windows should fail fast if the mac agent fails
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.6.0 (15.3)
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-08-08 14:10 UTC by Jerome Laban
Modified: 2017-11-21 18:17 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 for Bug 58642 on Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:

Description Jerome Laban 2017-08-08 14:10:27 UTC
Using Xamarin, when doing a command line build from a windows machine, if the build starts properly and sends its payload to the mac, and the mac agent fails for some reason (e.g. no space left on device), then the Windows msbuild will stall indefinitely, even if those error messages appear on the windows side.

The msbuild task on Windows should fail faster when an error occurs on the mac side.
Comment 1 Prashant [MSFT] 2017-08-09 05:31:50 UTC
Thanks so much for taking the time to submit this report! 
Could you run the msbuild with /v:diag flag, and share the output?

Also, please attach the following to help us reproduce this issue:

-Detailed reproduction steps
-Version information (Help → About Microsoft Visual Studio → Copy Info)
-Logs (Help → Xamarin → Zip Logs (last 7 days))
-Optional: project to reproduce your issue
Comment 2 Prashant [MSFT] 2017-09-11 05:34:11 UTC
Because we have not received a reply to our request for more information, we are marking this issue as RESOLVED→NORESPONSE. If you are still encountering this issue on the latest Visual Studio 2017 version 15.3.3, please don’t hesitate to reopen the ticket with the requested information. 

Comment 3 Jerome Laban 2017-11-21 18:04:20 UTC
Hi, So I have not been able to capture a relevant scenario for the original error, but it is actually easier to reproduce with the following scenario:

- Have an iOS compile properly using a mac connection, from an msbuild VSTS task.
- Reboot the mac, but don't log in
- The logs will display an error saying the mac needs to be logged in, but the msbuild task will not fail until the VSTS Build definition timeout has been reached.

The error should be reported immediately by the xamarin.ios build tasks and be terminated as an error. It currently is reported as a warning, and does not fail.
Comment 4 Jerome Laban 2017-11-21 18:17:13 UTC
Just a clarification, the MSBuild tasks are running on a Windows machine, connecting to a mac machine for the build through mtbs.