/AzurePipelines run

#160180

Automatic Validation ended with:

Executable C:\Program Files\BuildMonitor\ktsu.BuildMonitor.exe returned exit code: -532462766

Automated error analysis suggests -532462766 may mean EXCEPTION_COMPLUS (Unhandled Exception)

(Automated response - build 886.)

@stephengillie any idea how I could find out what this exception is? When installing via the local manifest I am able to successfully install and run the application with no exceptions.

When installing via the local manifest I am able to successfully install and run the application with no exceptions.

It would be better testing local manifests with Tools/SandboxTest.ps1 in Windows Sandbox. Each developers may have their own development environment, and may have different packages pre-installed. Those pre-installed packages may affect the installation process of you local manifests.

Windows Sandbox is a pure, brand new VM instance each time you launch it. The start point will always be the same on all developers. Tools/SandboxTest.ps1 performs same actions on every Sandbox instance, so you might be able to find some important key.

@stephengillie any idea how I could find out what this exception is? When installing via the local manifest I am able to successfully install and run the application with no exceptions.

This same happens with a pair of other packages in the repo (Ryujinx.Ryujinx and Ryujinx.Ryujinx.Ava) on a regular basis. I've been manually swapping labels to allow them to pass, and would be happy to do the same here.

duplicate

I spent today trying to get this working, but it seems as this is an OpenGL application using the Silk.NET library (same as Ryujinx) I had no luck getting it to actually run in the sandbox, perhaps why its failing in the automation.

I am adding the vcredist installation to my nsis installer and I'll submit another release.

Thankyou both.

/AzurePipelines run

I have remade the release including the vc redist package in the installer and updated the hash in the manifest.

As before, this installs and runs for me locally, as I have not been able to get opengl via Silk.NET to run in the sandbox yet.

• Possibly related: Support OpenGL for package validation. #12906

• Possibly related: Support OpenGL for package validation. #12906

Yeah, it seems like the same issue I was facing with validating it locally in my own sandbox, which makes sense.

/AzurePipelines run

Edit: I left it running over the weekend.

Manual Validation ended with:

Application: ktsu.BuildMonitor.exe
CoreCLR Version: 8.0.624.26715
.NET Version: 8.0.6
Description: The process was terminated due to an unhandled exception.
Exception Info: Silk.NET.GLFW.GlfwException: ApiUnavailable: WGL: The driver does not appear to support OpenGL
   at Silk.NET.GLFW.Glfw.<>c.<.cctor>b__143_0(ErrorCode errorCode, String description)
   at Silk.NET.GLFW.Glfw.CreateWindow(Int32 width, Int32 height, String title, Monitor* monitor, WindowHandle* share)
   at Silk.NET.Windowing.Glfw.GlfwWindow.CoreInitialize(WindowOptions opts)
   at Silk.NET.Windowing.Internals.WindowImplementationBase.CoreInitialize(ViewOptions opts)
   at Silk.NET.Windowing.Internals.ViewImplementationBase.Initialize()
   at Silk.NET.Windowing.WindowExtensions.Run(IView view)
   at ktsu.io.ImGuiApp.ImGuiApp.Start(String windowTitle, ImGuiAppWindowState initialWindowState, Action onStart, Action`1 onTick, Action onMenu, Action onWindowResized)
   at ktsu.BuildMonitor.BuildMonitor.Main() in D:\a\1\s\BuildMonitor\BuildMonitor.cs:line 34

Faulting application name: ktsu.BuildMonitor.exe, version: 1.0.0.0, time stamp: 0x664796e4 
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0xc9db1934 Exception code: 0xe0434352 Fault offset: 0x0000000000034f99 
Faulting process id: 0x273c 
Faulting application start time: 0x01dacbcd624488ae 
Faulting application path: C:\Program Files\BuildMonitor\ktsu.BuildMonitor.exe 
Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: afc39ea1-facc-4841-b29e-0b04e724f848 
Faulting package full name:  
Faulting package-relative application ID:   

(Automated response - build 886.)