-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🧑🌾 SEH Exceptions
in gz-rendering-win
#745
Comments
is this still an issue? |
I updated the issue with new information |
SEH Exception
in gz-rendering-winSEH Exceptions
in gz-rendering-win
The SEH exception might be a red herring. Based on the error
my guess is that the graphics card is not set up properly on that machine. The same test doesn't print that error on a passing test on a different machine (see |
Yeah, the error is probably likely that something in the scene creation process is an unchecked |
This is also happening on gz_rendering-main. I added Ionic as a label |
This is still affecting gz-rendering windows jobs with the same output Reference builds:
Failure Percentage:
|
@Crola1702 any progress on setting up ogre 2.3 on our windows machines? I believe that's a requirement for fixing these tests. |
I'm not sure. I can take a look with @j-rivero's help. Any ideas on where to start? |
Last time we talked about this, I remember the next action item was to check if our vcpkg port for ogre-next-23 actually works. If you can verify that locally, I think we can make the change in https://github.com/gazebo-tooling/release-tools/blob/f392d30813b5097229b22413f56a6733556d34f4/jenkins-scripts/lib/windows_env_vars.bat#L22 |
From: gazebosim/gz-rendering#745, ros2/rcl#1162 Signed-off-by: Crola1702 <[email protected]>
I did a quick test adding So I think there are a couple to tasks to do for getting ogre-next 2.3 working on windows:
|
Environment
Description
Steps to reproduce
Output
We have 71 test regressions in gz-rendering windows (7, 8, 9 and main)
First time we saw it: Sept 1
It stopped between Sept 28 and Oct 11
And now it came back
We think it's probably related to this issue: https://stackoverflow.com/questions/13157671/seh-exception-with-code-0xc0000005-thrown-in-the-test-body
Update (17/08/2023):
Reference build: https://build.osrfoundation.org/job/ign_rendering-ci-win/254/#showFailuresLink
Test regressions (71 last updated in 13-09-2024)
Log Output:
This issue started happening again on Aug 11 on different machines
Edit 17-10-2023:
New test regression (new test added by #908):
This is now a consistent failure in gz-rendering 7 and 8 Windows
Edit 12-08-2024:
New test regression caused by #976 5 months ago:
Edit 13-10-2024:
New test added in #1035 are failing because of this:
The text was updated successfully, but these errors were encountered: