thisisnic commented on PR #47985: URL: https://github.com/apache/arrow/pull/47985#issuecomment-3497376983
> Did you manage to get a CI job running with this failing in it? I too am surprised we hadn't caught it. Yeah, in my most recent commit I removed a LOT of crap I added on the journey to this smaller PR, but I ended up on this path as I added a condition in `configure.win` (and `configure`) to error out if the running of `codegen.R` failed and it instantly failed. I thought it was my changes or other recent ones which had caused this, before taking the loooooong path to figure out that it was segfaulting the whole time but an external process called from `configure.win` segfaulting doesn't cause the script to fail unless you explicitly tell it to (surprising!) and it had been doing it the whole time. Biggest clue was looking back to the oldest log I could find which was before all this base pipe stuff and it was segfaulting there but not erroring on CI! And in one of my commit above, I revert all of my changes except for the "error if the `configure.R` step fails" one, and it still fails on CI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
