-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-38824: [Go] Enable GC checks #38826
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
|
|
|
I wonder if this is making Go CI builds slower than they were. I see a ton of |
Answer: CI builds seem roughly the same duration as before. |
3b9143b to
79e0988
Compare
|
@github-actions crossbow submit -g go |
|
Revision: 29bf1db Submitted crossbow builds: ursacomputing/crossbow @ actions-ed99c57b77
|
zeroshade
left a comment
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.
LGTM thanks!
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 1cd22df. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
### What changes are included in this PR? Our codebase has many uses of `unsafe.Pointer`. It may be a good idea to add debug checks for these uses in CI builds, especially where data crosses C boundaries. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38824 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
What changes are included in this PR?
Our codebase has many uses of
unsafe.Pointer. It may be a good idea to add debug checks for these uses in CI builds, especially where data crosses C boundaries.Are these changes tested?
Yes.
Are there any user-facing changes?
No.