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

Bug#932463: suricata: autopkgtest fails due to (intermittent) download failure

Source: suricata
Version: 1:4.1.4-2
Severity: important
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
Usertags: flaky

Dear maintainers,

Your package has an autopkgtest, great. However, today it was reporting
a regression in systemd, because it failed to connect to some website.
Please consider retrying the connection and marking that particular test
as skippable and exit with exit code 77 in case the website can't be
reached at all. This will prevent this issue in the future.

    The test might need to be skipped for reasons that cannot be
    described by an existing restriction such as isolation-machine or
    breaks-testbed, but must instead be detected at runtime. If the
    test exits with status 77 (a convention borrowed from Automake), it
    will be treated as though it had been skipped. If it exits with any
    other status, its success or failure will be derived from the exit
    status and stderr as usual. Test authors must be careful to ensure
    that ``skippable`` tests never exit with status 77 for reasons that
    should be treated as a failure.



autopkgtest [22:15:56]: test command11: [-----------------------
Loading /etc/suricata/suricata-oinkmaster.conf
Downloading file from

/usr/sbin/oinkmaster: Error: could not download from
500 Can't connect to rules.emergingthreats.net:443 (Connection timed out)

Oink, oink. Exiting...
autopkgtest [22:20:17]: test command11: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: