You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Neal Richardson (Jira)" <ji...@apache.org> on 2021/08/04 19:37:00 UTC

[jira] [Assigned] (ARROW-13507) [R] LTO job on CRAN fails

     [ https://issues.apache.org/jira/browse/ARROW-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neal Richardson reassigned ARROW-13507:
---------------------------------------

    Assignee: Jonathan Keane

> [R] LTO job on CRAN fails
> -------------------------
>
>                 Key: ARROW-13507
>                 URL: https://issues.apache.org/jira/browse/ARROW-13507
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: R
>            Reporter: Neal Richardson
>            Assignee: Jonathan Keane
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 6.0.0, 5.0.1
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> ARROW-13199 added -fno-lto flags to the build (see also ARROW-12853). This likely is the cause of the LTO failure on CRAN: https://www.stats.ox.ac.uk/pub/bdr/LTO/arrow.out so we probably need to back it out.
> We don't have a CI job that tests with R built with --enable-lto, and AFAICT there is no docker image out there that has one. [I will try to get one added to wch/r-debug|https://github.com/wch/r-debug/pull/22] so that we don't have to build R from source to test this. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)