Your message dated Mon, 3 Feb 2025 11:04:09 -0300
with message-id <Z6DM2fYKSyWiq6Rg@voleno>
and subject line Re: Bug#1091861: closed by Debian FTP Masters
<[email protected]> (reply to Santiago Ruano Rincón
<[email protected]>) (Bug#1091861: fixed in pytango 10.0.0-3)
has caused the Debian Bug report #1091861,
regarding pytango: flaky autopkgtest: Timeout, waiting for event
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.)
--
1091861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091861
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pytango
Version: 10.0.0-2
Severity: serious
User: [email protected]
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package because it
was blocking gcc-14. I noticed that it regularly fails.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
https://ci.debian.net/packages/p/pytango/testing/amd64/55919644/
224s =================================== FAILURES
===================================
224s _________________ test_push_event_with_event_callback[Asyncio]
_________________
224s event_device = EventDevice(test/nodb/eventdevice)
224s
224s def test_push_event_with_event_callback(event_device):
224s string = StringIO()
224s ec = EventCallback(fd=string)
224s
224s if event_device.get_green_mode() == GreenMode.Asyncio:
224s with pytest.warns(DeprecationWarning):
224s > __test_push_event_with_timestamp(event_device, ec,
string)
224s
224s tests/test_event.py:505:
224s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
224s
224s event_device = EventDevice(test/nodb/eventdevice)
224s cb = <tango.utils.EventCallback object at 0x7f70876d7620>
224s string = <_io.StringIO object at 0x7f708799fb80>
224s
224s def __test_push_event_with_timestamp(event_device, cb, string):
224s # to reduce tests amount here we test only change event
224s eid = event_device.subscribe_event("attr",
EventType.CHANGE_EVENT, cb, wait=True)
224s # trigger an event
224s event_device.command_inout("send_events",
EventType.CHANGE_EVENT, wait=True)
224s # wait for tango event
224s for retry_count in range(MAX_RETRIES):
224s event_device.read_attribute("state", wait=True)
224s if len(cb.get_events()) > 5:
224s break
224s time.sleep(DELAY_PER_RETRY)
224s if retry_count + 1 >= MAX_RETRIES:
224s timeout_seconds = retry_count * DELAY_PER_RETRY
224s > pytest.fail(
224s f"Timeout, waiting for event, after
{timeout_seconds}sec over {MAX_RETRIES} retries. "
224s f"Occasionally happens, probably due to CI test
runtime environment"
224s )
224s E Failed: Timeout, waiting for event, after
39.800000000000004sec over 200 retries. Occasionally happens, probably
due to CI test runtime environment
224s
224s tests/test_event.py:473: Failed
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 10.0.0-4
Hello Paul,
El 22/01/25 a las 19:49, Paul Gevers escribió:
> Hi Santiago,
>
> Thanks for working on a fix, ...
>
> On 22-01-2025 14:27, Santiago Ruano Rincón wrote:
> > Control: reopen -1
> >
> > At least, one more test if failing (triggered by migration-reference/0):
> > https://ci.debian.net/packages/p/pytango/unstable/amd64/56790990/
> > so this will still block the gcc-14 migration.
>
> but let remove this confusion. pytango was blocking the migration at the
> moment I filed the bug, but the bug being about flakiness, I added a hint to
> let gcc-14 migrate. pytango wasn't the only package blocking gcc-14 due to
> flaky test by the way. Also glibc nearly always needs help as do some other
> packages that trigger a lot of tests.
>
> Paul
Thank you for clarifying!
And I am also closing this bug (again). AFAICS, the 10.0.0-4 changes
made the tests more reliable.
Thank a lot for your time.
-- Santiago
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 24 Jan 2025 18:08:09 -0300
Source: pytango
Architecture: source
Version: 10.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Santiago Ruano Rincón <[email protected]>
Changes:
pytango (10.0.0-4) unstable; urgency=medium
.
* Team upload.
* Disable some more tests that regularly fail
Checksums-Sha1:
8b954202686c5984edb9d0a2ad093ad57a7b2d07 2679 pytango_10.0.0-4.dsc
aa7dc2bcb21cbf629d5dd4fa8c0db9155dd17712 13008 pytango_10.0.0-4.debian.tar.xz
0b67d1646680084433aca91d6489abd559c2d6df 14082 pytango_10.0.0-4_amd64.buildinfo
Checksums-Sha256:
14d8d9a1c6adf1b432f2108a91e52fc6763e7a5df2a087a28f4896848f56f336 2679
pytango_10.0.0-4.dsc
987d5f33e0fd3f86f15eabc5b90350cddba81e67efc2754ff3de9fd3c5a712d1 13008
pytango_10.0.0-4.debian.tar.xz
5ed43acd224fc37b4fc4a060e3ac35795406b68f156a9b2a33911d8dc822428d 14082
pytango_10.0.0-4_amd64.buildinfo
Files:
231336dc158eb2cc71b3be1b86020d95 2679 science optional pytango_10.0.0-4.dsc
4f1749347d2b2265bccf20eecbc34b12 13008 science optional
pytango_10.0.0-4.debian.tar.xz
78790b9f38c718f38d503339639c933a 14082 science optional
pytango_10.0.0-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIwEARYKADQWIQR+lHTq7mkJOyB6t2Un3j1FEEiG7wUCZ5QHHhYcc2FudGlhZ29A
ZnJlZXhpYW4uY29tAAoJECfePUUQSIbvf1sBAK3kxmYtzCJ68UxTDhEqoF5fHlsj
hPjgKLncdClnKSMDAQD0VmXqRzsw8YSxUVwlETm1h1RlPWFvEy3nfdERF7CdAg==
=io0M
-----END PGP SIGNATURE-----
signature.asc
Description: PGP signature
--- End Message ---
