Your message dated Tue, 2 Jul 2019 20:23:04 +0200
with message-id <[email protected]>
and subject line Re: syslog-ng: upgrade autopkgtest fails in Debian migration
testing setup
has caused the Debian Bug report #900470,
regarding syslog-ng: upgrade autopkgtest fails in Debian migration testing setup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
900470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900470
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: syslog-ng
Version: 3.13.2-4
User: [email protected]
Usertags: issue
While inspecting regressions in autopkgtest results¹, I noticed that
your package syslog-ng passes in unstable and testing, except when it is
run in testing with an other package from unstable. Most (if not all)
failures are in the upgrade test. I believe that test should either be
disabled, or made compatible with the migration testing setup that we
use in Debian. Currently I have added a britney hint² to ignore all
results for syslog-ng as it would delay all migrations where syslog-ng
is tested, but the autopkgtest should be fixed instead.
Please contact me if you need more information on the Debian setup for
testing unstable-to-testing migration.
Paul
PS: I haven't raised the severity of this bug yet, but I'll inform the
release team about it and I expect they will raise it.
¹ https://ci.debian.net/packages/s/syslog-ng/testing/amd64/
² https://release.debian.org/britney/hints/elbrus
https://ci.debian.net/data/autopkgtest/testing/amd64/s/syslog-ng/326414/log.gz
autopkgtest [07:36:33]: test upgrade: [-----------------------
Reading package lists...
Building dependency tree...
Reading state information...
autopkgtest [07:36:33]: test upgrade: -----------------------]
autopkgtest [07:36:34]: test upgrade: - - - - - - - - - - results - - -
- - - - - - -
upgrade FAIL non-zero exit status 100
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.19.1-3
On Mon, 9 Jul 2018 17:29:16 +0200 Paul Gevers <[email protected]> wrote:
> Hi,
>
> On Thu, 31 May 2018 10:40:08 +0200 Paul Gevers <[email protected]> wrote:
> > While inspecting regressions in autopkgtest results¹, I noticed that
> > your package syslog-ng passes in unstable and testing, except when it is
> > run in testing with an other package from unstable. Most (if not all)
> > failures are in the upgrade test. I believe that test should either be
> > disabled, or made compatible with the migration testing setup that we
> > use in Debian. Currently I have added a britney hint² to ignore all
> > results for syslog-ng as it would delay all migrations where syslog-ng
> > is tested, but the autopkgtest should be fixed instead.
> >
> > Please contact me if you need more information on the Debian setup for
> > testing unstable-to-testing migration.
>
> The autopkgtest specification¹ now a new restriction "flaky" which you
> could use to tag this test as not suitable for gating. That way you can
> keep the test for manual checking in unstable, but it will not hinder
> any migrations.
Seems like this got fixed. I am removing the badtest hint.
syslog-ng (3.19.1-3) unstable; urgency=medium
* Correct syslog-ng-mod-examples description (closes: #920846).
* Disable pacctformat building on non-Linux systems.
* Disable buggy upgrade self-test.
-- Laszlo Boszormenyi (GCS) <[email protected]> Mon, 04 Feb 2019 18:47:26
+0000
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
