Skip to content

Conversation

@jpobst
Copy link
Contributor

@jpobst jpobst commented Aug 8, 2022

No description provided.

@jonpryor
Copy link
Contributor

I'm not sure why so many tests are failing on this PR. Could the Java.Interop bump really be responsible for these build failures? Consider AndroidAddKeepAlives(False,False,False,False):

/Users/runner/work/1/s/xamarin-android/bin/Release/dotnet/dotnet build /Users/runner/work/1/a/TestRelease/08-08_22.18.51/temp/AndroidAddKeepAlivesFalseFalseFalseFalse/UnnamedProject.csproj /t:Build,SignAndroidPackage /noconsolelogger "/flp1:LogFile=/Users/runner/work/1/a/TestRelease/08-08_22.18.51/temp/AndroidAddKeepAlivesFalseFalseFalseFalse/build.log;Encoding=UTF-8;Verbosity=diagnostic" -nodeReuse:false @"/Users/runner/work/1/a/TestRelease/08-08_22.18.51/temp/AndroidAddKeepAlivesFalseFalseFalseFalse/project.rsp"
MSBuild version 17.4.0-preview-22403-01+4e58a8330 for .NET
MSBUILD : error MSB1008: Only one project can be specified.
    Full command line: '/Users/runner/work/1/s/xamarin-android/bin/Release/dotnet/sdk/7.0.100-rc.1.22407.1/MSBuild.dll -maxcpucount -verbosity:m -restore -consoleloggerparameters:Summary --property:_DisableParallelAot=true /Users/runner/work/1/a/TestRelease/08-08_22.18.51/temp/AndroidAddKeepAlivesFalseFalseFalseFalse/UnnamedProject.csproj /t:Build,SignAndroidPackage /noconsolelogger /flp1:LogFile=/Users/runner/work/1/a/TestRelease/08-08_22.18.51/temp/AndroidAddKeepAlivesFalseFalseFalseFalse/build.log;Encoding=UTF-8;Verbosity=diagnostic -nodeReuse:false  /p:BuildingInsideVisualStudio=True  /p:BuildingOutOfProcess=true  /p:AndroidSdkDirectory="/Users/runner/Library/Android/sdk"   /p:JavaSdkDirectory="/Users/runner/hostedtoolcache/Java_Temurin-Hotspot_jdk/11.0.16-8/x64/Contents/Home/"   /bl:"/Users/runner/work/1/a/TestRelease/08-08_22.18.51/temp/AndroidAddKeepAlivesFalseFalseFalseFalse/msbuild.binlog" -distributedlogger:Microsoft.DotNet.Tools.MSBuild.MSBuildLogger,/Users/runner/work/1/s/xamarin-android/bin/Release/dotnet/sdk/7.0.100-rc.1.22407.1/dotnet.dll*Microsoft.DotNet.Tools.MSBuild.MSBuildForwardingLogger,/Users/runner/work/1/s/xamarin-android/bin/Release/dotnet/sdk/7.0.100-rc.1.22407.1/dotnet.dll'
  Switches appended by response files:
Switch:  /p:BuildingInsideVisualStudio=True

I do not understand how the Java.Interop bump could cause such an error.

@jpobst
Copy link
Contributor Author

jpobst commented Aug 11, 2022

I reran a full CI build for this and it's green:
https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=6545224&view=results

I am not sure why this PR is still showing the original CI status.

Anyways, the main point was to run ApiCompat to ensure no [Obsolete] attributes had changed. Given that it passed, I think the JI change is good to go.

@jpobst jpobst closed this Aug 11, 2022
@jpobst jpobst deleted the test-ji-1024 branch August 11, 2022 21:02
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants