linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jenkins Builder Robot <jenkins@linuxtv.org>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
	libcamera-devel@lists.libcamera.org
Subject: Re: [libcamera-devel] Build failed in Jenkins: libcamera #172
Date: Tue, 12 May 2020 00:12:32 +0300	[thread overview]
Message-ID: <20200511211232.GG5830@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2081683680.23.1589231002255.JavaMail.jenkins@builder.linuxtv.org>

Hello,

On Mon, May 11, 2020 at 09:03:22PM +0000, Jenkins Builder Robot wrote:
> See <https://builder.linuxtv.org/job/libcamera/172/display/redirect?page=changes>
> 
> Changes:
> 
> [laurent.pinchart] LICENSES: Add BSD-2-Clause license
> 
> [laurent.pinchart] include: uapi: Add header definitions for BCM2835 Unicam and ISP blocks
> 
> [laurent.pinchart] libcamera: pipeline: Raspberry Pi pipeline handler
> 
> [laurent.pinchart] libcamera: ipa: Raspberry Pi IPA
> 
> [laurent.pinchart] libcamera: utils: Raspberry Pi Camera Tuning Tool
> 
> [laurent.pinchart] libcamera: raspberrypi: Add components to meson build
> 
> 
> ------------------------------------------
> 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 4bb5b1f60248ada4a26e1114940d1bff1cae5bfc (refs/remotes/origin/master)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 4bb5b1f60248ada4a26e1114940d1bff1cae5bfc # timeout=10
> Commit message: "libcamera: raspberrypi: Add components to meson build"
>  > git rev-list --no-walk 019a145068b714482bbf791c0f296abd06ec0dc1 # timeout=10
> [libcamera] $ /bin/sh -xe /tmp/jenkins4639663244990242363.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

This is a bug in meson, fixed by
https://github.com/mesonbuild/meson/pull/7055. Until a new release
becomes available, I recommend either removing the build tree manually
before calling meson setup (and dropping the --wipe argument), or
removing the source symlink manually before running 'meson setup --wipe
build'.

> + 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:3:0: ERROR:  Dependency "boost" not found

The Raspberry Pi pipeline handler requires boost. If that dependency
can't be easily added to the build machine, the pipeline handlers can be
selected manually:

meson configure -Dpipelines='ipu3, rkisp1, simple, uvcvideo, vimc'

We should likely disable pipeline handlers automatically when
dependencies are missing.

> 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

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2020-05-11 21:12 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 ` Laurent Pinchart [this message]
2020-05-13 14:03 ` Build failed in Jenkins: libcamera #173 Jenkins Builder Robot
2020-05-13 14:18   ` Build failed in Jenkins: libcamera #174 Jenkins Builder Robot
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=20200511211232.GG5830@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).