From patchwork Mon Jan 19 10:20:34 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Barnab=C3=A1s_P=C5=91cze?= X-Patchwork-Id: 25839 Return-Path: X-Original-To: parsemail@patchwork.libcamera.org Delivered-To: parsemail@patchwork.libcamera.org Received: from lancelot.ideasonboard.com (lancelot.ideasonboard.com [92.243.16.209]) by patchwork.libcamera.org (Postfix) with ESMTPS id C93A0C3220 for ; Mon, 19 Jan 2026 10:20:46 +0000 (UTC) Received: from lancelot.ideasonboard.com (localhost [IPv6:::1]) by lancelot.ideasonboard.com (Postfix) with ESMTP id EF86461FCC; Mon, 19 Jan 2026 11:20:45 +0100 (CET) Authentication-Results: lancelot.ideasonboard.com; dkim=pass (1024-bit key; unprotected) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="DDoXreJy"; dkim-atps=neutral Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [IPv6:2001:4b98:dc2:55:216:3eff:fef7:d647]) by lancelot.ideasonboard.com (Postfix) with ESMTPS id B5D0961F9F for ; Mon, 19 Jan 2026 11:20:43 +0100 (CET) Received: from pb-laptop.local (185.221.143.114.nat.pool.zt.hu [185.221.143.114]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 3BC732D9 for ; Mon, 19 Jan 2026 11:20:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1768818013; bh=PNpm9cXM/u4M+Dk42fVqH++iGCBmtBHHQnQxEJ3tPMM=; h=From:To:Subject:Date:From; b=DDoXreJyl0klfeLyqMBtDKxb1Lrv6e0bq0rnCyJseFwU6eAK0khaKF+rDii/w+lMp 3bR+jow7d8I74d+pnY//Fv5Upztjywi5PctFdlnOS0BOag0XHNy2F4lga41CFTc20G KhUAlRugPEV4D1m4sRELWeHwN1k4UuSJo8Lq6Pms= From: =?utf-8?q?Barnab=C3=A1s_P=C5=91cze?= To: libcamera-devel@lists.libcamera.org Subject: [libcamera-ci] [RFC PATCH v1 0/5] on-device-testing proof of concept Date: Mon, 19 Jan 2026 11:20:34 +0100 Message-ID: <20260119102039.3521673-1-barnabas.pocze@ideasonboard.com> X-Mailer: git-send-email 2.52.0 MIME-Version: 1.0 X-BeenThere: libcamera-devel@lists.libcamera.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libcamera-devel-bounces@lists.libcamera.org Sender: "libcamera-devel" This adds the necessary gitlab parts for running lc-compliance via lava on a "real" device, specifically a debix-a board with an imx219 sensor. There are three parts to the process: 1. libcamera is cross-compiled to the target architecture. This uses a separate container, and does not use setup-container.sh. 2. A debian root file system is built, appropriate for running libcamera as compiled in (1). 3. LAVA job is submitted to the lava worker to run `test-libcamera.sh` on the device. Couple points: 1. While building debian root filesystem is integrated in the pipeline, manual intervention is needed. It must be uploaded to the lava worker's local container registry. Either one has to build the image locally or pull it from the gitlab container registry; and then upload it to the local registry. Specifying which container image the device should use is not implemented at the moment, it is hard-coded on the device itself. The jobs are triggered manually, so this is conveniently doable before the actual testing starts. Nonetheless I think be very nice if this could be fully automatic. 2. The cross compilation and rootfs generation both use their own separate containers, and separate setup processes not integrated with setup-container.sh. To be honest I find that whole mechanism is a unfortunate, I feel like it already multiplexes too many things. 3. lava-gitlab-runner can only use files from artifacts and not from the repository (https://github.com/collabora/lava-gitlab-runner/issues/16), so there is a job `lava-jobs-as-artifacts` for that. Although even if it could, the libcamera ci definitions are in a separate repository, so that would most likely still not work. 4. The cross compilation jobs saves the url of the debian package artifact in a `dotenv` artifact report, for lava-gitlab-runner to access it, and for it to be accessible on the device to download and install the package. This is needed because there does not appear to be a way to download job artifacts based on the (pipeline id, job name) tuple, same applies to getting the job id from another job. At least without more complex use of the gitlab api. But this means that the lava job must get the artifacts from the cross compilation job, which unfortunately means downloading the deb package unnecessarily. 5. The camera id is hard-coded in the lava job definition. Maybe it could be better to extend lc-compliance to support camera indices. Barnabás Pőcze (5): Add job to generate container for cross compilation Add job to build deb package for libcamera Add job to build debian rootfs Add job to run lc-compliance via lava Guard jobs required for hardware testing .gitlab-ci/build-debian-rootfs.sh | 79 ++++++++ .../opt/test-libcamera.sh | 18 ++ .gitlab-ci/on-device-testing/lava-debix-a.yml | 40 ++++ .gitlab-ci/setup-debian-cross-container.sh | 45 +++++ gitlab-ci.yml | 180 ++++++++++++++++++ 5 files changed, 362 insertions(+) create mode 100755 .gitlab-ci/build-debian-rootfs.sh create mode 100755 .gitlab-ci/debian-rootfs-overlay/opt/test-libcamera.sh create mode 100644 .gitlab-ci/on-device-testing/lava-debix-a.yml create mode 100755 .gitlab-ci/setup-debian-cross-container.sh --- 2.52.0