Log what is happening during path selection #46
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Downstream, in the proprietary parts of Xamarin.Android, there is some
strange errors occurring, such as:
Task "InstallPackageAssemblies"
InstallPackageAssemblies Task
...
AndroidSdkPath: /Users/builder/android-toolchain/sdk
AndroidNdkPath: /Users/builder/android-toolchain/ndk
JavaSdkPath: /usr
Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: Error finding Android/Java SDKs [/Users/builder/jenkins/workspace/monodroid-pr/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj]
Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: System.InvalidOperationException: Could not determine Android SDK location. Please provide `androidSdkPath`. [/Users/builder/jenkins/workspace/monodroid-pr/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj]
Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: at Xamarin.Android.Tools.AndroidSdkInfo..ctor (System.Action`2[T1,T2] logger, System.String androidSdkPath, System.String androidNdkPath, System.String javaSdkPath) [0x0004b] in <5fd439f4454d4cc18bc8c35d2b4c840c>:0 [/Users/builder/jenkins/workspace/monodroid-pr/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj]
Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: at Xamarin.AndroidTools.AndroidSdk.Refresh (System.String androidSdkPath, System.String androidNdkPath, System.String javaSdkPath) [0x00000] in <9cb77bd2eef54f10a4aa7622ee40470d>:0 [/Users/builder/jenkins/workspace/monodroid-pr/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj]
We are having a lot of trouble even figuring out what is going on,
since the EXACT SAME paths worked earlier in the same build. Earlier
in the log `ResolveSdks` worked just fine!
I'm hoping this logging information will help us troubleshoot this
issue and other scenarios in the future.
jonathanpeppers
force-pushed
the
moar-logging
branch
from
da09a6f to
7bd3f81
Compare
jonpryor
pushed a commit
that referenced
this pull request
Aug 15, 2018
Downstream, in the proprietary parts of Xamarin.Android, there are some strange errors occurring, such as: Task "InstallPackageAssemblies" InstallPackageAssemblies Task ... AndroidSdkPath: /Users/builder/android-toolchain/sdk AndroidNdkPath: /Users/builder/android-toolchain/ndk JavaSdkPath: /usr Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: Error finding Android/Java SDKs […/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj] Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: System.InvalidOperationException: Could not determine Android SDK location. Please provide `androidSdkPath`. […/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj] Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: at Xamarin.Android.Tools.AndroidSdkInfo..ctor (System.Action`2[T1,T2] logger, System.String androidSdkPath, System.String androidNdkPath, System.String javaSdkPath) [0x0004b] in <5fd439f4454d4cc18bc8c35d2b4c840c>:0 […/monodroid-pr/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj] Xamarin.Android.Common.Debugging.targets(479,2): error ADB0000: at Xamarin.AndroidTools.AndroidSdk.Refresh (System.String androidSdkPath, System.String androidNdkPath, System.String javaSdkPath) [0x00000] in <9cb77bd2eef54f10a4aa7622ee40470d>:0 […/monodroid-pr/monodroid/tests/runtime/Xamarin.Android.RuntimeTests.csproj] We are having a lot of trouble even figuring out what is going on, since the EXACT SAME paths worked earlier in the same build. Earlier in the log `ResolveSdks` worked just fine! I'm hoping this logging information will help us troubleshoot this issue and other scenarios in the future.
jonathanpeppers
added a commit
to jonathanpeppers/xamarin-android
that referenced
this pull request
Aug 16, 2018
Context; dotnet/android-tools@917d3b3...9e78d6e Fixes for OpenJDK: dotnet/android-tools#43 dotnet/android-tools#45 Better logging: dotnet/android-tools#46 Fix for missing JDKs on MacOS: dotnet/android-tools#48 Tests now pass on Windows: dotnet/android-tools#47
grendello
pushed a commit
to dotnet/android
that referenced
this pull request
Aug 17, 2018
Context; dotnet/android-tools@917d3b3...9e78d6e Fixes for OpenJDK: dotnet/android-tools#43 dotnet/android-tools#45 Better logging: dotnet/android-tools#46 Fix for missing JDKs on MacOS: dotnet/android-tools#48 Tests now pass on Windows: dotnet/android-tools#47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Downstream, in the proprietary parts of Xamarin.Android, there is some
strange errors occurring, such as:
We are having a lot of trouble even figuring out what is going on,
since the EXACT SAME paths worked earlier in the same build. Earlier
in the log
ResolveSdksworked just fine!I'm hoping this logging information will help us troubleshoot this
issue and other scenarios in the future.