Bug#1020833: openmsx-catapult: flaky autopkgtest: dogtail.tree.SearchError: child of [desktop frame | main]: "openmsx-catapult" application
Source: openmsx-catapult
Version: 18.0-1
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
Usertags: flaky
The autopkgtest for openmsx-catapult seems to be intermittently failing
like this:
> Warning: AT-SPI's desktop is visible but it has no children. Are you running any AT-SPI-aware applications?
> Clicking on [check box | Check for working hardware configurations after closing this dialog]
> Mouse button 1 click at (236.5,79.0)
> Clicking on [push button | OK]
> Mouse button 1 click at (330.5,129.0)
> Clicking on [menu | File]
> Mouse button 1 click at (19.5,12.5)
> Clicking on [menu item | Test MSX Hardware]
> Mouse button 1 click at (117.5,37.5)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 3)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 4)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 5)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 6)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 7)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 8)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 9)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 10)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 11)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 12)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 13)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 14)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 15)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 16)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 17)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 18)
> searching for child of [desktop frame | main]: "openmsx-catapult" application (attempt 19)
> Traceback (most recent call last):
> File "/tmp/autopkgtest-lxc.nboffbe8/downtmp/build.7HA/src/debian/tests/run.py", line 83, in <module>
> test_detect()
> File "/tmp/autopkgtest-lxc.nboffbe8/downtmp/build.7HA/src/debian/tests/run.py", line 56, in test_detect
> done = find('Done', idx = 1)
> File "/tmp/autopkgtest-lxc.nboffbe8/downtmp/build.7HA/src/debian/tests/run.py", line 21, in find
> window = tree.root.application('openmsx-catapult')
> File "/usr/lib/python3/dist-packages/dogtail/tree.py", line 1173, in application
> return root.findChild(predicate.IsAnApplicationNamed(appName), recursive=False, retry=retry, showingOnly=False)
> File "/usr/lib/python3/dist-packages/dogtail/tree.py", line 939, in findChild
> raise SearchError(describeSearch(self, pred, recursive, debugName))
> dogtail.tree.SearchError: child of [desktop frame | main]: "openmsx-catapult" application
for example in
<https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmsx-catapult/26226670/log.gz>
and
<https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmsx-catapult/26330175/log.gz>.
When testing a proposed update to a package it depends on (such as
glib2.0 and xorg-server in those logs), a test failure like this is
assumed to be a regression in the updated package, which can delay or
prevent testing migration.
Please look into whether this test can be made reliable, or if it cannot,
mark the test with "Restrictions: flaky" so that it doesn't disrupt other
packages.
Thanks,
smcv
Reply to: