Uh oh!
There was an error while loading. Please reload this page.
ARROW-4845: [R] Compiler warnings on Windows MingW64 - #4511
ARROW-4845: [R] Compiler warnings on Windows MingW64#4511romainfrancois wants to merge 3 commits into
Conversation
romainfrancois
commented
Jun 10, 2019
This did not test on win builder because I supposed we need a new build of How do we trigger new builds for https://github.com/rwinlib/arrow ? @jeroen@javierluraschi |
Codecov Report
@@ Coverage Diff @@## master #4511 +/- ##
===========================================
- Coverage 88.11% 75.01% -13.1%
===========================================
Files 850 54 -796 Lines 105774 3114 -102660 Branches 1253 0 -1253 ===========================================
- Hits 93203 2336 -90867 + Misses 12326 778 -11548 + Partials 245 0 -245Continue to review full report at Codecov.
|
nealrichardson
commented
Jun 10, 2019
https://issues.apache.org/jira/browse/ARROW-4845 shows lots of warnings that look to be from different lines--are you sure this is the only change needed? |
romainfrancois
commented
Jun 11, 2019
I'm not sure, that's why I tried to trigger a win builder build with before it could show me compile errors. |
pitrou
left a comment
There was a problem hiding this comment.
Looks like the fix would indeed silence the warning, but some comments.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
romainfrancois
commented
Jun 11, 2019
Perhaps we can use |
8ec6d6a to
e646f82Comparejeroen
commented
Jun 12, 2019
Once libarrow 0.14 is released you can send a PR to https://github.com/r-windows/rtools-packages and https://github.com/r-windows/rtools-backports and we can upload new binaries on rwinlib. |
wesm
commented
Jun 12, 2019
At some point we need to document the source build process on Windows rather than relying on pre-packaged binaries so that we can run it in CI, otherwise we will eventually get slammed with a Windows-only problem post-release |
jeroen
commented
Jun 12, 2019
The build process is documented and automated. You can either build libarrow locally or send a PR to https://github.com/r-windows/rtools-backports and then download the binaries from appveyor, and build your R package with that. There is nothing special about rwinlib, it's just a place where we host binaries for (stable) libraries. But you could host them anywhere else. |
No description provided.