Mailing-List: contact commits-help@beam.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.apache.org
Date: Mon, 31 Jul 2017 18:30:00 +0000 (UTC)
From: "Ahmet Altay (JIRA)" <jira@apache.org>
To: commits@beam.apache.org
Message-ID: <JIRA.13086354.1499800251000.54271.1501525800083@Atlassian.JIRA>
In-Reply-To: <JIRA.13086354.1499800251000@Atlassian.JIRA>
References: <JIRA.13086354.1499800251000@Atlassian.JIRA> <JIRA.13086354.1499800251445@jira-lw-us.apache.org>
Subject: [jira] [Commented] (BEAM-2587) Build fails due to python sdk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 31 Jul 2017 18:30:05 -0000


    [ https://issues.apache.org/jira/browse/BEAM-2587?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16107=
735#comment-16107735 ]=20

Ahmet Altay commented on BEAM-2587:
-----------------------------------

[~jbonofre] I will suggest moving this out of the 2.1.0 blocker list. The r=
eason is, it does not affect end users (i.e. published artifacts will alrea=
dy have the correct generated files), it does not affect daily development =
(i.e. works within a git tree), and event out of that conditions it fails b=
ased on pip/os versions that is not clearly defined yet. It will take some =
more time to reproduce and fix it and does not need to block the release.

However, this is a regression in the sense that at the time of 2.0.0 there =
was code path for dynamically generating these files.

> Build fails due to python sdk
> -----------------------------
>
>                 Key: BEAM-2587
>                 URL: https://issues.apache.org/jira/browse/BEAM-2587
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py
>    Affects Versions: 2.1.0
>            Reporter: Ahmet Altay
>             Fix For: 2.1.0
>
>
> Build fails with the following errors when {{mvn clean package}} is used =
on a clean Ubuntu 16.04 LTS machine with pip 8.x. The issue is resolved whe=
n pip is upgraded to pip 9.x
> "RuntimeError: Not in apache git tree; unable to find proto definitions."
> "DistutilsOptionError: can't combine user with prefix, exec_prefix/home, =
or install_(plat)base=E2=80=8B"
> We need to understand the issue and maybe add a note about requiring pip =
9.x for development. Note that this does not affect end users using prepack=
aged artifacts from central repositories.
> cc: [~robertwb]
> Script for reproduction:
> {code}
> #!/bin/bash
> set -e
> readonly MACHINE_ID=3D$(hexdump -n 1 -e '"%x"' /dev/random)
> readonly MACHINE=3D"${USER}-beam-build-${MACHINE_ID}"
> readonly ZONE=3D"us-central1-c"
> # provision building machine
> echo "Provisioning Build Machine (Ubuntu 16.04 LTS)"
> gcloud compute instances create "$MACHINE" \
>   --zone=3D"$ZONE" \
>   --image-project=3D"ubuntu-os-cloud" \
>   --image-family=3D"ubuntu-1604-lts"
> # wait for ssh to be ready
> echo "Waiting for machine to finish booting"
> sleep 30
> # ssh into the machine
> # 1. install dependencies as specified by beam readme
> # 2. download beam source from github
> # 3. build with maven
> echo "Downloading and building Apache Beam (release-2.1.0)"
> gcloud compute ssh "$MACHINE" --zone=3D"$ZONE" << EOF
> sudo apt-get --assume-yes update
> sudo apt-get --assume-yes install \
>     openjdk-8-jdk \
>     maven \
>     python-setuptools \
>     python-pip
> wget https://github.com/apache/beam/archive/release-2.1.0.tar.gz
> tar -xzf release-2.1.0.tar.gz
> cd beam-release-2.1.0
> mvn clean package
> EOF
> {code}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)