[{"id":38096,"web_url":"https://patchwork.libcamera.org/comment/38096/","msgid":"<20260205132827.GL156228@killaraus>","date":"2026-02-05T13:28:27","subject":"Re: [libcamera-ci] [RFC PATCH v2 0/5] on-device-testing proof of\n\tconcept","submitter":{"id":2,"url":"https://patchwork.libcamera.org/api/people/2/","name":"Laurent Pinchart","email":"laurent.pinchart@ideasonboard.com"},"content":"On Fri, Jan 30, 2026 at 05:02:49PM +0100, Barnabás Pőcze wrote:\n> This adds the necessary gitlab parts for running lc-compliance via\n> lava on a \"real\" device, specifically a debix-a board with an imx219\n> sensor.\n> \n> There are three parts to the process:\n> \n> 1. libcamera is cross-compiled to the target architecture.\n> This uses a separate container, and does not use setup-container.sh.\n> \n> 2. A debian root file system is built, appropriate for running\n> libcamera as compiled in (1).\n> \n> 3. LAVA job is submitted to the lava worker to run `test-libcamera.sh`\n> on the device.\n> \n> Couple points:\n> \n> * Deploying the debian root filesystem is a manual process. It must be built and\n> uploaded to the lava worker's local container registry. Specifying which container\n> image the device should use is not implemented at the moment, it is hard-coded on\n> the device itself.\n> \n> I think be very nice if this could be fully automatic.\n> \n> * lava-gitlab-runner can only use files from artifacts and not from\n> the repository (https://github.com/collabora/lava-gitlab-runner/issues/16),\n> so there is a job `lava-jobs-as-artifacts` for that. Although even if it\n> could, the libcamera ci definitions are in a separate repository, so that\n> would most likely still not work.\n> \n> * The cross compilation jobs saves the url of the debian package artifact\n> in a `dotenv` artifact report, for lava-gitlab-runner to access it, and for\n> it to be accessible on the device to download and install the package.\n> \n> This is needed because there does not appear to be a way to download job\n> artifacts based on the (pipeline id, job name) tuple, same applies to getting\n> the job id from another job. At least without more complex use of the gitlab api.\n> \n> But this means that the lava job must get the artifacts from the cross compilation\n> job, which unfortunately means downloading the deb package unnecessarily.\n\nYes that's annoying. The lava runner has some serious limitations, I\ndon't understand how this behaviour hasn't annoyed other people enough\nto fix the problem :-)\n\n> * The camera id is hard-coded in the lava job definition. Maybe it could be better\n> to extend lc-compliance to support camera indices.\n\nOr possibly pipeline handlers, if the goal is to test a particular\npipeline handler.\n\n> * dependencies:\n> - https://patchwork.libcamera.org/project/libcamera/list/?series=5756\n> - https://patchwork.libcamera.org/patch/26038/\n> \n> ---\n> changes in v2:\n> * use existing containers\n> * manual rootfs workflow\n> \n> v1: https://patchwork.libcamera.org/cover/25839/\n> ---\n> Barnabás Pőcze (5):\n> Install `fpm` in the debian 13 container\n> Add job to build deb package for libcamera\n> Add job to run lc-compliance via lava\n> Guard hardware testing jobs\n> Add description about debian rootfs setup for testing\n> \n> .gitlab-ci/on-device-testing/lava-debix-a.yml | 40 ++++++++\n> .gitlab-ci/setup-container.sh | 6 ++\n> .../debian-rootfs/build-debian-rootfs.sh | 62 ++++++++++++\n> containers/debian-rootfs/build.sh | 9 ++\n> .../overlay/opt/test-libcamera.sh | 18 ++++\n> doc/debian-rootfs.rst | 47 +++++++++\n> gitlab-ci.yml | 95 ++++++++++++++++++-\n> 7 files changed, 276 insertions(+), 1 deletion(-)\n> create mode 100644 .gitlab-ci/on-device-testing/lava-debix-a.yml\n> create mode 100755 containers/debian-rootfs/build-debian-rootfs.sh\n> create mode 100755 containers/debian-rootfs/build.sh\n> create mode 100755 containers/debian-rootfs/overlay/opt/test-libcamera.sh\n> create mode 100644 doc/debian-rootfs.rst","headers":{"Return-Path":"","X-Original-To":"parsemail@patchwork.libcamera.org","Delivered-To":"parsemail@patchwork.libcamera.org","Received":["from lancelot.ideasonboard.com (lancelot.ideasonboard.com\n\t[92.243.16.209])\n\tby patchwork.libcamera.org (Postfix) with ESMTPS id 7A71BBD78E\n\tfor ;\n\tThu, 5 Feb 2026 13:28:32 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id 7E3066205F;\n\tThu, 5 Feb 2026 14:28:31 +0100 (CET)","from perceval.ideasonboard.com (perceval.ideasonboard.com\n\t[213.167.242.64])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id 4F33162010\n\tfor ;\n\tThu, 5 Feb 2026 14:28:29 +0100 (CET)","from killaraus.ideasonboard.com\n\t(2001-14ba-703d-e500--2a1.rev.dnainternet.fi\n\t[IPv6:2001:14ba:703d:e500::2a1])\n\tby perceval.ideasonboard.com (Postfix) with UTF8SMTPSA id 3C5E9D0;\n\tThu, 5 Feb 2026 14:27:46 +0100 (CET)"],"Authentication-Results":"lancelot.ideasonboard.com; dkim=pass (1024-bit key;\n\tunprotected) header.d=ideasonboard.com header.i=@ideasonboard.com\n\theader.b=\"bal/72bv\"; dkim-atps=neutral","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com;\n\ts=mail; t=1770298066;\n\tbh=Saotqm+8MugAjmYPW0RoFV9JHn1LG5CjMFmA87wAZhQ=;\n\th=Date:From:To:Cc:Subject:References:In-Reply-To:From;\n\tb=bal/72bv13VtD+o0LXYpvdmheAKYhmiTih80v+VxIKwL0HN33DPQRNmRdWHkhJbUE\n\tIPBLN1GUAAbz7Xtf3zKzXKn6lAR4Tj/KGngp8BHMEDVrM5Y7610MjJgOWyXq5NFhf1\n\tMoLoHYu5CmI8Ewjwe9TvUjtEsaomBpfqourhaYRs=","Date":"Thu, 5 Feb 2026 15:28:27 +0200","From":"Laurent Pinchart ","To":"=?utf-8?q?Barnab=C3=A1s_P=C5=91cze?= ","Cc":"libcamera-devel@lists.libcamera.org","Subject":"Re: [libcamera-ci] [RFC PATCH v2 0/5] on-device-testing proof of\n\tconcept","Message-ID":"<20260205132827.GL156228@killaraus>","References":"<20260130160254.1770742-1-barnabas.pocze@ideasonboard.com>","MIME-Version":"1.0","Content-Type":"text/plain; charset=utf-8","Content-Disposition":"inline","Content-Transfer-Encoding":"8bit","In-Reply-To":"<20260130160254.1770742-1-barnabas.pocze@ideasonboard.com>","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"","List-Unsubscribe":",\n\t","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n\t","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" "}},{"id":38147,"web_url":"https://patchwork.libcamera.org/comment/38147/","msgid":"<2062b812-4127-42fa-ab35-8749605ce038@ideasonboard.com>","date":"2026-02-09T10:39:03","subject":"Re: [libcamera-ci] [RFC PATCH v2 0/5] on-device-testing proof of\n\tconcept","submitter":{"id":216,"url":"https://patchwork.libcamera.org/api/people/216/","name":"Barnabás Pőcze","email":"barnabas.pocze@ideasonboard.com"},"content":"2026. 02. 05. 14:28 keltezéssel, Laurent Pinchart írta:\n> On Fri, Jan 30, 2026 at 05:02:49PM +0100, Barnabás Pőcze wrote:\n>> This adds the necessary gitlab parts for running lc-compliance via\n>> lava on a \"real\" device, specifically a debix-a board with an imx219\n>> sensor.\n>>\n>> There are three parts to the process:\n>>\n>> 1. libcamera is cross-compiled to the target architecture.\n>> This uses a separate container, and does not use setup-container.sh.\n>>\n>> 2. A debian root file system is built, appropriate for running\n>> libcamera as compiled in (1).\n>>\n>> 3. LAVA job is submitted to the lava worker to run `test-libcamera.sh`\n>> on the device.\n>>\n>> Couple points:\n>>\n>> * Deploying the debian root filesystem is a manual process. It must be built and\n>> uploaded to the lava worker's local container registry. Specifying which container\n>> image the device should use is not implemented at the moment, it is hard-coded on\n>> the device itself.\n>>\n>> I think be very nice if this could be fully automatic.\n>>\n>> * lava-gitlab-runner can only use files from artifacts and not from\n>> the repository (https://github.com/collabora/lava-gitlab-runner/issues/16),\n>> so there is a job `lava-jobs-as-artifacts` for that. Although even if it\n>> could, the libcamera ci definitions are in a separate repository, so that\n>> would most likely still not work.\n>>\n>> * The cross compilation jobs saves the url of the debian package artifact\n>> in a `dotenv` artifact report, for lava-gitlab-runner to access it, and for\n>> it to be accessible on the device to download and install the package.\n>>\n>> This is needed because there does not appear to be a way to download job\n>> artifacts based on the (pipeline id, job name) tuple, same applies to getting\n>> the job id from another job. At least without more complex use of the gitlab api.\n>>\n>> But this means that the lava job must get the artifacts from the cross compilation\n>> job, which unfortunately means downloading the deb package unnecessarily.\n> \n> Yes that's annoying. The lava runner has some serious limitations, I\n> don't understand how this behaviour hasn't annoyed other people enough\n> to fix the problem :-)\n\nI suppose the question is: does it annoy us enough?\n\n\n> \n>> * The camera id is hard-coded in the lava job definition. Maybe it could be better\n>> to extend lc-compliance to support camera indices.\n> \n> Or possibly pipeline handlers, if the goal is to test a particular\n> pipeline handler.\n\nThat information is not available yet, no? So it would be a an API addition as well?\n\n\n> \n>> * dependencies:\n>> - https://patchwork.libcamera.org/project/libcamera/list/?series=5756\n>> - https://patchwork.libcamera.org/patch/26038/\n>>\n>> ---\n>> changes in v2:\n>> * use existing containers\n>> * manual rootfs workflow\n>>\n>> v1: https://patchwork.libcamera.org/cover/25839/\n>> ---\n>> Barnabás Pőcze (5):\n>> Install `fpm` in the debian 13 container\n>> Add job to build deb package for libcamera\n>> Add job to run lc-compliance via lava\n>> Guard hardware testing jobs\n>> Add description about debian rootfs setup for testing\n>>\n>> .gitlab-ci/on-device-testing/lava-debix-a.yml | 40 ++++++++\n>> .gitlab-ci/setup-container.sh | 6 ++\n>> .../debian-rootfs/build-debian-rootfs.sh | 62 ++++++++++++\n>> containers/debian-rootfs/build.sh | 9 ++\n>> .../overlay/opt/test-libcamera.sh | 18 ++++\n>> doc/debian-rootfs.rst | 47 +++++++++\n>> gitlab-ci.yml | 95 ++++++++++++++++++-\n>> 7 files changed, 276 insertions(+), 1 deletion(-)\n>> create mode 100644 .gitlab-ci/on-device-testing/lava-debix-a.yml\n>> create mode 100755 containers/debian-rootfs/build-debian-rootfs.sh\n>> create mode 100755 containers/debian-rootfs/build.sh\n>> create mode 100755 containers/debian-rootfs/overlay/opt/test-libcamera.sh\n>> create mode 100644 doc/debian-rootfs.rst\n>","headers":{"Return-Path":"","X-Original-To":"parsemail@patchwork.libcamera.org","Delivered-To":"parsemail@patchwork.libcamera.org","Received":["from lancelot.ideasonboard.com (lancelot.ideasonboard.com\n\t[92.243.16.209])\n\tby patchwork.libcamera.org (Postfix) with ESMTPS id 628D2C32E7\n\tfor ;\n\tMon, 9 Feb 2026 10:39:09 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id 95DAF620CB;\n\tMon, 9 Feb 2026 11:39:08 +0100 (CET)","from perceval.ideasonboard.com (perceval.ideasonboard.com\n\t[213.167.242.64])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id EB4E5615B2\n\tfor ;\n\tMon, 9 Feb 2026 11:39:06 +0100 (CET)","from [192.168.33.63] (185.221.141.206.nat.pool.zt.hu\n\t[185.221.141.206])\n\tby perceval.ideasonboard.com (Postfix) with ESMTPSA id 3830563F;\n\tMon, 9 Feb 2026 11:38:21 +0100 (CET)"],"Authentication-Results":"lancelot.ideasonboard.com; dkim=pass (1024-bit key;\n\tunprotected) header.d=ideasonboard.com header.i=@ideasonboard.com\n\theader.b=\"OQL5mLW9\"; dkim-atps=neutral","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com;\n\ts=mail; t=1770633501;\n\tbh=4BJD+/KiIYIWsDt9CfSi27V29oQRbLhPQ1u5sd8ij6E=;\n\th=Date:Subject:To:Cc:References:From:In-Reply-To:From;\n\tb=OQL5mLW957kVgZSHOC6QTsTwXLVwOn4hNqbqyqiT5D60oXqKx5naD4W9BCC6N4Wq7\n\t9yRwti5sZ4kbOVyaYtiBAMrQKHUFj/TI5X7NcnWT7guKxKgmmVR8Gl/VjTuoLuCGQE\n\trsfIq4FNPcsnN9u1JNwcfa34e876dVFMYafbpY0M=","Message-ID":"<2062b812-4127-42fa-ab35-8749605ce038@ideasonboard.com>","Date":"Mon, 9 Feb 2026 11:39:03 +0100","MIME-Version":"1.0","User-Agent":"Mozilla Thunderbird","Subject":"Re: [libcamera-ci] [RFC PATCH v2 0/5] on-device-testing proof of\n\tconcept","To":"Laurent Pinchart ","Cc":"libcamera-devel@lists.libcamera.org","References":"<20260130160254.1770742-1-barnabas.pocze@ideasonboard.com>\n\t<20260205132827.GL156228@killaraus>","From":"=?utf-8?q?Barnab=C3=A1s_P=C5=91cze?= ","Content-Language":"en-US, hu-HU","In-Reply-To":"<20260205132827.GL156228@killaraus>","Content-Type":"text/plain; charset=UTF-8; format=flowed","Content-Transfer-Encoding":"8bit","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"","List-Unsubscribe":",\n\t","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n\t","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" "}},{"id":38149,"web_url":"https://patchwork.libcamera.org/comment/38149/","msgid":"<20260209110309.GE2302514@killaraus.ideasonboard.com>","date":"2026-02-09T11:03:09","subject":"Re: [libcamera-ci] [RFC PATCH v2 0/5] on-device-testing proof of\n\tconcept","submitter":{"id":2,"url":"https://patchwork.libcamera.org/api/people/2/","name":"Laurent Pinchart","email":"laurent.pinchart@ideasonboard.com"},"content":"On Mon, Feb 09, 2026 at 11:39:03AM +0100, Barnabás Pőcze wrote:\n> 2026. 02. 05. 14:28 keltezéssel, Laurent Pinchart írta:\n> > On Fri, Jan 30, 2026 at 05:02:49PM +0100, Barnabás Pőcze wrote:\n> >> This adds the necessary gitlab parts for running lc-compliance via\n> >> lava on a \"real\" device, specifically a debix-a board with an imx219\n> >> sensor.\n> >>\n> >> There are three parts to the process:\n> >>\n> >> 1. libcamera is cross-compiled to the target architecture.\n> >> This uses a separate container, and does not use setup-container.sh.\n> >>\n> >> 2. A debian root file system is built, appropriate for running\n> >> libcamera as compiled in (1).\n> >>\n> >> 3. LAVA job is submitted to the lava worker to run `test-libcamera.sh`\n> >> on the device.\n> >>\n> >> Couple points:\n> >>\n> >> * Deploying the debian root filesystem is a manual process. It must be built and\n> >> uploaded to the lava worker's local container registry. Specifying which container\n> >> image the device should use is not implemented at the moment, it is hard-coded on\n> >> the device itself.\n> >>\n> >> I think be very nice if this could be fully automatic.\n> >>\n> >> * lava-gitlab-runner can only use files from artifacts and not from\n> >> the repository (https://github.com/collabora/lava-gitlab-runner/issues/16),\n> >> so there is a job `lava-jobs-as-artifacts` for that. Although even if it\n> >> could, the libcamera ci definitions are in a separate repository, so that\n> >> would most likely still not work.\n> >>\n> >> * The cross compilation jobs saves the url of the debian package artifact\n> >> in a `dotenv` artifact report, for lava-gitlab-runner to access it, and for\n> >> it to be accessible on the device to download and install the package.\n> >>\n> >> This is needed because there does not appear to be a way to download job\n> >> artifacts based on the (pipeline id, job name) tuple, same applies to getting\n> >> the job id from another job. At least without more complex use of the gitlab api.\n> >>\n> >> But this means that the lava job must get the artifacts from the cross compilation\n> >> job, which unfortunately means downloading the deb package unnecessarily.\n> > \n> > Yes that's annoying. The lava runner has some serious limitations, I\n> > don't understand how this behaviour hasn't annoyed other people enough\n> > to fix the problem :-)\n> \n> I suppose the question is: does it annoy us enough?\n\nMaybe this falls in the category of those issues that everybody would\nlove to see being fixed by someone else.\n\n> >> * The camera id is hard-coded in the lava job definition. Maybe it could be better\n> >> to extend lc-compliance to support camera indices.\n> > \n> > Or possibly pipeline handlers, if the goal is to test a particular\n> > pipeline handler.\n> \n> That information is not available yet, no? So it would be a an API addition as well?\n\nYes, it would be an API addition.\n\n> >> * dependencies:\n> >> - https://patchwork.libcamera.org/project/libcamera/list/?series=5756\n> >> - https://patchwork.libcamera.org/patch/26038/\n> >>\n> >> ---\n> >> changes in v2:\n> >> * use existing containers\n> >> * manual rootfs workflow\n> >>\n> >> v1: https://patchwork.libcamera.org/cover/25839/\n> >> ---\n> >> Barnabás Pőcze (5):\n> >> Install `fpm` in the debian 13 container\n> >> Add job to build deb package for libcamera\n> >> Add job to run lc-compliance via lava\n> >> Guard hardware testing jobs\n> >> Add description about debian rootfs setup for testing\n> >>\n> >> .gitlab-ci/on-device-testing/lava-debix-a.yml | 40 ++++++++\n> >> .gitlab-ci/setup-container.sh | 6 ++\n> >> .../debian-rootfs/build-debian-rootfs.sh | 62 ++++++++++++\n> >> containers/debian-rootfs/build.sh | 9 ++\n> >> .../overlay/opt/test-libcamera.sh | 18 ++++\n> >> doc/debian-rootfs.rst | 47 +++++++++\n> >> gitlab-ci.yml | 95 ++++++++++++++++++-\n> >> 7 files changed, 276 insertions(+), 1 deletion(-)\n> >> create mode 100644 .gitlab-ci/on-device-testing/lava-debix-a.yml\n> >> create mode 100755 containers/debian-rootfs/build-debian-rootfs.sh\n> >> create mode 100755 containers/debian-rootfs/build.sh\n> >> create mode 100755 containers/debian-rootfs/overlay/opt/test-libcamera.sh\n> >> create mode 100644 doc/debian-rootfs.rst","headers":{"Return-Path":"","X-Original-To":"parsemail@patchwork.libcamera.org","Delivered-To":"parsemail@patchwork.libcamera.org","Received":["from lancelot.ideasonboard.com (lancelot.ideasonboard.com\n\t[92.243.16.209])\n\tby patchwork.libcamera.org (Postfix) with ESMTPS id AA6CCC3220\n\tfor ;\n\tMon, 9 Feb 2026 11:03:12 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id 629AF620D6;\n\tMon, 9 Feb 2026 12:03:12 +0100 (CET)","from perceval.ideasonboard.com (perceval.ideasonboard.com\n\t[IPv6:2001:4b98:dc2:55:216:3eff:fef7:d647])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id 32B1F61FA0\n\tfor ;\n\tMon, 9 Feb 2026 12:03:11 +0100 (CET)","from killaraus.ideasonboard.com\n\t(2001-14ba-703d-e500--2a1.rev.dnainternet.fi\n\t[IPv6:2001:14ba:703d:e500::2a1])\n\tby perceval.ideasonboard.com (Postfix) with UTF8SMTPSA id 81880454;\n\tMon, 9 Feb 2026 12:02:25 +0100 (CET)"],"Authentication-Results":"lancelot.ideasonboard.com; dkim=pass (1024-bit key;\n\tunprotected) header.d=ideasonboard.com header.i=@ideasonboard.com\n\theader.b=\"Lf1ADo0l\"; dkim-atps=neutral","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com;\n\ts=mail; t=1770634945;\n\tbh=sFpisGNHWJdtbmoqjd1fNDvLLuifOTrhwomjRxUfsQE=;\n\th=Date:From:To:Cc:Subject:References:In-Reply-To:From;\n\tb=Lf1ADo0loYTzTv9lcFVyDbarV0pmcPubOb5Wd1aiHX9uZM2gDw2wYxXVvYwc+Jf/u\n\tiSNEax7fuJ1ZosrqRgY6J/yH0Q1M8ofeMojXLNCF3+KgBiSVrwstkahWMjMPp9ZAgL\n\tTX1sw+y1Zfua0VfAgSKgLTrHbz2H2wahg26ESjaY=","Date":"Mon, 9 Feb 2026 13:03:09 +0200","From":"Laurent Pinchart ","To":"=?utf-8?q?Barnab=C3=A1s_P=C5=91cze?= ","Cc":"libcamera-devel@lists.libcamera.org","Subject":"Re: [libcamera-ci] [RFC PATCH v2 0/5] on-device-testing proof of\n\tconcept","Message-ID":"<20260209110309.GE2302514@killaraus.ideasonboard.com>","References":"<20260130160254.1770742-1-barnabas.pocze@ideasonboard.com>\n\t<20260205132827.GL156228@killaraus>\n\t<2062b812-4127-42fa-ab35-8749605ce038@ideasonboard.com>","MIME-Version":"1.0","Content-Type":"text/plain; charset=utf-8","Content-Disposition":"inline","Content-Transfer-Encoding":"8bit","In-Reply-To":"<2062b812-4127-42fa-ab35-8749605ce038@ideasonboard.com>","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"","List-Unsubscribe":",\n\t","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n\t","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" "}}]