You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Uwe Korn (Jira)" <ji...@apache.org> on 2021/06/10 12:38:00 UTC

[jira] [Resolved] (ARROW-12738) [CI] [Gandiva] Nightly build error in azure-conda-osx-clang-py38 (and py39, py*-r*)

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

Uwe Korn resolved ARROW-12738.
------------------------------
    Fix Version/s: 5.0.0
       Resolution: Fixed

Issue resolved by pull request 10499
[https://github.com/apache/arrow/pull/10499]

> [CI] [Gandiva] Nightly build error in azure-conda-osx-clang-py38 (and py39, py*-r*)
> -----------------------------------------------------------------------------------
>
>                 Key: ARROW-12738
>                 URL: https://issues.apache.org/jira/browse/ARROW-12738
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: C++ - Gandiva, Continuous Integration
>            Reporter: Mauricio 'Pachá' Vargas Sepúlveda
>            Assignee: Uwe Korn
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 5.0.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> These are all failing because of a mismatch in LLVM version, they all have some variation on the following when referencing the precompiled gandiva
> {code}
> Unknown attribute kind (70) (Producer: 'LLVM12.0.0' Reader: 'LLVM 10.0.1')
> {code}
> It _looks like_ the precompiled gandiva llvm version might be [coming from the .env file|LLVM=12]
> Examples:
> https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=6219&view=logs&j=cf796865-97b7-5cd1-be8e-6e00ce4fd8cf&t=88ee2fb8-46fd-5c68-fde3-1c8d31ba2a5f&l=1069
> https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=6250&view=logs&j=cf796865-97b7-5cd1-be8e-6e00ce4fd8cf&t=88ee2fb8-46fd-5c68-fde3-1c8d31ba2a5f&l=1046
> For some of these, the build phase will pass (even though it did not succeed and the error is then: "File ... does not exist". This is a red herring and the build problem above is the real issue.



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