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

Bug#908108: marked as done (libkf5mailimporter: flaky autopkgtest different failures in different runs)

Your message dated Mon, 04 Feb 2019 15:47:50 +0100
with message-id <1716317.9l2z9TSRL1@tuxin>
and subject line Disabled autopkgtests
has caused the Debian Bug report #908108,
regarding libkf5mailimporter: flaky autopkgtest different failures in different runs
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 owner@bugs.debian.org
immediately.)


-- 
908108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908108
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libkf5mailimporter
Version: 4:17.12.3-1
Severity: important
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
Usertags: flaky

Dear maintainers,

With a recent upload of glibc the autopkgtest of libkf5mailimporter
started to fail when run in testing. The test was retried and failed
again, but this time on a different error. The third time it passed. I
copied the output below.

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug). If this flakiness can't really be fixed,
consider setting the "flaky" restriction (see
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst).

Recent discussion of gating migration by autopkgtests on debian-devel
[1] noted that if this is going to work, and in particular if we are
going to *block* migration when it causes autopkgtest regressions rather
than merely delaying it, intermittent autopkgtest failures are likely to
have to be considered RC due to their impact on the tested package's
dependencies; for now I've filed it as important.

Paul

[1] https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkf5mailimporter/944753/log.gz

96% tests passed, 1 tests failed out of 25

Total Test time (real) =   1.24 sec

The following tests FAILED:
	  4 - mailimporter-filtersylpheedtest (Failed)

https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkf5mailimporter/939739/log.gz

96% tests passed, 1 tests failed out of 25

Total Test time (real) =   1.39 sec

The following tests FAILED:
	  2 - mailimporter-filtericedovetest (Failed)

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 4:18.08.3-1

As autopkgtests in KDEPIM are not in a good shape, the got disabled completely 
for the moment.

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: