Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid configure warning when checking ogre-1.10 #411

Merged
merged 2 commits into from
Sep 16, 2021

Conversation

j-rivero
Copy link
Contributor

馃 Bug fix

Fixes #400

Summary

After #376, the check for Ogre-1.10 is generating warnings during the configuration of the software. The PR changes the behavior to do a fake check with QUIET to avoid warnings and a real check afterwards if the unofficial ogre version is used.

Checklist

  • Signed all commits for DCO
  • All tests passed (See test coverage)

Note to maintainers: Remember to use Squash-Merge

Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
@osrf-triage osrf-triage added this to Inbox in Core development Sep 15, 2021
@github-actions github-actions bot added the 馃彴 citadel Ignition Citadel label Sep 15, 2021
@codecov
Copy link

codecov bot commented Sep 15, 2021

Codecov Report

Merging #411 (9541e41) into ign-rendering3 (08ee26c) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@               Coverage Diff               @@
##           ign-rendering3     #411   +/-   ##
===============================================
  Coverage           53.35%   53.35%           
===============================================
  Files                 131      131           
  Lines               12036    12036           
===============================================
  Hits                 6422     6422           
  Misses               5614     5614           

Continue to review full report at Codecov.

Legend - Click here to learn more
螖 = absolute <relative> (impact), 酶 = not affected, ? = missing data
Powered by Codecov. Last update 08ee26c...9541e41. Read the comment docs.

Core development automation moved this from Inbox to In review Sep 15, 2021
Copy link
Contributor

@Blast545 Blast545 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Windows CI error is a flaky known issue.

@j-rivero j-rivero merged commit 32d2aa3 into ign-rendering3 Sep 16, 2021
Core development automation moved this from In review to Done Sep 16, 2021
@j-rivero j-rivero deleted the ign_rendering3_no_warning_ogre_110 branch September 16, 2021 14:13
@iche033 iche033 mentioned this pull request Sep 20, 2021
@osrf-triage
Copy link

This pull request has been mentioned on Gazebo Community. There might be relevant details there:

https://community.gazebosim.org/t/new-ignition-releases-2022-01-10/1228/1

@j-rivero j-rivero removed this from Done in Core development May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
馃彴 citadel Ignition Citadel
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants