MR: debian/devscripts!20


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

This is particularly noticeable in the autopkgtest excuses, which use
<span> tags to color the output.

    $ grep-excuses neovim
    neovim (0.2.2-3 to 0.3.0-2)
        Maintainer: Debian Vim Maintainers
        7 days old (needed 5 days)
        missing build on ppc64el: neovim (from 0.2.2-3)
        old binaries left on all: neovim-runtime (from 0.2.2-3) (but ignoring cruft, so nevermind)
        Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neovim.html


        autopkgtest for ruby-neovim/0.7.1-1: amd64: <span style="background:#87d96c">Pass</span>

Signed-off-by: James McCoy <jamessan@debian.org>

MR: debian/devscripts!19


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Include all the arguments the user originally passed, which they
probably want to pass again.

Closes: #895279

Simon McVittie authored Apr 09, 2018 and Osamu Aoki committed Jun 16, 2018

An absolute path for USCAN_DESTDIR was handled everywhere else, but in
git mode uscan blindly appended it to $curdir, resulting in paths
like "/home/smcv/src/debian/ioquake3//home/smcv/tmp/build-area..."
when used.

Signed-off-by: Simon McVittie <smcv@debian.org>

Signed-off-by: Osamu Aoki <osamu@debian.org>

MR: debian/devscripts!18


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Simon McVittie <smcv@debian.org>

A skippable test probes for some resource that it needs, which might
be something too complicated to express in Restrictions (for example
"/var/tmp supports extended attributes" for flatpak and ostree). If
that resource is not found, the test exits 77 (a convention borrowed
from Automake) and the test runner treats it as though it had been
skipped based on its Restrictions.

As suggested in <https://bugs.debian.org/851558>
and implemented for autopkgtest in
<ci-team/autopkgtest!20

>.

Signed-off-by: Simon McVittie <smcv@debian.org>

Flaky tests are intended to pass, but are known to be unreliable,
subject to intermittent failures or otherwise unsuitable for gating CI.
To determine when a flaky test has become reliable, it is useful to
run it in realistic infrastructure for a while and gather data.

If a flaky test passes it is reported in the same way as any other
passing test, but if a flaky test fails (for any reason) it is
reported as flaky instead of as a failure.

As suggested in <https://bugs.debian.org/851558>
and implemented for autopkgtest in
<ci-team/autopkgtest!19

>.

Signed-off-by: Simon McVittie <smcv@debian.org>

This is useless now, but will become useful when TestOptions contains
more options.

Signed-off-by: Simon McVittie <smcv@debian.org>

Signed-off-by: Simon McVittie <smcv@debian.org>

MR: debian/devscripts!17


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

If you have DEBDIFF_SHOW_MOVED=yes in ~/.devscripts (as I do) then
this test would fail, because the message printed is not the same
as expected.

Signed-off-by: Simon McVittie <smcv@debian.org>

MR: debian/devscripts!16


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Closes: #900963
Signed-off-by: Mattia Rizzolo <mattia@debian.org>

this avoids perl warnings in some corner cases

Thanks: nthykier for mentioning the potential issue
Signed-off-by: Mattia Rizzolo <mattia@debian.org>

debchange: Replace implicit boolean evaluation of a Dpkg::Version object by Dpkg::Version::is_valid().

Closes: #900703
Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Previously modified files would only be printed with --verbose turned on.

This change allows wrap-and-sort to be less verbose with --dry-run on.

MR: debian/devscripts!15


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

This bug was introduced by commit 2ef682e5.

Tests are now proper objects instead of just strings, we can no longer
compare them directly to the names of the tests passed in the command
line.

This makes the verbose output mode even more clear, with the complete
output of the test between dashed lines, e.g.

----------------------------------------------------------------------
testname
----------------------------------------------------------------------
O: ...
O: ...
O: ... output of the test ...
O: ...
O: ...
----------------------------------------------------------------------
testname: PASS

i.e. only leave a temporary directory behind with build artifacts for
inspection if the package is not reproducible.

MR: debian/devscripts!13


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Thanks: terceiro for noticying I forgot it…
Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Closes: #898450
Signed-off-by: Mattia Rizzolo <mattia@debian.org>

test_uscan_ftp: Handle errors coming from the ftpserver.py subprocess to avoid possible endless loops

Closes: #898370
Signed-off-by: Mattia Rizzolo <mattia@debian.org>

This involves extracting the logic for running a test into a TestCommand
class, which can handle any command, and a Test subclass, which handles
the special case of a script under debian/tests

Closes: #781963

The end of those lines is a mess, so let's simplify. Also, sort the list
to make it more readable and provide a better indication of where to
insert new items.

- Remove "hourglass" progress indicator
- display output of commands in verbose output
- improve organization of verbose output

Closes: #748852