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

No PR for version update of gz-physics even if the new version is correctly listed in bot-versions output and no error is listed in version error #3010

Closed
traversaro opened this issue Sep 24, 2024 · 5 comments

Comments

@traversaro
Copy link
Contributor

traversaro commented Sep 24, 2024

At conda-forge/gz-sim-feedstock#65 we are experiencing something strange with the automatic updates that we are not sure how to further debug.

The project is https://github.com/conda-forge/gz-physics-feedstock/ . The latest version on conda-forge is 7.2.0, while there was an upstream tag for 7.3.0 (https://github.com/gazebosim/gz-physics/releases/tag/gz-physics7_7.3.0, unfortunatly the tag format gz-physics7_7.3.0 probably plays a role here).

By inspecting the bot-versions output, you can find the new version is correctly detected: (see https://github.com/regro/cf-scripts/actions/runs/11007210867/job/30562973811):

2024-09-24T05:29:51.8730580Z 2024-09-24 05:29:51,872 INFO     conda_forge_tick.update_upstream_versions || itr  2236 - eta  2226s: gz-physics - 7.2.0 -> 7.3.0

Also by manually triggering an update with conda-forge/gz-physics-feedstock#39, the correct 7.3.0 version is updated (see conda-forge/gz-physics-feedstock#40).

Furthermore, there is no error for gz-physics in https://conda-forge.org/status/#version .

However, it seems that no automatic PR to update the repository to 7.3.0 is opened by the bot.

Does anyone have some pointer to debug this issue further? Thanks a lot in advance!

@traversaro
Copy link
Contributor Author

There is a similar issue for gz-sim that is at 8.3.0 and no PR is opened to update to 8.6.0 .

@traversaro
Copy link
Contributor Author

traversaro commented Sep 26, 2024

Ok, indeed some gz- recipes (that all share the same structure and unusual style of tags [gz-<project><major>-<major>.<minor>.<patch>]) the update is working as expected:

What they have in common is that in cf-graph-countyfair they have the correct version number listed:

The following package up in the stack is gz-msgs, that does not receive version update PRs, and in version_pr_info they have:

Note "new_version": "10_10.2.0" in place of the "new_version": "10.2.0" of working feedstocks. Note that also the new_version_attemps was wrong (i.e. 2_2.0.0) in the new_version_attempts also for gz-utils (see https://github.com/regro/cf-graph-countyfair/blob/54145d34bd8b22d5e69795fa9bf208aeaaa4be36/version_pr_info/a/8/b/5/a/gz-utils.json#L4), whiele for gz-math and gz-cmake it was always correct.

@traversaro
Copy link
Contributor Author

The following package up in the stack is gz-msgs, that does not receive version update PRs, and in version_pr_info they have:

* https://github.com/regro/cf-graph-countyfair/blob/54145d34bd8b22d5e69795fa9bf208aeaaa4be36/version_pr_info/c/1/b/0/a/gz-msgs.json#L4

Interestingly, the latest run of bot-bot actually updated that file: https://github.com/regro/cf-graph-countyfair/blob/09a9304ce47629fffbd4c97e028e162ab202c761/version_pr_info/c/1/b/0/a/gz-msgs.json .

@traversaro
Copy link
Contributor Author

traversaro commented Sep 27, 2024

I have no idea what changed, but now all the version update were unblocked, see for example conda-forge/gz-physics-feedstock#41 . The only one missing is gz-sim, where the "wrong" 9_9.0.0 version is shown: https://github.com/regro/cf-graph-countyfair/blob/48abfb1a9b2434bdedcf815be8dccbf123c9071d/version_pr_info/d/4/9/e/5/gz-sim.json#L4 , but this may be expected as the fix in the structure are in conda-forge/gz-sim-feedstock#64 that still needs to be merged. At this point, we can close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant