`make list-nunit-tests` fail

[atsushieno]

https://github.com/xamarin/xamarin-android/blob/master/Documentation/building/unix-instructions.md#listing-nunit-tests says make list-nunit-tests should list the nunit tests. But it does not work (on Linux):

Build FAILED.

"/sources/xamarin-android/build-tools/scripts/RunTests.targets" (ListNUnitTests target) (1) ->
(ListNUnitTests target) -> 
  Xamarin.Android.Build.Tests.AndroidRegExTests.RegExTests("res\\layout\\main.axml : error : No resource identifier found for attribute \"id2\" in package \"android\" (TaskId:22)",True,"res\\layout\\main.axml","","error","No resource identifier found for attribute \"id2\" in package \"android\" (TaskId:22)") [/sources/xamarin-android/build-tools/scripts/RunTests.targets]
  Xamarin.Android.Build.Tests.AndroidRegExTests.RegExTests("Resources/values/theme.xml(2): error APT0000: Error retrieving parent for item: No resource found that matches the given name '@android:style/Theme.AppCompat'.",True,"Resources/values/theme.xml","2","error APT0000","Error retrieving parent for item: No resource found that matches the given name '@android:style/Theme.AppCompat'.") [/sources/xamarin-android/build-tools/scripts/RunTests.targets]
  /sources/xamarin-android/build-tools/scripts/RunTests.targets(30,5): error MSB3073: The command "mono packages/NUnit.ConsoleRunner.3.7.0/tools/nunit3-console.exe  --explore /sources/xamarin-android/build-tools/scripts/../../bin/TestDebug/Xamarin.Android.Build.Tests.dll" exited with code -1.

    0 Warning(s)
3 Error(s)

Full log: https://gist.github.com/atsushieno/94df35d45ce39c945032d3906d5f92ee

xamarin-android master 5c8ba5b

[dotnet-policy-service]

We suspect this issue is stale and no longer relevant. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

[dotnet-policy-service]

This issue will now be closed since it had been marked "possibly-stale" but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.