Source: autopkgtest
Version: 5.13.1
Severity: normal

Hi,

I have some problems understanding the breaks-testbed restriction:

  breaks-testbed
    The test, when run, is liable to break the testbed system. This
    includes causing data loss, causing services that the machine is
    running to malfunction, or permanently disabling services; it does
    not include causing services on the machine to temporarily fail.

AIUI the testbed system is a throwaway chroot/container/virtual machine/...
So how can breakage (e.g. rm /bin/ls) be persistent? Or is it possible
to run subsequent tests in the same testbed instance?
Or does that mean the test can affect the host system? (E.g. from a
chroot with root access killing all processes with even PIDs, including
processes on the host.)
BTW, what does "machine" denote in the quoted paragraph?

Or am I on the wrong track here?


Andreas

Reply via email to