You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Andrew Sherman (JIRA)" <ji...@apache.org> on 2019/02/13 22:55:01 UTC
[jira] [Resolved] (IMPALA-8200) Builds fail using wrong branch of
impala-lzo
[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Sherman resolved IMPALA-8200.
------------------------------------
Resolution: Fixed
Fixed by force-pushing the correct change to upstream as well as internal gerrit.
> Builds fail using wrong branch of impala-lzo
> --------------------------------------------
>
> Key: IMPALA-8200
> URL: https://issues.apache.org/jira/browse/IMPALA-8200
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Andrew Sherman
> Assignee: Andrew Sherman
> Priority: Critical
> Labels: broken-build
> Fix For: Impala 3.2.0
>
>
> An earlier build succeeded using this commit from the branch 'master'
> {quote}
> commit dccb1be88a5e237b06ae69cd99b048a38d9f024b (HEAD -> master)
> Author: Philip Zeyliger <ph...@cloudera.com>
> AuthorDate: Tue Jan 22 14:21:42 2019 -0800
> Commit: Philip Zeyliger <ph...@cloudera.com>
> CommitDate: Fri Feb 1 11:04:06 2019 -0800
> Adapt to new interface for AddDiskIoRange (IMPALA-7980)
>
> The change for IMPALA-7980 moves out the "are we done
> adding disk io ranges" accounting from AddDiskIoRange()
> to a new UpdateRemainingScanRangeSubmissions call.
> {quote}
> but now the build is failing pointing at 'origin/master:
> {quote}
> commit 9543908ec82245878c4060dec64a1533d7adbee6 (origin/master-backup-2019-01-23, origin/master)
> Author: Alex Behm <al...@cloudera.com>
> AuthorDate: Thu Dec 4 16:53:06 2014 -0800
> Commit: Alex Behm <al...@cloudera.com>
> CommitDate: Fri Dec 5 14:28:25 2014 -0800
> Remove data compaction flag.
>
> Change-Id: Ife72c7ee630b6ecd9024a3d33b7673b56fcf1fba
> {quote}
> which is obviously something pretty old and wrong
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)