[tests] make adb logcat appear in the build output #832
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
It is useful to have the logcat output in the Jenkins CI console logs, as the Workspace is only available until a next build starts and so logcat-*.txt dumps, we create after running tests, are available only for short time.
|
We already dump logcat in case test fails https://github.com/radekdoulik/xamarin-android/blob/255840da427ca5c643f1f0dde2f506881e98fdc2/build-tools/scripts/TestApks.targets#L77 and that should be enough |
jonpryor
pushed a commit
that referenced
this pull request
May 10, 2021
Changes: dotnet/java-interop@4d0cba6...12e670a * dotnet/java-interop@12e670a8: [generator] Support binding non-const Java interface fields (#831) * dotnet/java-interop@c925b784: [generator] Support varargs arrays in event listener methods (#832)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It is useful to have the logcat output in the Jenkins CI console logs,
as the Workspace is only available until a next build starts and so
logcat-*.txt dumps, we create after running tests, are available only
for short time.