Your message dated Sat, 3 Aug 2024 12:38:01 +0200
with message-id <3f55bc96-6607-451e-a6b4-4d41184b9...@debian.org>
and subject line Re: pytango: failed to build from source on arm64: test timeout
has caused the Debian Bug report #1076830,
regarding pytango: failed to build from source on arm64: test timeout
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 ow...@bugs.debian.org
immediately.)
--
1076830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytango
Version: 9.5.0-4
Severity: serious
Tags: ftbfs
Justification: FTBFS
Hi,
The latest upload of pytango failed to build on the arm64 buildd. Seems
like the build is flaky as the error is about a timeout during the test.
Paul
=================================== FAILURES
===================================
___________________ test_subscribe_data_ready_event[Asyncio]
___________________
event_device = EventDevice(test/nodb/eventdevice)
def test_subscribe_data_ready_event(event_device):
results_data_ready_event = []
def callback_data_ready(evt):
results_data_ready_event.append(evt.ctr)
# Subscribe to data ready event
eid_data_ready = event_device.subscribe_event(
"attr", EventType.DATA_READY_EVENT, callback_data_ready,
wait=True
)
assert eid_data_ready == 1
# Trigger an event
event_device.command_inout("send_data_ready_event", wait=True)
# Wait for tango event
for retry_count in range(MAX_RETRIES):
event_device.read_attribute("state", wait=True)
if len(results_data_ready_event):
break
time.sleep(DELAY_PER_RETRY)
if retry_count + 1 >= MAX_RETRIES:
timeout_seconds = retry_count * DELAY_PER_RETRY
> pytest.fail(
f"Timeout, waiting for event, after
{timeout_seconds}sec over {MAX_RETRIES} retries. Occasionally happens,
probably due to CI test runtime environment"
)
E Failed: Timeout, waiting for event, after
9.950000000000001sec over 200 retries. Occasionally happens, probably
due to CI test runtime environment
tests/test_event.py:151: Failed
---------------------------- Captured stdout setup
-----------------------------
Ready to accept request
---------------------------- Captured stderr setup
-----------------------------
Can't create notifd event supplier. Notifd event not available
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.9.8-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 9.5.0-5
The increased timeout fixed the build
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
