Build failed in Jenkins: Kbin_uX32__webrtc__ubuntu_xenial_i386__binary #2

2 views
Skip to first unread message

ROS Buildfarm

unread,
Apr 29, 2020, 5:54:54 PM4/29/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/2/display/redirect>

Changes:


------------------------------------------
[...truncated 330.90 KB...]
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=webrtc

//Path to a program.
CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries.
CMAKE_STATIC_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_STRIP:FILEPATH=/usr/bin/strip

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make. This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//Value Computed by CMake
webrtc_BINARY_DIR:STATIC=/tmp/binarydeb/ros-kinetic-webrtc-59.0.4/obj-i686-linux-gnu

//Value Computed by CMake
webrtc_SOURCE_DIR:STATIC=/tmp/binarydeb/ros-kinetic-webrtc-59.0.4


########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=/tmp/binarydeb/ros-kinetic-webrtc-59.0.4/obj-i686-linux-gnu
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=5
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
//ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=/usr/bin/cmake
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=/tmp/binarydeb/ros-kinetic-webrtc-59.0.4
//Install .so files without execute permission.
CMAKE_INSTALL_SO_NO_EXE:INTERNAL=1
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_NM
CMAKE_NM-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJCOPY
CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJDUMP
CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=/usr/share/cmake-3.5
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/bin/uname
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1

cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 10439 killed;
[ssh-agent] Stopped.
[description-setter] Could not determine description.

ROS Buildfarm

unread,
Apr 29, 2020, 7:12:15 PM4/29/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/3/display/redirect>

Changes:


------------------------------------------
[...truncated 243.88 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 26923 killed;

ROS Buildfarm

unread,
Apr 30, 2020, 7:20:49 PM4/30/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/4/display/redirect>

Changes:


------------------------------------------
[...truncated 329.65 KB...]

ROS Buildfarm

unread,
May 1, 2020, 7:08:15 PM5/1/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/5/display/redirect>

Changes:


------------------------------------------
[...truncated 329.19 KB...]
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMakdh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
echo Agent pid 30611 killed;

ROS Buildfarm

unread,
May 2, 2020, 7:04:35 PM5/2/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/6/display/redirect>

Changes:


------------------------------------------
[...truncated 243.80 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
# END SUBSECTION
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 22512 killed;

ROS Buildfarm

unread,
May 3, 2020, 7:22:42 PM5/3/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/7/display/redirect>

Changes:


------------------------------------------
[...truncated 329.64 KB...]
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMake
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1929 killed;

ROS Buildfarm

unread,
May 4, 2020, 7:22:23 PM5/4/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/8/display/redirect>

Changes:


------------------------------------------
[...truncated 326.47 KB...]
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 3093 killed;

ROS Buildfarm

unread,
May 5, 2020, 7:23:04 PM5/5/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/9/display/redirect>

Changes:


------------------------------------------
[...truncated 243.83 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 8903 killed;

ROS Buildfarm

unread,
May 6, 2020, 7:08:08 PM5/6/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/10/display/redirect>

Changes:


------------------------------------------
[...truncated 329.19 KB...]
echo Agent pid 28087 killed;

ROS Buildfarm

unread,
May 7, 2020, 7:09:41 PM5/7/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/11/display/redirect>

Changes:


------------------------------------------
[...truncated 326.59 KB...]
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2195 killed;

ROS Buildfarm

unread,
May 8, 2020, 7:04:39 PM5/8/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/12/display/redirect>

Changes:


------------------------------------------
[...truncated 244.03 KB...]
//Path to a program.
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 27431 killed;

ROS Buildfarm

unread,
May 9, 2020, 7:20:37 PM5/9/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/13/display/redirect>

Changes:


------------------------------------------
[...truncated 243.73 KB...]
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 18676 killed;

ROS Buildfarm

unread,
May 10, 2020, 7:13:22 PM5/10/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/14/display/redirect>

Changes:


------------------------------------------
[...truncated 243.55 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 30873 killed;

ROS Buildfarm

unread,
May 11, 2020, 7:12:11 PM5/11/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/15/display/redirect>

Changes:


------------------------------------------
[...truncated 243.50 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 30701 killed;

ROS Buildfarm

unread,
May 12, 2020, 7:07:41 PM5/12/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/16/display/redirect>

Changes:


------------------------------------------
[...truncated 329.19 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 13000 killed;

ROS Buildfarm

unread,
May 13, 2020, 7:08:01 PM5/13/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/17/display/redirect>

Changes:


------------------------------------------
[...truncated 330.27 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 31747 killed;

ROS Buildfarm

unread,
May 14, 2020, 7:48:34 PM5/14/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/18/display/redirect>

Changes:


------------------------------------------
[...truncated 330.19 KB...]
--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 6392 killed;

ROS Buildfarm

unread,
May 15, 2020, 7:08:59 PM5/15/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/19/display/redirect>

Changes:


------------------------------------------
[...truncated 327.51 KB...]

//Path to a program.
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 19971 killed;

ROS Buildfarm

unread,
May 16, 2020, 7:06:42 PM5/16/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/20/display/redirect>

Changes:


------------------------------------------
[...truncated 243.84 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 29352 killed;

ROS Buildfarm

unread,
May 17, 2020, 7:19:23 PM5/17/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/21/display/redirect>

Changes:


------------------------------------------
[...truncated 243.45 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1035 killed;

ROS Buildfarm

unread,
May 18, 2020, 7:08:18 PM5/18/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/22/display/redirect>

Changes:


------------------------------------------
[...truncated 329.74 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 31025 killed;

ROS Buildfarm

unread,
May 19, 2020, 7:18:10 PM5/19/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/23/display/redirect>

Changes:


------------------------------------------
[...truncated 327.52 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
# END SUBSECTION
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 20098 killed;

ROS Buildfarm

unread,
May 20, 2020, 7:06:46 PM5/20/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/24/display/redirect>

Changes:


------------------------------------------
[...truncated 325.69 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
# END SUBSECTION
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 16332 killed;

ROS Buildfarm

unread,
May 21, 2020, 7:05:33 PM5/21/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/25/display/redirect>

Changes:


------------------------------------------
[...truncated 244.09 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 5096 killed;

ROS Buildfarm

unread,
May 22, 2020, 7:04:50 PM5/22/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/26/display/redirect>

Changes:


------------------------------------------
[...truncated 244.17 KB...]
echo Agent pid 29145 killed;

ROS Buildfarm

unread,
May 23, 2020, 7:08:31 PM5/23/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/27/display/redirect>

Changes:


------------------------------------------
[...truncated 330.08 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2970 killed;

ROS Buildfarm

unread,
May 24, 2020, 7:10:05 PM5/24/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/28/display/redirect>

Changes:


------------------------------------------
[...truncated 327.20 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 12858 killed;

ROS Buildfarm

unread,
May 25, 2020, 7:07:44 PM5/25/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/29/display/redirect>

Changes:


------------------------------------------
[...truncated 330.13 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
# END SUBSECTION
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2312 killed;

ROS Buildfarm

unread,
May 26, 2020, 7:05:04 PM5/26/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/30/display/redirect>

Changes:


------------------------------------------
[...truncated 244.33 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 4474 killed;

ROS Buildfarm

unread,
May 27, 2020, 7:07:43 PM5/27/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/31/display/redirect>

Changes:


------------------------------------------
[...truncated 330.43 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 25380 killed;

ROS Buildfarm

unread,
May 28, 2020, 7:04:34 PM5/28/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/32/display/redirect>

Changes:


------------------------------------------
[...truncated 244.07 KB...]
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 6946 killed;

ROS Buildfarm

unread,
May 29, 2020, 9:42:33 PM5/29/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/33/display/redirect>

Changes:


------------------------------------------
[...truncated 325.94 KB...]
echo Agent pid 19563 killed;

ROS Buildfarm

unread,
May 30, 2020, 7:16:32 PM5/30/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/34/display/redirect>

Changes:


------------------------------------------
[...truncated 327.35 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 3546 killed;

ROS Buildfarm

unread,
May 31, 2020, 7:20:59 PM5/31/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/35/display/redirect>

Changes:


------------------------------------------
[...truncated 243.81 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 20199 killed;

ROS Buildfarm

unread,
Jun 1, 2020, 7:04:48 PM6/1/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/36/display/redirect>

Changes:


------------------------------------------
[...truncated 244.21 KB...]
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMakdh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
echo Agent pid 5965 killed;

ROS Buildfarm

unread,
Jun 2, 2020, 7:08:24 PM6/2/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/37/display/redirect>

Changes:


------------------------------------------
[...truncated 327.58 KB...]
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMake
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2518 killed;

ROS Buildfarm

unread,
Jun 3, 2020, 7:08:32 PM6/3/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/38/display/redirect>
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------
# END SUBSECTION

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 3672 killed;

ROS Buildfarm

unread,
Jun 4, 2020, 7:06:44 PM6/4/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/39/display/redirect>
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
# END SUBSECTION
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 17143 killed;

ROS Buildfarm

unread,
Jun 5, 2020, 7:19:50 PM6/5/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/40/display/redirect>

Changes:


------------------------------------------
[...truncated 243.80 KB...]
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 21631 killed;

ROS Buildfarm

unread,
Jun 6, 2020, 7:19:55 PM6/6/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/41/display/redirect>
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 12631 killed;

ROS Buildfarm

unread,
Jun 7, 2020, 7:19:53 PM6/7/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/42/display/redirect>

Changes:


------------------------------------------
[...truncated 244.03 KB...]
//Path to a program.
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
# END SUBSECTION
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 3166 killed;

ROS Buildfarm

unread,
Jun 8, 2020, 7:05:06 PM6/8/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/43/display/redirect>

Changes:


------------------------------------------
[...truncated 243.99 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 5140 killed;

ROS Buildfarm

unread,
Jun 9, 2020, 7:18:57 PM6/9/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/44/display/redirect>

Changes:


------------------------------------------
[...truncated 243.98 KB...]
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 19546 killed;

ROS Buildfarm

unread,
Jun 10, 2020, 7:08:15 PM6/10/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/45/display/redirect>

Changes:


------------------------------------------
[...truncated 330.83 KB...]
echo Agent pid 26087 killed;

ROS Buildfarm

unread,
Jun 11, 2020, 7:20:30 PM6/11/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/46/display/redirect>

Changes:


------------------------------------------
[...truncated 225.79 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 12491 killed;

ROS Buildfarm

unread,
Jun 12, 2020, 7:04:30 PM6/12/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/47/display/redirect>

Changes:


------------------------------------------
[...truncated 226.09 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 17828 killed;

ROS Buildfarm

unread,
Jun 13, 2020, 7:26:33 PM6/13/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/48/display/redirect>

Changes:


------------------------------------------
[...truncated 332.90 KB...]
# END SUBSECTION
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1934 killed;

ROS Buildfarm

unread,
Jun 14, 2020, 7:18:54 PM6/14/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/49/display/redirect>

Changes:


------------------------------------------
[...truncated 225.90 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2984 killed;

ROS Buildfarm

unread,
Jun 15, 2020, 7:04:28 PM6/15/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/50/display/redirect>

Changes:


------------------------------------------
[...truncated 226.34 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 10960 killed;

ROS Buildfarm

unread,
Jun 16, 2020, 7:52:36 PM6/16/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/51/display/redirect>

Changes:


------------------------------------------
[...truncated 226.51 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 28192 killed;

ROS Buildfarm

unread,
Jun 17, 2020, 8:36:58 PM6/17/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/52/display/redirect>

Changes:


------------------------------------------
[...truncated 226.05 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 714 killed;

ROS Buildfarm

unread,
Jun 18, 2020, 7:37:30 PM6/18/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/53/display/redirect>

Changes:


------------------------------------------
[...truncated 93.06 KB...]
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 17706 killed;

ROS Buildfarm

unread,
Jun 19, 2020, 7:57:02 PM6/19/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/54/display/redirect>

Changes:


------------------------------------------
[...truncated 226.17 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 15603 killed;

ROS Buildfarm

unread,
Jun 20, 2020, 8:50:42 PM6/20/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/55/display/redirect>

Changes:


------------------------------------------
[...truncated 225.79 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 7081 killed;

ROS Buildfarm

unread,
Jun 21, 2020, 7:35:15 PM6/21/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/56/display/redirect>

Changes:


------------------------------------------
[...truncated 92.75 KB...]
echo Agent pid 9087 killed;

ROS Buildfarm

unread,
Jun 22, 2020, 8:05:01 PM6/22/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/57/display/redirect>

Changes:


------------------------------------------
[...truncated 332.72 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 24186 killed;

ROS Buildfarm

unread,
Jun 22, 2020, 8:21:48 PM6/22/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/58/display/redirect>

Changes:


------------------------------------------
[...truncated 332.97 KB...]
echo Agent pid 6625 killed;

ROS Buildfarm

unread,
Jun 23, 2020, 7:04:46 PM6/23/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/59/display/redirect>

Changes:


------------------------------------------
[...truncated 226.26 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 27157 killed;

ROS Buildfarm

unread,
Jun 24, 2020, 7:08:41 PM6/24/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/60/display/redirect>
--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 8578 killed;

ROS Buildfarm

unread,
Jun 25, 2020, 7:07:26 PM6/25/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/61/display/redirect>

Changes:


------------------------------------------
[...truncated 328.38 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 9501 killed;

ROS Buildfarm

unread,
Jun 26, 2020, 7:28:18 PM6/26/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/62/display/redirect>

Changes:


------------------------------------------
[...truncated 332.91 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2090 killed;

ROS Buildfarm

unread,
Jun 27, 2020, 7:29:12 PM6/27/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/63/display/redirect>

Changes:


------------------------------------------
[...truncated 328.20 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 26605 killed;

ROS Buildfarm

unread,
Jun 28, 2020, 7:32:47 PM6/28/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/64/display/redirect>

Changes:


------------------------------------------
[...truncated 332.97 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 24674 killed;

ROS Buildfarm

unread,
Jun 29, 2020, 7:25:13 PM6/29/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/65/display/redirect>

Changes:


------------------------------------------
[...truncated 225.79 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 25410 killed;

ROS Buildfarm

unread,
Jun 30, 2020, 7:18:48 PM6/30/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/66/display/redirect>

Changes:


------------------------------------------
[...truncated 226.61 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 12661 killed;

ROS Buildfarm

unread,
Jul 1, 2020, 7:27:37 PM7/1/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/67/display/redirect>

Changes:


------------------------------------------
[...truncated 333.05 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2389 killed;

ROS Buildfarm

unread,
Jul 2, 2020, 7:08:05 PM7/2/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/68/display/redirect>

Changes:


------------------------------------------
[...truncated 330.68 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 23642 killed;

ROS Buildfarm

unread,
Jul 3, 2020, 7:08:25 PM7/3/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/69/display/redirect>

Changes:


------------------------------------------
[...truncated 333.12 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 17007 killed;

ROS Buildfarm

unread,
Jul 4, 2020, 7:23:34 PM7/4/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/70/display/redirect>

Changes:


------------------------------------------
[...truncated 225.85 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2773 killed;

ROS Buildfarm

unread,
Jul 5, 2020, 7:08:35 PM7/5/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/71/display/redirect>

Changes:


------------------------------------------
[...truncated 333.05 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 29938 killed;

ROS Buildfarm

unread,
Jul 6, 2020, 7:22:26 PM7/6/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/72/display/redirect>

Changes:


------------------------------------------
[...truncated 226.60 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 21309 killed;

ROS Buildfarm

unread,
Jul 7, 2020, 7:08:42 PM7/7/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/73/display/redirect>

Changes:


------------------------------------------
[...truncated 333.18 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 13550 killed;

ROS Buildfarm

unread,
Jul 8, 2020, 7:01:49 PM7/8/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/74/display/redirect>

Changes:


------------------------------------------
[...truncated 7.75 KB...]
+ git -C ros_buildfarm --no-pager log -n 1
commit f559beb7d33fc3a4e3317a42a4a6ab7f5c009f55
Author: Scott K Logan <log...@cottsay.net>
Date: Wed Jul 1 17:11:06 2020 -0700

Changes for compatibility with the latest Pulp release (#818)

See https://pulp-rpm.readthedocs.io/en/3.4/changes.html#id79
+ rm -fr ros_buildfarm/.git
+ rm -fr ros_buildfarm/doc
+ echo # END SECTION
# END SECTION
[Kbin_uX32__webrtc__ubuntu_xenial_i386__binary] $ /bin/sh -xe /tmp/jenkins205691959578520384.sh
+ echo # BEGIN SECTION: Write PGP repository keys
# BEGIN SECTION: Write PGP repository keys
+ mkdir -p /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/keys
+ rm -fr /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/keys/*
+ echo -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1

mQINBFzvJpYBEADY8l1YvO7iYW5gUESyzsTGnMvVUmlV3XarBaJz9bGRmgPXh7jc
VFrQhE0L/HV7LOfoLI9H2GWYyHBqN5ERBlcA8XxG3ZvX7t9nAZPQT2Xxe3GT3tro
u5oCR+SyHN9xPnUwDuqUSvJ2eqMYb9B/Hph3OmtjG30jSNq9kOF5bBTk1hOTGPH4
K/AY0jzT6OpHfXU6ytlFsI47ZKsnTUhipGsKucQ1CXlyirndZ3V3k70YaooZ55rG
aIoAWlx2H0J7sAHmqS29N9jV9mo135d+d+TdLBXI0PXtiHzE9IPaX+ctdSUrPnp+
TwR99lxglpIG6hLuvOMAaxiqFBB/Jf3XJ8OBakfS6nHrWH2WqQxRbiITl0irkQoz
pwNEF2Bv0+Jvs1UFEdVGz5a8xexQHst/RmKrtHLct3iOCvBNqoAQRbvWvBhPjO/p
V5cYeUljZ5wpHyFkaEViClaVWqa6PIsyLqmyjsruPCWlURLsQoQxABcL8bwxX7UT
hM6CtH6tGlYZ85RIzRifIm2oudzV5l+8oRgFr9yVcwyOFT6JCioqkwldW52P1pk/
/SnuexC6LYqqDuHUs5NnokzzpfS6QaWfTY5P5tz4KHJfsjDIktly3mKVfY0fSPVV
okdGpcUzvz2hq1fqjxB6MlB/1vtk0bImfcsoxBmF7H+4E9ZN1sX/tSb0KQARAQAB
tCZPcGVuIFJvYm90aWNzIDxpbmZvQG9zcmZvdW5kYXRpb24ub3JnPokCVAQTAQoA
PhYhBMHPbjHmut6IaLFytPQu1vurF8ZUBQJc7yaWAhsDBQkDwmcABQsJCAcCBhUK
CQgLAgQWAgMBAh4BAheAAAoJEPQu1vurF8ZUkhIP/RbZY1ErvCEUy8iLJm9aSpLQ
nDZl5xILOxyZlzpg+Ml5bb0EkQDr92foCgcvLeANKARNCaGLyNIWkuyDovPV0xZJ
rEy0kgBrDNb3++NmdI/+GA92pkedMXXioQvqdsxUagXAIB/sNGByJEhs37F05AnF
vZbjUhceq3xTlvAMcrBWrgB4NwBivZY6IgLvl/CRQpVYwANShIQdbvHvZSxRonWh
NXr6v/Wcf8rsp7g2VqJ2N2AcWT84aa9BLQ3Oe/SgrNx4QEhA1y7rc3oaqPVu5ZXO
K+4O14JrpbEZ3Xs9YEjrcOuEDEpYktA8qqUDTdFyZrxb9S6BquUKrA6jZgT913kj
J4e7YAZobC4rH0w4u0PrqDgYOkXA9Mo7L601/7ZaDJob80UcK+Z12ZSw73IgBix6
DiJVfXuWkk5PM2zsFn6UOQXUNlZlDAOj5NC01V0fJ8P0v6GO9YOSSQx0j5UtkUbR
fp/4W7uCPFvwAatWEHJhlM3sQNiMNStJFegr56xQu1a/cbJH7GdbseMhG/f0BaKQ
qXCI3ffB5y5AOLc9Hw7PYiTFQsuY1ePRhE+J9mejgWRZxkjAH/FlAubqXkDgterC
h+sLkzGf+my2IbsMCuc+3aeNMJ5Ej/vlXefCH/MpPWAHCqpQhe2DET/jRSaM53US
AHNx8kw4MPUkxExgI7Sd
=4Ofr
-----END PGP PUBLIC KEY BLOCK-----

+ echo # END SECTION
# END SECTION
[Kbin_uX32__webrtc__ubuntu_xenial_i386__binary] $ /bin/sh -xe /tmp/jenkins1519074162017687452.sh
+ rm -fr /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/docker_generating_docker
+ mkdir -p /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/docker_generating_docker
+ sleep 1
+ python3 -u /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/ros_buildfarm/scripts/subprocess_reaper.py 16203 --cid-file /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/docker_generating_docker/docker.cid
+ echo # BEGIN SECTION: Generate Dockerfile - binarydeb task
# BEGIN SECTION: Generate Dockerfile - binarydeb task
+ export TZ=UTC+00
+ export PYTHONPATH=/home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/ros_buildfarm:
+ python3 -u /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/ros_buildfarm/scripts/release/run_binarydeb_job.py --rosdistro-index-url https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml kinetic webrtc ubuntu xenial i386 --distribution-repository-urls http://repositories.ros.org/ubuntu/building --distribution-repository-key-files /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/keys/0.key --target-repository http://repositories.ros.org/ubuntu/building --binarypkg-dir /tmp/binarydeb --dockerfile-dir /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/docker_generating_docker --env-vars --append-timestamp
Using the following distribution repositories:
http://repositories.ros.org/ubuntu/building (/home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/keys/0.key)
Generating Dockerfile '/home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/docker_generating_docker/Dockerfile':
# generated from release/deb/binarypkg_create_task.Dockerfile.em

FROM osrf/ubuntu_i386:xenial

VOLUME ["/var/cache/apt/archives"]

ENV DEBIAN_FRONTEND noninteractive


RUN for i in 1 2 3; do apt-get update && apt-get install -q -y locales && apt-get clean && break || if [ $i -lt 3 ]; then sleep 5; else false; fi; done
RUN echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen
RUN locale-gen en_US.UTF-8
ENV LANG en_US.UTF-8
ENV TZ UTC+00


RUN useradd -u 1001 -l -m buildfarm

RUN mkdir /tmp/keys
RUN echo "-----BEGIN PGP PUBLIC KEY BLOCK-----\nVersion: GnuPG v1\n\nmQINBFzvJpYBEADY8l1YvO7iYW5gUESyzsTGnMvVUmlV3XarBaJz9bGRmgPXh7jc\nVFrQhE0L/HV7LOfoLI9H2GWYyHBqN5ERBlcA8XxG3ZvX7t9nAZPQT2Xxe3GT3tro\nu5oCR+SyHN9xPnUwDuqUSvJ2eqMYb9B/Hph3OmtjG30jSNq9kOF5bBTk1hOTGPH4\nK/AY0jzT6OpHfXU6ytlFsI47ZKsnTUhipGsKucQ1CXlyirndZ3V3k70YaooZ55rG\naIoAWlx2H0J7sAHmqS29N9jV9mo135d+d+TdLBXI0PXtiHzE9IPaX+ctdSUrPnp+\nTwR99lxglpIG6hLuvOMAaxiqFBB/Jf3XJ8OBakfS6nHrWH2WqQxRbiITl0irkQoz\npwNEF2Bv0+Jvs1UFEdVGz5a8xexQHst/RmKrtHLct3iOCvBNqoAQRbvWvBhPjO/p\nV5cYeUljZ5wpHyFkaEViClaVWqa6PIsyLqmyjsruPCWlURLsQoQxABcL8bwxX7UT\nhM6CtH6tGlYZ85RIzRifIm2oudzV5l+8oRgFr9yVcwyOFT6JCioqkwldW52P1pk/\n/SnuexC6LYqqDuHUs5NnokzzpfS6QaWfTY5P5tz4KHJfsjDIktly3mKVfY0fSPVV\nokdGpcUzvz2hq1fqjxB6MlB/1vtk0bImfcsoxBmF7H+4E9ZN1sX/tSb0KQARAQAB\ntCZPcGVuIFJvYm90aWNzIDxpbmZvQG9zcmZvdW5kYXRpb24ub3JnPokCVAQTAQoA\nPhYhBMHPbjHmut6IaLFytPQu1vurF8ZUBQJc7yaWAhsDBQkDwmcABQsJCAcCBhUK\nCQgLAgQWAgMBAh4BAheAAAoJEPQu1vurF8ZUkhIP/RbZY1ErvCEUy8iLJm9aSpLQ\nnDZl5xILOxyZlzpg+Ml5bb0EkQDr92foCgcvLeANKARNCaGLyNIWkuyDovPV0xZJ\nrEy0kgBrDNb3++NmdI/+GA92pkedMXXioQvqdsxUagXAIB/sNGByJEhs37F05AnF\nvZbjUhceq3xTlvAMcrBWrgB4NwBivZY6IgLvl/CRQpVYwANShIQdbvHvZSxRonWh\nNXr6v/Wcf8rsp7g2VqJ2N2AcWT84aa9BLQ3Oe/SgrNx4QEhA1y7rc3oaqPVu5ZXO\nK+4O14JrpbEZ3Xs9YEjrcOuEDEpYktA8qqUDTdFyZrxb9S6BquUKrA6jZgT913kj\nJ4e7YAZobC4rH0w4u0PrqDgYOkXA9Mo7L601/7ZaDJob80UcK+Z12ZSw73IgBix6\nDiJVfXuWkk5PM2zsFn6UOQXUNlZlDAOj5NC01V0fJ8P0v6GO9YOSSQx0j5UtkUbR\nfp/4W7uCPFvwAatWEHJhlM3sQNiMNStJFegr56xQu1a/cbJH7GdbseMhG/f0BaKQ\nqXCI3ffB5y5AOLc9Hw7PYiTFQsuY1ePRhE+J9mejgWRZxkjAH/FlAubqXkDgterC\nh+sLkzGf+my2IbsMCuc+3aeNMJ5Ej/vlXefCH/MpPWAHCqpQhe2DET/jRSaM53US\nAHNx8kw4MPUkxExgI7Sd\n=4Ofr\n-----END PGP PUBLIC KEY BLOCK-----" > /tmp/keys/0.key && apt-key add /tmp/keys/0.key
RUN echo deb http://repositories.ros.org/ubuntu/building xenial main | tee -a /etc/apt/sources.list.d/buildfarm.list
RUN echo deb-src http://repositories.ros.org/ubuntu/building xenial main | tee -a /etc/apt/sources.list.d/buildfarm.list

RUN grep -q -F -e "deb http://old-releases.ubuntu.com" /etc/apt/sources.list && ((grep -q -E -x -e "deb http://old-releases\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb http://old-releases.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://old-releases\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb-src http://old-releases.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://old-releases\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb http://old-releases.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://old-releases\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb-src http://old-releases.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://old-releases\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb http://old-releases.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://old-releases\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb-src http://old-releases.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list)) || ((grep -q -E -x -e "deb http://archive\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb http://archive.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://archive\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb-src http://archive.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://archive\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb http://archive.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://archive\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb-src http://archive.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://archive\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb http://archive.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://archive\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb-src http://archive.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list))

RUN mkdir /tmp/wrapper_scripts
RUN echo "#!/usr/bin/env python3\n\n# Copyright 2014-2016 Open Source Robotics Foundation, Inc.\n#\n# Licensed under the Apache License, Version 2.0 (the \"License\");\n# you may not use this file except in compliance with the License.\n# You may obtain a copy of the License at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by applicable law or agreed to in writing, software\n# distributed under the License is distributed on an \"AS IS\" BASIS,\n# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n# See the License for the specific language governing permissions and\n# limitations under the License.\n\nimport subprocess\nimport sys\nfrom time import sleep\n\n\ndef main(argv=sys.argv[1:]):\n max_tries = 10\n known_error_strings = [\n 'Failed to fetch',\n 'Failed to stat',\n 'Hash Sum mismatch',\n 'Unable to locate package',\n 'is not what the server reported',\n ]\n\n command = argv[0]\n if command in ['update', 'source']:\n rc, _, _ = call_apt_repeatedly(\n argv, known_error_strings, max_tries)\n return rc\n elif command == 'update-install-clean':\n return call_apt_update_install_clean(\n argv[1:], known_error_strings, max_tries)\n else:\n assert \"Command '%s' not implemented\" % command\n\n\ndef call_apt_update_install_clean(\n install_argv, known_error_strings, max_tries):\n tries = 0\n command = 'update'\n while tries < max_tries:\n if command == 'update':\n rc, _, tries = call_apt_repeatedly(\n [command], known_error_strings, max_tries - tries,\n offset=tries)\n if rc != 0:\n # abort if update was unsuccessful even after retries\n break\n # move on to the install command if update was successful\n command = 'install'\n\n if command == 'install':\n # any call is considered a try\n tries += 1\n known_error_strings_redo_update = [\n 'Size mismatch',\n 'maybe run apt update',\n 'The following packages cannot be authenticated!',\n 'Unable to locate package',\n 'has no installation candidate',\n 'corrupted package archive',\n ]\n rc, known_error_conditions = \\\\\n call_apt(\n [command] + install_argv,\n known_error_strings + known_error_strings_redo_update)\n if not known_error_conditions:\n if rc != 0:\n # abort if install was unsuccessful\n break\n # move on to the clean command if install was successful\n command = 'clean'\n continue\n\n # known errors are always interpreted as a non-zero rc\n if rc == 0:\n rc = 1\n # check if update needs to be rerun\n if (\n set(known_error_conditions) &\n set(known_error_strings_redo_update)\n ):\n command = 'update'\n print(\"'apt install' failed and likely requires \" +\n \"'apt update' to run again\")\n # retry with update command\n continue\n\n print('')\n print('Invocation failed due to the following known error '\n 'conditions: ' + ', '.join(known_error_conditions))\n print('')\n if tries < max_tries:\n sleep_time = 5\n print(\"Reinvoke 'apt install' after sleeping %s seconds\" %\n sleep_time)\n sleep(sleep_time)\n # retry install command\n\n if command == 'clean':\n rc, _ = call_apt([command], [])\n break\n\n return rc\n\n\ndef call_apt_repeatedly(argv, known_error_strings, max_tries, offset=0):\n command = argv[0]\n for i in range(1, max_tries + 1):\n if i > 1:\n sleep_time = 5 + 2 * (i + offset)\n print(\"Reinvoke 'apt %s' (%d/%d) after sleeping %s seconds\" %\n (command, i + offset, max_tries + offset, sleep_time))\n sleep(sleep_time)\n rc, known_error_conditions = call_apt(argv, known_error_strings)\n if not known_error_conditions:\n # break the loop and return the reported rc\n break\n # known errors are always interpreted as a non-zero rc\n if rc == 0:\n rc = 1\n print('')\n print('Invocation failed due to the following known error conditions: '\n ', '.join(known_error_conditions))\n print('')\n # retry in case of failure with known error condition\n return rc, known_error_conditions, i + offset\n\n\ndef call_apt(argv, known_error_strings):\n known_error_conditions = []\n\n # some of the used options are not supported in older distros\n # e.g. Ubuntu Wily, Debian Jessie\n cmd = ['apt-get'] + argv\n print(\"Invoking '%s'\" % ' '.join(cmd))\n proc = subprocess.Popen(\n cmd, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)\n lines = []\n while True:\n line = proc.stdout.readline()\n if not line:\n break\n line = line.decode()\n lines.append(line)\n sys.stdout.write(line)\n for known_error_string in known_error_strings:\n if known_error_string in line:\n if known_error_string not in known_error_conditions:\n known_error_conditions.append(known_error_string)\n proc.wait()\n rc = proc.returncode\n if rc and not known_error_conditions:\n print('Invocation failed without any known error condition, '\n 'printing all lines to debug known error detection:')\n for index, line in enumerate(lines):\n print(' ', index + 1, \"'%s'\" % line.rstrip('\\\\n\\\\r'))\n print('None of the following known errors were detected:')\n for index, known_error_string in enumerate(known_error_strings):\n print(' ', index + 1, \"'%s'\" % known_error_string)\n return rc, known_error_conditions\n\n\nif __name__ == '__main__':\n sys.exit(main())" > /tmp/wrapper_scripts/apt.py
RUN echo "#!/usr/bin/env python3\n\n# Copyright 2016 Open Source Robotics Foundation, Inc.\n#\n# Licensed under the Apache License, Version 2.0 (the \"License\");\n# you may not use this file except in compliance with the License.\n# You may obtain a copy of the License at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by applicable law or agreed to in writing, software\n# distributed under the License is distributed on an \"AS IS\" BASIS,\n# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n# See the License for the specific language governing permissions and\n# limitations under the License.\n\nimport subprocess\nimport sys\nfrom time import sleep\n\n\ndef main(argv=sys.argv[1:]):\n max_tries = 10\n known_error_strings = [\n 'Connection timed out',\n ]\n\n command = argv[0]\n if command == 'clone':\n rc, _, _ = call_git_repeatedly(\n argv, known_error_strings, max_tries)\n return rc\n else:\n assert \"Command '%s' not implemented\" % command\n\n\ndef call_git_repeatedly(argv, known_error_strings, max_tries):\n command = argv[0]\n for i in range(1, max_tries + 1):\n if i > 1:\n sleep_time = 5 + 2 * i\n print(\"Reinvoke 'git %s' (%d/%d) after sleeping %s seconds\" %\n (command, i, max_tries, sleep_time))\n sleep(sleep_time)\n rc, known_error_conditions = call_git(argv, known_error_strings)\n if rc == 0 or not known_error_conditions:\n break\n print('')\n print('Invocation failed due to the following known error conditions: '\n ', '.join(known_error_conditions))\n print('')\n # retry in case of failure with known error condition\n return rc, known_error_conditions, i\n\n\ndef call_git(argv, known_error_strings):\n known_error_conditions = []\n\n cmd = ['git'] + argv\n print(\"Invoking '%s'\" % ' '.join(cmd))\n proc = subprocess.Popen(\n cmd, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)\n while True:\n line = proc.stdout.readline()\n if not line:\n break\n line = line.decode()\n sys.stdout.write(line)\n for known_error_string in known_error_strings:\n if known_error_string in line:\n if known_error_string not in known_error_conditions:\n known_error_conditions.append(known_error_string)\n proc.wait()\n rc = proc.returncode\n return rc, known_error_conditions\n\n\nif __name__ == '__main__':\n sys.exit(main())" > /tmp/wrapper_scripts/git.py

# automatic invalidation once every day
RUN echo "2020-07-08 (+0000)"

RUN for i in 1 2 3; do apt-get update && apt-get install -q -y python3 && apt-get clean && break || if [ $i -lt 3 ]; then sleep 5; else false; fi; done

RUN python3 -u /tmp/wrapper_scripts/apt.py update-install-clean -q -y devscripts dpkg-dev python3-apt python3-catkin-pkg-modules python3-empy python3-rosdistro-modules python3-yaml

# always invalidate to actually have the latest apt repo state
RUN echo "2020-07-08 23:01:37 +0000"
RUN python3 -u /tmp/wrapper_scripts/apt.py update

USER buildfarm
ENTRYPOINT ["sh", "-c"]
CMD ["PYTHONPATH=/tmp/ros_buildfarm:$PYTHONPATH python3 -u /tmp/ros_buildfarm/scripts/release/get_sourcedeb.py --rosdistro-index-url https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml kinetic webrtc --sourcepkg-dir /tmp/binarydeb && PYTHONPATH=/tmp/ros_buildfarm:$PYTHONPATH python3 -u /tmp/ros_buildfarm/scripts/release/append_build_timestamp.py kinetic webrtc --sourcepkg-dir /tmp/binarydeb && PYTHONPATH=/tmp/ros_buildfarm:$PYTHONPATH python3 -u /tmp/ros_buildfarm/scripts/release/create_binarydeb_task_generator.py --rosdistro-index-url https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml kinetic webrtc ubuntu xenial i386 --distribution-repository-urls http://repositories.ros.org/ubuntu/building --distribution-repository-key-files /tmp/keys/0.key --binarypkg-dir /tmp/binarydeb --env-vars --dockerfile-dir /tmp/docker_build_binarydeb"]
+ echo # END SECTION
# END SECTION
+ echo # BEGIN SECTION: Build Dockerfile - binarydeb task
# BEGIN SECTION: Build Dockerfile - binarydeb task
+ cd /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/docker_generating_docker
+ python3 -u /home/jenkins-agent/workspace/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/ros_buildfarm/scripts/misc/docker_pull_baseimage.py
Get base image name from Dockerfile 'Dockerfile': osrf/ubuntu_i386:xenial
Check docker base image for updates: docker pull osrf/ubuntu_i386:xenial
xenial: Pulling from osrf/ubuntu_i386
Digest: sha256:6db8007727c38ddab377e16ae1dcbc3106861b33428d57bca79280ea282593d5
Status: Image is up to date for osrf/ubuntu_i386:xenial
docker.io/osrf/ubuntu_i386:xenial
+ docker build --force-rm -t binarydeb_task_generation.kinetic_ubuntu_xenial_i386_webrtc .
Sending build context to Docker daemon 18.94kB
Step 1/25 : FROM osrf/ubuntu_i386:xenial
---> 1f78e9620cb4
Step 2/25 : VOLUME ["/var/cache/apt/archives"]
---> Using cache
---> 5fe7c5c20b6c
Step 3/25 : ENV DEBIAN_FRONTEND noninteractive
---> Using cache
---> b0f4d2d562a6
Step 4/25 : RUN for i in 1 2 3; do apt-get update && apt-get install -q -y locales && apt-get clean && break || if [ $i -lt 3 ]; then sleep 5; else false; fi; done
---> Using cache
---> c5afc944f9d6
Step 5/25 : RUN echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen
---> Using cache
---> d756aa5ae871
Step 6/25 : RUN locale-gen en_US.UTF-8
---> Using cache
---> 25c739eee57a
Step 7/25 : ENV LANG en_US.UTF-8
---> Using cache
---> bba45c4948ea
Step 8/25 : ENV TZ UTC+00
---> Using cache
---> 6543d78f1441
Step 9/25 : RUN useradd -u 1001 -l -m buildfarm
---> Using cache
---> f4aa888b694e
Step 10/25 : RUN mkdir /tmp/keys
---> Running in c581503328ac
Removing intermediate container c581503328ac
---> 04dc4f274379
Step 11/25 : RUN echo "-----BEGIN PGP PUBLIC KEY BLOCK-----\nVersion: GnuPG v1\n\nmQINBFzvJpYBEADY8l1YvO7iYW5gUESyzsTGnMvVUmlV3XarBaJz9bGRmgPXh7jc\nVFrQhE0L/HV7LOfoLI9H2GWYyHBqN5ERBlcA8XxG3ZvX7t9nAZPQT2Xxe3GT3tro\nu5oCR+SyHN9xPnUwDuqUSvJ2eqMYb9B/Hph3OmtjG30jSNq9kOF5bBTk1hOTGPH4\nK/AY0jzT6OpHfXU6ytlFsI47ZKsnTUhipGsKucQ1CXlyirndZ3V3k70YaooZ55rG\naIoAWlx2H0J7sAHmqS29N9jV9mo135d+d+TdLBXI0PXtiHzE9IPaX+ctdSUrPnp+\nTwR99lxglpIG6hLuvOMAaxiqFBB/Jf3XJ8OBakfS6nHrWH2WqQxRbiITl0irkQoz\npwNEF2Bv0+Jvs1UFEdVGz5a8xexQHst/RmKrtHLct3iOCvBNqoAQRbvWvBhPjO/p\nV5cYeUljZ5wpHyFkaEViClaVWqa6PIsyLqmyjsruPCWlURLsQoQxABcL8bwxX7UT\nhM6CtH6tGlYZ85RIzRifIm2oudzV5l+8oRgFr9yVcwyOFT6JCioqkwldW52P1pk/\n/SnuexC6LYqqDuHUs5NnokzzpfS6QaWfTY5P5tz4KHJfsjDIktly3mKVfY0fSPVV\nokdGpcUzvz2hq1fqjxB6MlB/1vtk0bImfcsoxBmF7H+4E9ZN1sX/tSb0KQARAQAB\ntCZPcGVuIFJvYm90aWNzIDxpbmZvQG9zcmZvdW5kYXRpb24ub3JnPokCVAQTAQoA\nPhYhBMHPbjHmut6IaLFytPQu1vurF8ZUBQJc7yaWAhsDBQkDwmcABQsJCAcCBhUK\nCQgLAgQWAgMBAh4BAheAAAoJEPQu1vurF8ZUkhIP/RbZY1ErvCEUy8iLJm9aSpLQ\nnDZl5xILOxyZlzpg+Ml5bb0EkQDr92foCgcvLeANKARNCaGLyNIWkuyDovPV0xZJ\nrEy0kgBrDNb3++NmdI/+GA92pkedMXXioQvqdsxUagXAIB/sNGByJEhs37F05AnF\nvZbjUhceq3xTlvAMcrBWrgB4NwBivZY6IgLvl/CRQpVYwANShIQdbvHvZSxRonWh\nNXr6v/Wcf8rsp7g2VqJ2N2AcWT84aa9BLQ3Oe/SgrNx4QEhA1y7rc3oaqPVu5ZXO\nK+4O14JrpbEZ3Xs9YEjrcOuEDEpYktA8qqUDTdFyZrxb9S6BquUKrA6jZgT913kj\nJ4e7YAZobC4rH0w4u0PrqDgYOkXA9Mo7L601/7ZaDJob80UcK+Z12ZSw73IgBix6\nDiJVfXuWkk5PM2zsFn6UOQXUNlZlDAOj5NC01V0fJ8P0v6GO9YOSSQx0j5UtkUbR\nfp/4W7uCPFvwAatWEHJhlM3sQNiMNStJFegr56xQu1a/cbJH7GdbseMhG/f0BaKQ\nqXCI3ffB5y5AOLc9Hw7PYiTFQsuY1ePRhE+J9mejgWRZxkjAH/FlAubqXkDgterC\nh+sLkzGf+my2IbsMCuc+3aeNMJ5Ej/vlXefCH/MpPWAHCqpQhe2DET/jRSaM53US\nAHNx8kw4MPUkxExgI7Sd\n=4Ofr\n-----END PGP PUBLIC KEY BLOCK-----" > /tmp/keys/0.key && apt-key add /tmp/keys/0.key
---> Running in d1c201aa32c1
OK
Removing intermediate container d1c201aa32c1
---> 39e258d38fce
Step 12/25 : RUN echo deb http://repositories.ros.org/ubuntu/building xenial main | tee -a /etc/apt/sources.list.d/buildfarm.list
---> Running in bda191011eaa
deb http://repositories.ros.org/ubuntu/building xenial main
Removing intermediate container bda191011eaa
---> 798f8cbc5c88
Step 13/25 : RUN echo deb-src http://repositories.ros.org/ubuntu/building xenial main | tee -a /etc/apt/sources.list.d/buildfarm.list
---> Running in e261d5104f56
deb-src http://repositories.ros.org/ubuntu/building xenial main
Removing intermediate container e261d5104f56
---> cd49cd3fc267
Step 14/25 : RUN grep -q -F -e "deb http://old-releases.ubuntu.com" /etc/apt/sources.list && ((grep -q -E -x -e "deb http://old-releases\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb http://old-releases.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://old-releases\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb-src http://old-releases.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://old-releases\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb http://old-releases.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://old-releases\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb-src http://old-releases.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://old-releases\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb http://old-releases.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://old-releases\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z]+)*" /etc/apt/sources.list || echo "deb-src http://old-releases.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list)) || ((grep -q -E -x -e "deb http://archive\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb http://archive.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://archive\.ubuntu\.com/ubuntu/? xenial ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb-src http://archive.ubuntu.com/ubuntu/ xenial multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://archive\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb http://archive.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://archive\.ubuntu\.com/ubuntu/? xenial-updates ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb-src http://archive.ubuntu.com/ubuntu/ xenial-updates multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb http://archive\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb http://archive.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list) && (grep -q -E -x -e "deb-src http://archive\.ubuntu\.com/ubuntu/? xenial-security ([-a-z]+ )*multiverse( [-a-z])*" /etc/apt/sources.list || echo "deb-src http://archive.ubuntu.com/ubuntu/ xenial-security multiverse" >> /etc/apt/sources.list))
---> Running in 6beb9abdec2d
Removing intermediate container 6beb9abdec2d
---> edb0a2c9bf2f
Step 15/25 : RUN mkdir /tmp/wrapper_scripts
---> Running in 83c0715b18b4
FATAL: command execution failed
java.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
at com.sun.proxy.$Proxy82.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1150)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1142)
at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1853)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:427)
FATAL: Unable to delete script file /tmp/jenkins1519074162017687452.sh
java.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@5c23637e:JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446": Remote call on JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446 failed. The channel is closing down or has closed down
at hudson.remoting.Channel.call(Channel.java:948)
at hudson.FilePath.act(FilePath.java:1069)
at hudson.FilePath.act(FilePath.java:1058)
at hudson.FilePath.delete(FilePath.java:1539)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1853)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:427)
Build step 'Execute shell' marked build as failure
FATAL: Channel "hudson.remoting.Channel@5c23637e:JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446": Remote call on JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446 failed. The channel is closing down or has closed down
java.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@5c23637e:JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446": Remote call on JNLP4-connect connection from 172.30.1.189/172.30.1.189:55446 failed. The channel is closing down or has closed down
at hudson.remoting.Channel.call(Channel.java:948)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
at com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.stop(ExecRemoteAgent.java:130)
at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.tearDown(SSHAgentBuildWrapper.java:417)
at hudson.model.Build$BuildExecution.doRun(Build.java:174)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1853)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:427)

ROS Buildfarm

unread,
Jul 8, 2020, 7:31:15 PM7/8/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/75/display/redirect>
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 31885 killed;
[ssh-agent] Stopped.

ROS Buildfarm

unread,
Jul 9, 2020, 7:05:20 PM7/9/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/76/display/redirect>

Changes:


------------------------------------------
[...truncated 226.59 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 5002 killed;
[ssh-agent] Stopped.

ROS Buildfarm

unread,
Jul 10, 2020, 7:08:22 PM7/10/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/77/display/redirect>

Changes:


------------------------------------------
[...truncated 333.14 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 966 killed;

ROS Buildfarm

unread,
Jul 11, 2020, 7:26:29 PM7/11/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/78/display/redirect>
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
# END SUBSECTION
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2482 killed;

ROS Buildfarm

unread,
Jul 12, 2020, 7:25:54 PM7/12/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/79/display/redirect>

Changes:


------------------------------------------
[...truncated 225.84 KB...]
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 10025 killed;

ROS Buildfarm

unread,
Jul 13, 2020, 7:07:59 PM7/13/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/80/display/redirect>

Changes:


------------------------------------------
[...truncated 333.20 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 9255 killed;

ROS Buildfarm

unread,
Jul 14, 2020, 7:05:27 PM7/14/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/81/display/redirect>

Changes:


------------------------------------------
[...truncated 227.18 KB...]
//ADVANCED property for variable: CMAKE_EXEdh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
echo Agent pid 16131 killed;

ROS Buildfarm

unread,
Jul 15, 2020, 7:14:50 PM7/15/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/82/display/redirect>

Changes:


------------------------------------------
[...truncated 226.15 KB...]
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
echo Agent pid 10516 killed;

ROS Buildfarm

unread,
Jul 16, 2020, 7:33:12 PM7/16/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/83/display/redirect>

Changes:


------------------------------------------
[...truncated 333.23 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
# END SUBSECTION
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1986 killed;

ROS Buildfarm

unread,
Jul 17, 2020, 7:26:04 PM7/17/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/84/display/redirect>

Changes:


------------------------------------------
[...truncated 333.24 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 31801 killed;

ROS Buildfarm

unread,
Jul 18, 2020, 7:21:33 PM7/18/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/85/display/redirect>

Changes:


------------------------------------------
[...truncated 225.86 KB...]
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 7880 killed;

ROS Buildfarm

unread,
Jul 19, 2020, 7:29:18 PM7/19/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/86/display/redirect>

Changes:


------------------------------------------
[...truncated 333.23 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1948 killed;

ROS Buildfarm

unread,
Jul 20, 2020, 7:31:25 PM7/20/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/87/display/redirect>

Changes:


------------------------------------------
[...truncated 328.59 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 30515 killed;

ROS Buildfarm

unread,
Jul 21, 2020, 7:04:12 PM7/21/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/88/display/redirect>

Changes:


------------------------------------------
[...truncated 226.50 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1700 killed;

ROS Buildfarm

unread,
Jul 22, 2020, 7:20:06 PM7/22/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/89/display/redirect>

Changes:


------------------------------------------
[...truncated 225.85 KB...]
//ADVANCED property for variable: CMAKE_EXEdh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 29540 killed;

ROS Buildfarm

unread,
Jul 23, 2020, 7:07:51 PM7/23/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/90/display/redirect>

Changes:


------------------------------------------
[...truncated 333.62 KB...]
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 22639 killed;

ROS Buildfarm

unread,
Jul 24, 2020, 7:08:15 PM7/24/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/91/display/redirect>

Changes:


------------------------------------------
[...truncated 328.57 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 25284 killed;

ROS Buildfarm

unread,
Jul 25, 2020, 7:08:07 PM7/25/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/92/display/redirect>

Changes:


------------------------------------------
[...truncated 332.65 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 15672 killed;

ROS Buildfarm

unread,
Jul 26, 2020, 7:25:20 PM7/26/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/93/display/redirect>

Changes:


------------------------------------------
[...truncated 333.22 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 27765 killed;

ROS Buildfarm

unread,
Jul 27, 2020, 7:08:36 PM7/27/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/94/display/redirect>

Changes:


------------------------------------------
[...truncated 332.68 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 20505 killed;

ROS Buildfarm

unread,
Jul 28, 2020, 7:25:14 PM7/28/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/95/display/redirect>

Changes:


------------------------------------------
[...truncated 333.27 KB...]
make[1]: *** [override_dh_auto_configure] Error 255
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 25784 killed;

ROS Buildfarm

unread,
Jul 29, 2020, 7:07:10 PM7/29/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/96/display/redirect>

Changes:


------------------------------------------
[...truncated 328.59 KB...]
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

# END SUBSECTION
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 24494 killed;

ROS Buildfarm

unread,
Jul 30, 2020, 7:08:03 PM7/30/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/97/display/redirect>

Changes:


------------------------------------------
[...truncated 328.60 KB...]
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 9964 killed;

ROS Buildfarm

unread,
Aug 1, 2020, 1:23:26 AM8/1/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/98/display/redirect>

Changes:


------------------------------------------
[...truncated 225.92 KB...]
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 10048 killed;

ROS Buildfarm

unread,
Aug 1, 2020, 9:25:50 PM8/1/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/99/display/redirect>
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
# END SUBSECTION
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 4472 killed;

ROS Buildfarm

unread,
Aug 2, 2020, 7:06:43 PM8/2/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/100/display/redirect>

Changes:


------------------------------------------
[...truncated 226.37 KB...]
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/opt/ros/kinetic returned exit code 1
cd /tmp/binarydeb/ros-kinetic-webrtc-59.0.4
make[1]: *** [override_dh_auto_configure] Error 255
debian/rules:25: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/tmp/binarydeb/ros-kinetic-webrtc-59.0.4'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
# END SUBSECTION
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 18425 killed;

ROS Buildfarm

unread,
Aug 3, 2020, 7:04:56 PM8/3/20
to ros-buildf...@googlegroups.com, tfoote+b...@osrfoundation.org, timo.r...@fkie.fraunhofer.de
See <http://build.ros.org/job/Kbin_uX32__webrtc__ubuntu_xenial_i386__binary/101/display/redirect>

Changes:


------------------------------------------
[...truncated 226.87 KB...]
make: *** [binary] Error 2
debian/rules:22: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Building failed
Traceback (most recent call last):
File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 138, in build_binarydeb
subprocess.check_call(cmd, cwd=source_dir)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-kinetic-webrtc']' returned non-zero exit status 1
# END SUBSECTION

--------------------------------------------------------------------------------------------------
`apt-src build ros-kinetic-webrtc` failed.
This is usually because of an error building the package.
The traceback from this failure (just above) is printed for completeness, but you can ignore it.
You should look above `E: Building failed` in the build log for the actual cause of the failure.
--------------------------------------------------------------------------------------------------

Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 23857 killed;
It is loading more messages.
0 new messages