Uh oh!
There was an error while loading. Please reload this page.
ARROW-17252: [R] Intermittent valgrind failure (explicit StopProducing approach) - #13780
ARROW-17252: [R] Intermittent valgrind failure (explicit StopProducing approach)#13780paleolimbot wants to merge 2 commits into
Conversation
paleolimbot
commented
Aug 2, 2022
@github-actions crossbow submit test-r-linux-valgrind |
Revision: e0fab9b Submitted crossbow builds: ursacomputing/crossbow @ actions-cc5998cdea
|
Uh oh!
There was an error while loading. Please reload this page.
pitrou
commented
Aug 3, 2022
This looks like a clean approach, but hopefully it will solve the issue as well :-) |
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
paleolimbot
commented
Aug 3, 2022
@github-actions crossbow submit test-r-linux-valgrind |
Revision: eb8194d Submitted crossbow builds: ursacomputing/crossbow @ actions-60deab85dd
|
pitrou
commented
Aug 8, 2022
@paleolimbot Did you favor another approach? It's not clear here :-) |
paleolimbot
commented
Aug 8, 2022
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.