-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
ARROW-17252: [R] Intermittent valgrind failure (explicit StopProducing approach) #13780
Conversation
@github-actions crossbow submit test-r-linux-valgrind |
|
Revision: e0fab9b Submitted crossbow builds: ursacomputing/crossbow @ actions-cc5998cdea
|
This looks like a clean approach, but hopefully it will solve the issue as well :-) |
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
@github-actions crossbow submit test-r-linux-valgrind |
Revision: eb8194d Submitted crossbow builds: ursacomputing/crossbow @ actions-60deab85dd
|
@paleolimbot Did you favor another approach? It's not clear here :-) |
Thanks - I should have left a note. This approach never solved the issue! Reverting part of the PR that introduced the errors (#13773) and waiting for IO thread pool jobs to finish (#13779) both seem to work. I think we are going with the first option as a patch, although there is a PR in the query engine to support better cancelling of scans (#13782), after which the call to |
No description provided.