gazebosim / gazebosim/gz-rendering
WIP: Conda Windows migration: failing tests in current vcpkg and new conda envs
- Dominant language
- C++
- Stars
- 81
- Forks
- 90
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Description
The issues tries to compile the current status of failing tests in existing vcpkg and the new conda environments, specially related to the installations of ogre, ogre-next in both. Special focus on reporting problems in current version that are not catched by the testing suite due to different bugs: https://github.com/gazebosim/gz-rendering/pull/1089 and https://github.com/gazebosim/gz-rendering/pull/1090
## Fortress (gz-rendering6)
:arrow_right: Reference build https://build.osrfoundation.org/view/gz-fortress/job/gz_rendering-ign-rendering6-win/100
### Current status
Although the test suite is green, there are different problems affecting the run:
* ogre: `1.12.9`
* :heavy_check_mark: CMake / Configuring time: detected
* :warning: Test suite: not run (bug in hardcoding the engines in test_config.h)
* ogre-next: `2.1.9999~20210319~3aa42f`
* :heavy_check_mark: CMake / Configuring time: detected
* :warning: Test suite: run but critical problems seems not to be catched by test suite
* optix:
* :heavy_check_mark: CMake / Configuring time: not detected (fine, we don't install the support)
* :warning: Test suite: run (this is a bug in hardcoding the engines in test_config.h)
#### Real failures in current
This is a run with the right engine support implemented https://github.com/gazebosim/gz-rendering/pull/1089 and a heavy failure if the engine fails to be loaded https://github.com/gazebosim/gz-rendering/pull/1090 .
:arrow_right: Reference build: https://build.osrfoundation.org/job/gz_rendering-pr-win/266
* ogre: `1.12.9`
* :heavy_check_mark: CMake / Configuring time: detected
* :fire: Tests suite: run, [26 failing tests](https://build.osrfoundation.org/job/gz_rendering-pr-win/266/testReport/)
* ogre-next: `2.1.9999~20210319~3aa42f`
* :heavy_check_mark: CMake / Configuring time: detected
* :fire: Test suite: run, [65 failing tests](https://build.osrfoundation.org/job/gz_rendering-pr-win/266/testReport/)
* optix:
* :heavy_check_mark: CMake / Configuring time: not detected (fine, we don't install the support)
* :heavy_check_mark: Test suite: not run (fine)
### Conda migration
:arrow_right: Reference build: https://build.osrfoundation.org/view/conda/job/_test_gz_rendering-pr-cwin/24
* ogre: `1.10.12.1`
* :heavy_check_mark: CMake / Configuring time: detected
* :fire: Tests suite: run, [8 failing tests](https://build.osrfoundation.org/job/gz_rendering-pr-win/266/testReport/) [ignore the LoadOgre2Test]
* ogre-next: `2.2.6`
* :fire: CMake / Configuring time: failed
* Test suite: disabled
* optix:
* :heavy_check_mark: CMake / Configuring time: not detected (fine, we don't install the support)
* :heavy_check_mark: Test suite: not run (fine)
#### Failing tests inspection
| test-name | output | diagnose |
|--------------|------------|------------|
| UNIT_BoundingBoxCamera_TEST | Engine 'ogre' doesn't support bounding box cameras | ✅ unsupported. To be disabled|
| UNIT_RenderEngine_TEST | ItemIdentityException: Resource with the name Default/TransRed already exists | ⚠️ might be easy to fix |
| UNIT_Visual_TEST | ItemIdentityException: Resource with the name Default/TransRed already exists. | ⚠️ might be easy to fix|
| INTEGRATION_gpu_rays | Expected: (14.9) < (range), actual: 14.9 vs 0 | 🔥 Probably needs deeper debug |
| INTEGRATION_camera | gz-rendering\test\media\materials\programs\simple_color_vs.glsl already exists | ⚠️ might be easy to fix|
| INTEGRATION_render_pass | _Distortion already exists. in ResourceManage | ⚠️ might be easy to fix|
| PERFORMANCE_scene_factory | | ✅ memory check test. To be disabled |
Contributor guide
Research direction
Start by reviewing test_config.h and the listed failing tests, then reproduce the Fortress and Conda Windows reference builds. Compare the failures for ogre and ogre-next, including resource-duplication, GPU-ray, camera, and render-pass tests; done means the engine support is correctly detected and the relevant test failures are resolved or intentionally disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, computer-graphics, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100