During AppleSilicon initial bring-up we observed a test failure where the Internal_Convertfwrite(...) function was being called with an empty string. This was being treated as a failure during the MultiByte to utf-8 conversion. For the conversion reporting a failure in this case was incorrect. Therefore a fix was included in #40435.
However, it is not clear why this only occurred for osx-arm64 and not osx-x64.
Temporarily remove the fix and investigate the root cause of why this only occurs on arm64. We would like to be sure the fix is not masking another underlying issue.
See discussion https://github.com/dotnet/runtime/pull/40435/files/e186f0106acfd8ebba311581ddbc4e0877442f46#r498157083
During AppleSilicon initial bring-up we observed a test failure where the
Internal_Convertfwrite(...)function was being called with an empty string. This was being treated as a failure during the MultiByte to utf-8 conversion. For the conversion reporting a failure in this case was incorrect. Therefore a fix was included in #40435.However, it is not clear why this only occurred for
osx-arm64and notosx-x64.Temporarily remove the fix and investigate the root cause of why this only occurs on
arm64. We would like to be sure the fix is not masking another underlying issue.See discussion https://github.com/dotnet/runtime/pull/40435/files/e186f0106acfd8ebba311581ddbc4e0877442f46#r498157083