-
Notifications
You must be signed in to change notification settings - Fork 212
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
Disable rendering tests on Mac when building debug. #257
Conversation
Display tests currently fail due to #246. In order to make it easier to triage CI failures, disable these tests in that configuration pending resolution of the failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, should be temporary until we can resolve the debug loading. Thanks.
@nuclearsandwich have your run CI to show that these are disabled correctly (And still work when not in Debug)? |
rviz_rendering_tests/CMakeLists.txt
Outdated
PUBLIC src/rviz_rendering_tests) | ||
target_link_libraries(test_rviz_rendering_tests | ||
ament_index_cpp::ament_index_cpp) | ||
if (APPLE AND NOT CMAKE_BUILD_TYPE STREQUAL "Debug") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the tests now disabled for Linux ? (aka if NOT APPLE but DISPLAYPRESENT)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah... Should probably be NOT APPLE OR NOT CMAKE_BUILD_TYPE STREQUAL "Debug"
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep or NOT (APPLE AND CMAKE_BUILD_TYPE STREQUAL "Debug")
. I find the latter easier to read but it's very subjective
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yours sounds better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch here. If we opt to keep the nested conditional approach I'll change it to @mikaelarguedas's condition.
rviz_rendering_tests/CMakeLists.txt
Outdated
@@ -70,7 +70,7 @@ if(BUILD_TESTING) | |||
rviz_ogre_vendor::OgreMain | |||
rviz_rendering::rviz_rendering | |||
resource_retriever::resource_retriever | |||
) | |||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can smudge out this whitespace change before merging.
@@ -59,7 +59,7 @@ if(BUILD_TESTING) | |||
set(DISPLAYPRESENT FALSE) | |||
endif() | |||
|
|||
if(APPLE OR DISPLAYPRESENT OR EnableDisplayTests STREQUAL "True") | |||
if((APPLE AND NOT CMAKE_BUILD_TYPE STREQUAL "Debug") OR DISPLAYPRESENT OR EnableDisplayTests STREQUAL "True") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is now a very long line.
I think that's better to add a temporary extra conditional with a TODO as we expect it to disappear as soon as the tests are fixed in Debug. I assume that on the other hand the original APPLE OR DISPLAYPRESENT OR EnableDisplayTests STREQUAL "True"
will stay as is for the foreseeable future, is that correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have strong feelings either way. The extra conditional optimized for preserving existing logic, this optimizes for minimal diff churn.
The tests still ran and failed with the same error. I'm not entirely sure why. Does CMAKE_BUILD_TYPE need to be evaluated, i.e. |
I don't think so, at least we use it not evaluated in other places and it seems to be doing the right thing. Maybe another part of the condition evaluates to TRUE ?
|
It certainly wouldn't be wrong to do |
This construct is actually part of |
It appears that the |
@nuclearsandwich since the only failure was the linter failure and it was just whitespace change, I'm ok if you want to merge this now without new CI. |
With @mikaelarguedas's assistance I verified the fix for the linter error locally and a build (below) is running to verify it in CI. For the builds above, Display tests ran on Mac with build type none but did not run on the Debug build or Windows or Linux builds. So this change should be good once the final CI check completes. Hopefully it won't stick around too long. |
This reverts commit e8181a4.
Display tests currently fail due to #246.
In order to make it easier to triage CI failures, disable these tests in that configuration pending resolution of the failure.
Temporarily resolves #245.