You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a couple of other PRs that don't have any actions to run that didn't have the issue.
In all of these cases, the linux side succeeded, the mac side errored out, and the windows side was cancelled after the mac side failed, since it was still running.
As far as I can tell, this looks like it might be the first "real" issue:
========================================
PackVSMacTemplates
========================================
Determining projects to restore...
Restored /Users/runner/work/MonoGame/MonoGame/Templates/MonoGame.Templates.VSMacExtension/MonoGame.Templates.VSMacExtension.csproj (in 3.27 sec).
MSBuild version 17.5.0+6f08c67f3 for .NET
Determining projects to restore...
Restored /Users/runner/work/MonoGame/MonoGame/Templates/MonoGame.Templates.VSMacExtension/MonoGame.Templates.VSMacExtension.csproj (in 402 ms).
/Users/runner/.nuget/packages/microsoft.visualstudiomac.sdk/17.0.0/build/Microsoft.VisualStudioMac.Sdk.targets(55,5): warning : The TargetFrameworkVersion 'v6.0' does not the target instance. Overriding with 'v7.0'. [/Users/runner/work/MonoGame/MonoGame/Templates/MonoGame.Templates.VSMacExtension/MonoGame.Templates.VSMacExtension.csproj]
This part seems problematic:
TargetFrameworkVersion 'v6.0' does not the target instance. Overriding with 'v7.0'
After that, there's a long collection of things like this:
warning MSB3243: No way to resolve conflict between "Microsoft.Win32.SystemEvents, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" and "Microsoft.Win32.SystemEvents, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51". Choosing "Microsoft.Win32.SystemEvents, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" arbitrarily.
After a giant pile of those, we start to get errors like this:
error CS0518: Predefined type 'System.Object' is not defined or imported
What version of MonoGame does the bug occur on:
MonoGame 3.8.1, but this doesn't seem like an MG source code issue, but some sort of build action configuration issue.
What operating system are you using:
MacOS? I used Windows during development, but the builds are dying on the macos side.
What MonoGame platform are you using:
Not relevant.
The text was updated successfully, but these errors were encountered:
Were I to take a guess, I'd guess this is happening on the build action side, within GitHub. That maybe there's some configuration that is set up to run the latest version when it maybe needs to be locked to .NET 6 or something. But that's a wild guess.
I'm not sure what next step to take to try to diagnose this. If somebody could point me in a good direction, I'd keep working on it. But it is starting to feel like it is outside of my control. I think I'd maybe need to set up my own self-hosted runners in my fork and run the same actions through those runners from my own fork or something?
All five of the last PRs that run checks (four of which are mine) fail on the MacOS side:
CalculateNormals
that picked the wrong normal for each point. #8007[ContentReadersConsumer]
attribute to enable preserving content readers while trimming #8014There are a couple of other PRs that don't have any actions to run that didn't have the issue.
In all of these cases, the linux side succeeded, the mac side errored out, and the windows side was cancelled after the mac side failed, since it was still running.
All of them show the same stuff in the output. Here's an example: https://github.com/MonoGame/MonoGame/actions/runs/4706087874/jobs/8347094062?pr=8015
As far as I can tell, this looks like it might be the first "real" issue:
This part seems problematic:
After that, there's a long collection of things like this:
After a giant pile of those, we start to get errors like this:
What version of MonoGame does the bug occur on:
What operating system are you using:
What MonoGame platform are you using:
The text was updated successfully, but these errors were encountered: