-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
py-nio: Port health display fails to update from "failed" to "successful" #361
Comments
Now I see it. This is related to #343. |
I don't think so. There really were no successful builds of py-nio on anything other than Ventura x86_64, because it is a stub port and thus the built archive can be used on any OS version, so the other builders all skipped it. So this is more like #135 with the added complication of |
@jmroot, I see. It looks like rev bump is the only way for a developer to fix displayed port health after a failed dependency is fixed. Agreed? |
No, a rev bump will not help anything here. |
Port py-nio was recently rebuilt by manual triggers, after dependency py27-nio was fixed. However, the new py-nio builds are not syncing to the ports website. Build status continues to show only old broken builds, and "failed install-dependencies" for 10 out of 11 builders that should now be "successful". Therefore the port health is seriously misstated.
On previous advice, I have avoided trying to force by rev-bump. Is there a bug in the port sync machinery, or am I missing something?
https://ports.macports.org/port/py-nio/builds/
https://ports.macports.org/port/py27-nio/builds/
[Updated description to be more specific to port health display.]
The text was updated successfully, but these errors were encountered: