mesos-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Park <mp...@apache.org>
Subject Re: Build failed in Jenkins: Mesos-Buildbot » cmake,clang,--verbose,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2) #3128
Date Wed, 18 Jan 2017 21:09:05 GMT
This is me. Please ignore.

On Wed, Jan 18, 2017 at 1:07 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:

> See <https://builds.apache.org/job/Mesos-Buildbot/BUILDTOOL=
> cmake,COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_
> VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2)/3128/changes>
>
> Changes:
>
> [kapil] Avoided use of CHECK macros in libprocess.
>
> [kapil] Avoided use of CHECK macros.
>
> [mpark] Added `libssl-dev` to `support/mesos-tidy/Dockerfile`.
>
> [mpark] Used the `mesos/mesos-tidy` image from DockerHub.
>
> [mpark] Renamed `CONFIGURE_FLAGS` to `CMAKE_ARGS`.
>
> [mpark] Added a `support/README.md` and the `support/jenkins` directory.
>
> ------------------------------------------
> Started by upstream project "Mesos-Buildbot" build number 3128
> originally caused by:
>  Started by an SCM change
>  Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on H1 (Hadoop) in workspace <https://builds.apache.org/
> job/Mesos-Buildbot/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&
> (!ubuntu-eu2)/ws/>
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url https://git-wip-us.apache.org/
> repos/asf/mesos.git # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/mesos.git
>  > git --version # timeout=10
>  > git -c core.askpass=true fetch --tags --progress
> https://git-wip-us.apache.org/repos/asf/mesos.git
> +refs/heads/*:refs/remotes/origin/*
> Checking out Revision 745b3c7589e5252cf93f62e081b78fa420771d0c
> (origin/master)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 745b3c7589e5252cf93f62e081b78fa420771d0c
>  > git rev-list 81a804b2ccc2ee125138a57bda344f29a37c9482 # timeout=10
> [(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2)]
$ /bin/bash
> -xe /tmp/hudson9122386312405874738.sh
> + ./support/jenkins/buildbot.sh
> Requirement already satisfied (use --upgrade to upgrade): virtualenv in
> /home/jenkins/.local/lib/python2.7/site-packages
> Cleaning up...
> Total errors found: 0
> <https://builds.apache.org/job/Mesos-Buildbot/BUILDTOOL=
> cmake,COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_
> VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2)/ws/src/cli_new/bootstrap>:
> line 64: /home/jenkins/jenkins-slave/workspace/Mesos-Buildbot/
> BUILDTOOL/cmake/COMPILER/clang/CONFIGURATION/--verbose/ENVIRONMENT/GLOG_v=1:
> No such file or directory
> Already using interpreter /usr/bin/python
> There must be only one argument: DEST_DIR (you gave <
> https://builds.apache.org/job/Mesos-Buildbot/BUILDTOOL=
> cmake,COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_
> VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2)/ws/src/cli_new/.virtualenv)>
> Usage: virtualenv [OPTIONS] DEST_DIR
>
> Options:
>   --version             show program's version number and exit
>   -h, --help            show this help message and exit
>   -v, --verbose         Increase verbosity.
>   -q, --quiet           Decrease verbosity.
>   -p PYTHON_EXE, --python=PYTHON_EXE
>                         The Python interpreter to use, e.g.,
>                         --python=python2.5 will use the python2.5
> interpreter
>                         to create the new environment.  The default is the
>                         interpreter that virtualenv was installed with
>                         (/usr/bin/python)
>   --clear               Clear out the non-root install and start from
> scratch.
>   --no-site-packages    DEPRECATED. Retained only for backward
> compatibility.
>                         Not having access to global site-packages is now
> the
>                         default behavior.
>   --system-site-packages
>                         Give the virtual environment access to the global
>                         site-packages.
>   --always-copy         Always copy files rather than symlinking.
>   --unzip-setuptools    Unzip Setuptools when installing it.
>   --relocatable         Make an EXISTING virtualenv environment
> relocatable.
>                         This fixes up scripts and makes all .pth files
>                         relative.
>   --no-setuptools       Do not install setuptools in the new virtualenv.
>   --no-pip              Do not install pip in the new virtualenv.
>   --no-wheel            Do not install wheel in the new virtualenv.
>   --extra-search-dir=DIR
>                         Directory to look for setuptools/pip distributions
> in.
>                         This option can be used multiple times.
>   --download            Download preinstalled packages from PyPI.
>   --no-download, --never-download
>                         Do not download preinstalled packages from PyPI.
>   --prompt=PROMPT       Provides an alternative prompt prefix for this
>                         environment.
>   --setuptools          DEPRECATED. Retained only for backward
> compatibility.
>                         This option has no effect.
>   --distribute          DEPRECATED. Retained only for backward
> compatibility.
>                         This option has no effect.
> Checking 1098 C++ files
> Checking 8 Python files
> Virtualenv not detected... Building
> Build step 'Execute shell' marked build as failure
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message