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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bumps in garden: use ign-math7 and dependents #1264

Merged
merged 6 commits into from
Dec 30, 2021

Conversation

chapulina
Copy link
Contributor

@github-actions github-actions bot added the 🌱 garden Ignition Garden label Dec 27, 2021
@chapulina chapulina requested a review from scpeters December 27, 2021 22:45
@chapulina chapulina added the needs upstream release Blocked by a release of an upstream library label Dec 27, 2021
Signed-off-by: Louise Poubel <[email protected]>
@chapulina chapulina requested a review from iche033 as a code owner December 28, 2021 01:58
@chapulina chapulina removed the needs upstream release Blocked by a release of an upstream library label Dec 29, 2021
@scpeters scpeters changed the title Bumps in garden : ci_matching_branch/bump_garden_ign-gazebo7 Bumps in garden: use ign-math7 and dependents Dec 30, 2021
Signed-off-by: Louise Poubel <[email protected]>
@chapulina
Copy link
Contributor Author

The TriggeredPublisher test failures seem to be caused by SDFormat:

173: [ RUN      ] TriggeredPublisherTest.EmptyInputEmptyOutput
173: [Msg] Loading SDF world file[/home/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/test/worlds/triggered_publisher.sdf].
173: Error [Param.cc:768] Unknown parameter type[ignition.msgs.Boolean]
173: Exception [Param.cc:81] SDF ASSERTION                     
173: Invalid parameter
173: In function       : Param
173: Assert expression : this->dataPtr->ValueFromStringImpl( this->dataPtr->typeName, _default, this->dataPtr->defaultValue)
173: unknown file: Failure
173: Unknown C++ exception thrown in SetUp().

It may already be on main, but we can't trigger a test build because we're in the middle of the dependency bump.

@scpeters
Copy link
Member

scpeters commented Dec 30, 2021

The TriggeredPublisher test failures seem to be caused by SDFormat:

173: [ RUN      ] TriggeredPublisherTest.EmptyInputEmptyOutput
173: [Msg] Loading SDF world file[/home/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/test/worlds/triggered_publisher.sdf].
173: Error [Param.cc:768] Unknown parameter type[ignition.msgs.Boolean]
173: Exception [Param.cc:81] SDF ASSERTION                     
173: Invalid parameter
173: In function       : Param
173: Assert expression : this->dataPtr->ValueFromStringImpl( this->dataPtr->typeName, _default, this->dataPtr->defaultValue)
173: unknown file: Failure
173: Unknown C++ exception thrown in SetUp().

It may already be on main, but we can't trigger a test build because we're in the middle of the dependency bump.

Observations:

I suggest a prerelease of libsdformat12

@scpeters
Copy link
Member

I suggest a prerelease of libsdformat12

and I think we should disable the triggered publisher tests so we can finish this merge

@scpeters
Copy link
Member

I suspect gazebosim/sdformat#689 for the TriggeredPublisher test failures

@chapulina
Copy link
Contributor Author

I think we should disable the triggered publisher tests so we can finish this merge

Since ign-gazebo already has other failing / flaky tests, I think it's ok to leave those failing so we remember to address them quickly.

I suggest a prerelease of libsdformat12

I can reproduce the failure locally on a Fortress workspace, so we don't need the pre-release to confirm the issue. Let me take a stab at it, hopefully it's an easy fix.

@scpeters
Copy link
Member

I suspect ignitionrobotics/sdformat#689 for the TriggeredPublisher test failures

I've commented https://github.com/ignitionrobotics/sdformat/pull/689/files#r776821783 on the line I believe to be causing the problem

@scpeters
Copy link
Member

I think we should disable the triggered publisher tests so we can finish this merge

Since ign-gazebo already has other failing / flaky tests, I think it's ok to leave those failing so we remember to address them quickly.

the triggered publisher failures were the only problems with the following build:

I think it's worth disabling the builds before merging this rather than merging them if we know they will always be failing

I suggest a prerelease of libsdformat12

I can reproduce the failure locally on a Fortress workspace, so we don't need the pre-release to confirm the issue. Let me take a stab at it, hopefully it's an easy fix.

if not a prerelease, perhaps we could trigger some nightly builds of libsdformat12? I think it will be easier to confirm the fix if we have debs that we can use from CI builds. An alternative would be building an entire workspace from source from a specified .repos file like the ROS2 CI

@chapulina
Copy link
Contributor Author

I think it's worth disabling the builds before merging this rather than merging them if we know they will always be failing

Ok, disabling those tests, right? We'll just need another PR to re-enable them soon.

An alternative would be building an entire workspace from source from a specified .repos file like the ROS2 CI

Yeah we can do that with GitHub actions. I'm hoping to open a PR upstream soon with a band-aid that we can test against ign-gazebo. Or are you saying we should test the current sdf12 branch to confirm the issue?

@chapulina
Copy link
Contributor Author

@scpeters , what do you think of not blocking this on the triggered publisher issue? I'd like to finish bumping ign-launch and ign-garden today. If you feel strongly about disabling the tests on this PR I can do that now, just let me know. The issue is coming from ign-gazebo6, so disabling them here only solves part of the issue.

An alternative would be building an entire workspace from source from a specified .repos file like the ROS2 CI
Yeah we can do that with GitHub actions.

@scpeters
Copy link
Member

@scpeters , what do you think of not blocking this on the triggered publisher issue? I'd like to finish bumping ign-launch and ign-garden today. If you feel strongly about disabling the tests on this PR I can do that now, just let me know. The issue is coming from ign-gazebo6, so disabling them here only solves part of the issue.

An alternative would be building an entire workspace from source from a specified .repos file like the ROS2 CI
Yeah we can do that with GitHub actions.

yes we should disable the triggered publisher test

…thub.com/ignitionrobotics/ign-gazebo into ci_matching_branch/bump_garden_ign-gazebo7

Signed-off-by: Louise Poubel <[email protected]>
@chapulina
Copy link
Contributor Author

yes we should disable the triggered publisher test

Ok, disabled in faf7533

@scpeters
Copy link
Member

yes we should disable the triggered publisher test

Ok, disabled in faf7533

to remind us to reenable the tests: #1267

@codecov
Copy link

codecov bot commented Dec 30, 2021

Codecov Report

Merging #1264 (662508d) into main (0e720f0) will decrease coverage by 0.23%.
The diff coverage is 40.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1264      +/-   ##
==========================================
- Coverage   61.95%   61.71%   -0.24%     
==========================================
  Files         276      274       -2     
  Lines       22996    22740     -256     
==========================================
- Hits        14248    14035     -213     
+ Misses       8748     8705      -43     
Impacted Files Coverage Δ
include/ignition/gazebo/gui/GuiEvents.hh 0.00% <ø> (ø)
...lization_capabilities/VisualizationCapabilities.cc 3.70% <0.00%> (ø)
src/rendering/SceneManager.cc 25.99% <0.00%> (ø)
src/systems/track_controller/TrackController.cc 70.94% <0.00%> (ø)
...ems/collada_world_exporter/ColladaWorldExporter.cc 94.81% <100.00%> (ø)
src/systems/multicopter_control/Common.cc 71.42% <100.00%> (ø)
.../systems/triggered_publisher/TriggeredPublisher.cc
.../systems/triggered_publisher/TriggeredPublisher.hh
src/systems/buoyancy/Buoyancy.cc 83.09% <0.00%> (+0.07%) ⬆️
src/systems/physics/Physics.cc 71.65% <0.00%> (+0.10%) ⬆️

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 0e720f0...662508d. Read the comment docs.

@chapulina chapulina merged commit a95a584 into main Dec 30, 2021
@chapulina chapulina deleted the ci_matching_branch/bump_garden_ign-gazebo7 branch December 30, 2021 20:51
@j-rivero j-rivero mentioned this pull request Sep 16, 2022
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌱 garden Ignition Garden
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants