-
Notifications
You must be signed in to change notification settings - Fork 710
Revert "Merge pull request #7995 from robx/cleanup-processes" #8295
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
Conversation
Why are we reverting? Is there time pressure? The correct way is to fix it. Please explain exactly what this reversal fixes, on which platform etc. Even after reading #8208 I don't understand it. |
The bug and the platform is the title of the linked issue: The time pressure is mentioned in the last comment of the issue, and also my preference for fixing it.
|
-1 for reverting, unless @robx agrees that fixing will take a long time. The way is forward. Releases should be good quality. |
Agree, i asked @robx (and include it as reviewer) for that reason. I would not merge this without his approval. |
For the record, the PR being reverted is #7995. If I understand correctly, this reverts a merge commit, which causes the whole PR to be left out. Let me restart CI to verify if the failure is transient. |
8bc627f
to
d42a630
Compare
This reverts commit ddf3ba2, reversing
changes made to 001e3cc.
pr #7995
I've checked manually a version of branch 3.8 with this reverted and it does not show the problem described here: #8208
This is the fast way to remove the issue for the incoming 3.8 version but ideally the pr should be kept and fixed as the refactor was good.
//cc @robx