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

Bug#902850: marked as done (plasma-framework: flaky autopkgtest: DialogNativeTest::position() Compared values are not the same)

Your message dated Sun, 10 May 2020 21:07:17 +0200
with message-id <ea8cb5b1-65ea-a194-e00d-02ab80e00ee8@debian.org>
and subject line Re: plasma-framework: flaky autopkgtest: DialogNativeTest::position() Compared values are not the same
has caused the Debian Bug report #902850,
regarding plasma-framework: flaky autopkgtest: DialogNativeTest::position() Compared values are not the same
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.)


-- 
902850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902850
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: plasma-framework
Version: 5.46.0-1
Severity: important
User: debian-ci@lists.debian.org
Usertags: flaky

While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times²³ without apparent changes and passed
later again. I think all cases had the error that I copied below. The
last regression was involved in delaying the migration of xorg-server.

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).

Recent discussion of gating migration by autopkgtests on debian-devel⁶
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

¹ https://ci.debian.net/packages/p/plasma-framework/testing/amd64/
²
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/plasma-framework/479454/log.gz
³
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/plasma-framework/386329/log.gz
⁴
https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-framework/541592/log.gz
⁵ https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-framework/541592/log.gz

11/14 Test #11: dialognativetest .................***Failed    0.41 sec
********* Start testing of DialogNativeTest *********
Config: Using QtTest library 5.10.1, Qt 5.10.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)
QWARN  : DialogNativeTest::initTestCase() kf5.kcoreaddons.kdirwatch:
Cannot watch QRC-like path ":/icons/hicolor/index.theme"
PASS   : DialogNativeTest::initTestCase()
PASS   : DialogNativeTest::size()
FAIL!  : DialogNativeTest::position() Compared values are not the same
   Actual   (m_dialog->y()): 0
   Expected (49)           : 49
   Loc:
[/tmp/autopkgtest-lxc.a5u4pbl8/downtmp/build.YAX/src/autotests/dialognativetest.cpp(96)]
PASS   : DialogNativeTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 355ms
********* Finished testing of DialogNativeTest *********

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 5.62.0-2

On Mon, 2 Jul 2018 11:40:06 +0200 Paul Gevers <elbrus@debian.org> wrote:
> While inspecting regressions in autopkgtest results¹, I noticed that
> your package failed multiple times²³ without apparent changes and passed
> later again. I think all cases had the error that I copied below. The
> last regression was involved in delaying the migration of xorg-server.
> 
> 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).

This seems to have been fixed a while ago.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: