On 2025-05-29 05:47, Jochen Sprickerhof wrote:
> sbuild only calls autopkgtest, so reassigning to autopkgtest accordingly.
I think there are two distinct cases to consider here:
(1) sbuild's unshare backend for build-time stuff, distinct from
the autopkgtest backend (right?)
(2) sbuild c
Am 29. Mai 2025 10:30:37 OESZ schrieb picca :
>Jochen Sprickerhof writes:
>> Why in the unshare backend?
>
>because it is the sbuild prefered backend now. I try to stick to the
>sbuild default so when I run sbuild it use unshare with autopkgtest.
That is only because it needs no setup. We will
Jochen Sprickerhof writes:
> Control: -1 reassign autopkgtest
>
> Hi Frederic,
Hello Joshen
>>so the idea is to implement OpenCL test on real hardware.
>>
>>In order to run these test the hardware should be available in the unshare
>>backend.
>
> Why in the unshare backend?
because it is the
Control: -1 reassign autopkgtest
Hi Frederic,
* Picca Frédéric-Emmanuel [2025-05-28 13:03]:
Hello, we are trying to run autopkgtest with a computer with and AMD GPU card.
sbuild only calls autopkgtest, so reassigning to autopkgtest
accordingly.
so the idea is to implement OpenCL test on
Package: sbuild
Version: 0.89.2
Severity: normal
Dear Maintainer,
Hello, we are trying to run autopkgtest with a computer with and AMD GPU card.
so the idea is to implement OpenCL test on real hardware.
In order to run these test the hardware should be available in the unshare
backend.
for th
5 matches
Mail list logo
