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

leaktest: remove forced GC #92930

Merged
merged 1 commit into from
Dec 12, 2022
Merged

Conversation

andreimatei
Copy link
Contributor

The leaktest was forcing a GC, which is bizarre. Folklore has it that it was done for #61120, which in the meantime has been solved in other ways. This patch removes the unusual GC and hopes for the best.

Release note: None
Epic: None

@andreimatei andreimatei requested review from tbg and lunevalex December 2, 2022 17:42
@cockroach-teamcity
Copy link
Member

This change is Reviewable

The leaktest was forcing a GC, which is bizarre. Folklore has it that it
was done for cockroachdb#61120, which in the meantime has been solved in other
ways. This patch removes the unusual GC and hopes for the best.

Release note: None
Epic: None
Copy link
Contributor Author

@andreimatei andreimatei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors r+

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @lunevalex)

@craig
Copy link
Contributor

craig bot commented Dec 12, 2022

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Dec 12, 2022

Build succeeded:

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

Successfully merging this pull request may close these issues.

3 participants