All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jenkins Builder Robot <jenkins@linuxtv.org>
To: mchehab@kernel.org, linux-media@vger.kernel.org,
	libcamera-devel@lists.libcamera.org
Subject: Build failed in Jenkins: libcamera #174
Date: Wed, 13 May 2020 14:18:20 +0000 (UTC)	[thread overview]
Message-ID: <1444985187.25.1589379500987.JavaMail.jenkins@builder.linuxtv.org> (raw)
In-Reply-To: <2088872996.24.1589378624749.JavaMail.jenkins@builder.linuxtv.org>

See <https://builder.linuxtv.org/job/libcamera/174/display/redirect?page=changes>

Changes:

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E231

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E201 and E202

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E203

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E241

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E211

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E251

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E128

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E225

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E228

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E701

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E303

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E261 and E262

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E222

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E711 and E712

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E123 and E126

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E116 and E117

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E713

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E721

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E722

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle W504

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E741

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E305

[laurent.pinchart] utils: raspberrypi: ctt: Fix pycodestyle E302


------------------------------------------
Started by an SCM change
Running as SYSTEM
Building remotely on slave2 in workspace <https://builder.linuxtv.org/job/libcamera/ws/>
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://linuxtv.org/libcamera.git # timeout=10
Fetching upstream changes from git://linuxtv.org/libcamera.git
 > git --version # timeout=10
 > git fetch --tags --force --progress -- git://linuxtv.org/libcamera.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision e8655c2161a97261971ef19621a34651980b76d6 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e8655c2161a97261971ef19621a34651980b76d6 # timeout=10
Commit message: "utils: raspberrypi: ctt: Fix pycodestyle E302"
 > git rev-list --no-walk 7a653369cb42e1611b884f4a16de60d1b60aa8e7 # timeout=10
[libcamera] $ /bin/sh -xe /tmp/jenkins11751882835199749524.sh
+ meson setup --wipe build
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 112, in run
    return options.run_func(options)
  File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 229, in run
    app = MesonApp(options)
  File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 82, in __init__
    mesonlib.windows_proof_rmtree(l)
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonlib.py", line 1116, in windows_proof_rmtree
    shutil.rmtree(f)
  File "/usr/lib/python3.7/shutil.py", line 501, in rmtree
    onerror(os.path.islink, path, sys.exc_info())
  File "/usr/lib/python3.7/shutil.py", line 499, in rmtree
    raise OSError("Cannot call rmtree on a symbolic link")
OSError: Cannot call rmtree on a symbolic link
+ true
+ meson configure build

ERROR: No such build data file as "'<https://builder.linuxtv.org/job/libcamera/ws/build/meson-private/build.dat'".>
+ meson build
The Meson build system
Version: 0.49.2
Source dir: <https://builder.linuxtv.org/job/libcamera/ws/>
Build dir: <https://builder.linuxtv.org/job/libcamera/ws/build>
Build type: native build
Project name: libcamera
Project version: 0.0.0
Native C compiler: ccache cc (gcc 8.3.0 "cc (Debian 8.3.0-6) 8.3.0")
Native C++ compiler: ccache c++ (gcc 8.3.0 "c++ (Debian 8.3.0-6) 8.3.0")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Header <execinfo.h> has symbol "backtrace" : YES
Header <stdlib.h> has symbol "secure_getenv" : YES
Compiler for C supports arguments -Wno-c99-designator -Wc99-designator: NO
Configuring version.h using configuration
Program openssl found: YES (/usr/bin/openssl)
Library atomic found: YES
Library dl found: YES
Library gnutls found: YES
Found pkg-config: /usr/bin/pkg-config (0.29)
Dependency libudev found: YES 241
Dependency threads found: YES 
Dependency Boost found: NO 

src/ipa/raspberrypi/meson.build:5:0: ERROR:  Dependency "boost" not found

A full log can be found at <https://builder.linuxtv.org/job/libcamera/ws/build/meson-logs/meson-log.txt>
Build step 'Execute shell' marked build as failure

  reply	other threads:[~2020-05-13 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 21:03 Build failed in Jenkins: libcamera #172 Jenkins Builder Robot
2020-05-11 21:12 ` [libcamera-devel] " Laurent Pinchart
2020-05-13 14:03 ` Build failed in Jenkins: libcamera #173 Jenkins Builder Robot
2020-05-13 14:18   ` Jenkins Builder Robot [this message]
2020-05-13 19:18     ` Build failed in Jenkins: libcamera #175 Jenkins Builder Robot
2020-05-14 12:24       ` Jenkins build is back to normal : libcamera #176 Jenkins Builder Robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1444985187.25.1589379500987.JavaMail.jenkins@builder.linuxtv.org \
    --to=jenkins@linuxtv.org \
    --cc=libcamera-devel@lists.libcamera.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.