-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Bump to potentially fix https://github.com/conda-forge/gz-sim-feedstock/pull/9, fix autotick bot #7
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.01.22.14.39.28
There is an error related to the use of dart 6.13, we probably need to update gz-physics to get gazebosim/gz-physics#465 (unfortunatly there are no automatic updates due to conda-forge/libignition-gazebo-feedstock#24 and similar issues). |
Ah unfortunatly gazebo-physics 6.3.0 still needs to updated (see gazebosim/gz-physics#474), so we can just backport the dartsim 6.13 fixes. |
The patch does not apply cleanly, at this point we can fix to dartsim 6.12 until gazebo-physics 6.3.0 is released. |
Hmm .. some test failures on windows now :(
|
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
Just to be sure I will update to last version the dependencies: |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
Integration tests on Windows are failing with:
Let's see if it works with one thread. |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/gz-physics-feedstock/actions/runs/5200683715. |
Current problem is:
both on VS2019 and VS2022 . |
However, at least on VS2022 all other test link and pass fine, so I guess there is something strange in that test. In VS2019 the test So, to proceed:
|
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/gz-physics-feedstock/actions/runs/5203709050. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.06.07.14.53.06
Indeed, this happens also in the CI:
|
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.06.07.14.53.06
In a non-deterministic way, vs2022 builds also fail with:
Furthermore, the test failure also occure in vs2022 with the CI. Note that the failure is:
that apparently seems related to the simulation going unstable, see gazebosim/gz-sim#15 (comment) and related issues. For this reason, I think it is worth to just disable the test and go back to vs2019 to move forward (it is possible to use anyhow bullet instead of dart if necessary). |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.06.08.00.22.40
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
Two changes:
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)