-
Notifications
You must be signed in to change notification settings - Fork 231
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
Avoid unnecessary rinfo calls after creating gateways #909
Conversation
Hopefully this fixes pytest-dev#907, as seems this is the only change in pytest-dev#901 which is somehow related.
I'll try to run sqlalchemy test on this branch later |
@CaselIT oh that would be great, thanks! |
Change-Id: I4bc459895692931db30b9e5b98d10d94f1cdc5ac
This run should use the patch you added https://github.com/sqlalchemy/sqlalchemy/actions/runs/5018530060 It will take a while since there are other 3 pipeline in the queue before it |
Change-Id: I4bc459895692931db30b9e5b98d10d94f1cdc5ac
Change-Id: I4bc459895692931db30b9e5b98d10d94f1cdc5ac
Edited the link above since fumbled the tox config |
Thanks @CaselIT. It passed! Can you trigger a new run to make sure it was not a fluke? |
Done https://github.com/sqlalchemy/sqlalchemy/actions/runs/5018530060 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, i made a rough proposal for a more informative changelog
i think its important people get a basic gist of the underlying issue
Co-authored-by: Ronny Pfannschmidt <[email protected]>
Re-run also passed. trying a 3rd time just to be sure (3.3.0 failed each time in 4 runs it did, so we should be good) |
also 3rd re-run seems fine |
Hopefully this fixes #907, as seems this is the only change in #901 which is somehow related.