build slaves

historical

On Sun, Jan 07, 2018 at 05:58:40PM +0100, Max wrote:
> Hi.
> 
> Seems like jobs which update osmo-ci and osmo-python-tests on build slaves are
> failing for 20+ days. This only happens for some of the slaves but not the others.
> 
> I'd like to understand why this is happening and, ideally, fix it. However, there're
> few obstacles:

It's because of

"ImportError: No module named setuptools"

since your commit, where you obviously never checked whether setuptools is
available on the build slaves:

Author:     Max <msuraev at sysmocom.de>
AuthorDate: Fri Dec 15 12:12:01 2017 +0100
Commit:     Max <msuraev at sysmocom.de>
CommitDate: Fri Dec 15 20:40:41 2017 +0100

    Use setuptools for packaging

    According to https://docs.python.org/3/library/distutils.html the
    setuptools are used in place of distutils anyway. Using it directly
    allows us to make packaging more flexible: specify dependencies,
    automatically find package name etc.

    Change-Id: I39ee53f352001e47c6df055cbec52d638480253d

I see console logs fine.
https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/63/label=OsmocomBuild1/console
https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/63/label=build2-deb8build/console

So do we really need this setuptools thing or can we just revert the change?

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180107/101761f2/attachment.bin>