beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BEAM-2587) Build fails due to python sdk
Date Mon, 31 Jul 2017 19:51:02 GMT

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

Ahmet Altay edited comment on BEAM-2587 at 7/31/17 7:50 PM:
------------------------------------------------------------

[~jbonofre] I will suggest moving this out of the 2.1.0 blocker list. The reason is, it does
not affect end users (i.e. published artifacts will already have the correct generated files),
it does not affect daily development (i.e. works within a git tree), and even out of that
conditions it fails based 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 no code path
for dynamically generating these files.


was (Author: altay):
[~jbonofre] I will suggest moving this out of the 2.1.0 blocker list. The reason is, it does
not affect end users (i.e. published artifacts will already 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 based 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
>
> 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 when 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‚Äč"
> 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 prepackaged artifacts from central repositories.
> cc: [~robertwb]
> Script for reproduction:
> {code}
> #!/bin/bash
> set -e
> readonly MACHINE_ID=$(hexdump -n 1 -e '"%x"' /dev/random)
> readonly MACHINE="${USER}-beam-build-${MACHINE_ID}"
> readonly ZONE="us-central1-c"
> # provision building machine
> echo "Provisioning Build Machine (Ubuntu 16.04 LTS)"
> gcloud compute instances create "$MACHINE" \
>   --zone="$ZONE" \
>   --image-project="ubuntu-os-cloud" \
>   --image-family="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="$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)

Mime
View raw message