[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Query on Package rasdaemon Transition to Testing: QEMU vs. LXC



Hi Paul,

Thanks for the tip! I gave "isolation-machine" a try and have a
further question: does Debian CI accept exit code 8 when migrating a
package from Sid to Testing?

In my case, by using "isolation-machine", I will get exit code 8. I
also consider to use "flaky" but it will return 2 accordingly[1].
"flaky" is inappropriate to my test as my test is not supposedly to
fail in expected env.

I will move my package forward if exit code 8 is acceptable to Debian
CI when migrating a package from Sid to Testing.


[1] EXIT STATUS of autopkgtest (quote from
https://manpages.debian.org/testing/autopkgtest/autopkgtest.1.en.html
)

0 all tests passed
2 at least one test was skipped (or at least one flaky test failed)
4 at least one test failed
6 at least one test failed and at least one test skipped
8 no tests in this package, or all non-superficial tests were skipped
12 erroneous package
14 erroneous package and at least one test skipped
16 testbed failure
20 other unexpected failures including bad usage


Kind regards,
Tai


On Mon, Jan 1, 2024 at 7:25 AM Paul Gevers <elbrus@debian.org> wrote:
>
> Hi Taihsiang,
>
> On 31-12-2023 23:00, Taihsiang Ho (tai271828) wrote:
> > Despite reviewing several debci documents, I haven't found clear
> > guidance on whether using qemu is acceptable in such cases. My
> > references include:
> >
> >      https://wiki.debian.org/debci
> >      https://wiki.debian.org/debci/DistributedSpec
> >      https://wiki.debian.org/ContinuousIntegration/DebianSetup
>
> The canonical information source is the autopkgtest spec:
> https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
>
> """
> isolation-machine
>
>      The test wants to interact with the kernel, reboot the machine, or
> other things which fail in a simple schroot and even a container. Those
> tests need to be run in their own machine/VM (e. g.
> autopkgtest-virt-qemu or autopkgtest-virt-null). When running the test
> in a virtualization server which does not provide this it will be skipped.
> """
>
> > Could someone with more expertise or relevant experience provide
> > advice on the best approach for rasdaemon in this context?
>
> My advice is, add an isolation-machine restriction.
>
> Paul


Reply to: