Your message dated Thu, 22 Jun 2023 18:43:44 +0200
with message-id <[email protected]>
and subject line Re: pango1.0: flaky autopkgtest:
pango_layout_set_markup_with_accel: Error on line 2 char 28
has caused the Debian Bug report #904452,
regarding pango1.0: flaky autopkgtest: pango_layout_set_markup_with_accel:
Error on line 2 char 28
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.)
--
904452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904452
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pango1.0
Version: 1.42.1-1
Severity: important
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: flaky
While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times² without apparent changes and passed
later again. Recent cases had the error that I copied below, I haven't
checked older history. The last regression was involved in delaying
the migration of fribidi.
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). Note that we recently added the "flaky"
restriction to autopkgtest. If you can't really fix the test, but still
want it run, you can mark it as not suitable for gating.
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 and time unaware people are going to waist on looking into
the issue; for now I've filed it as important.
Paul
¹ https://ci.debian.net/packages/p/pango1.0
²
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/610952/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/662717/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pango1.0/331745/log.gz
³ https://lists.debian.org/debian-devel/2018/05/msg00061.html
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/610952/log.gz
/layout/valid-1.markup:
(/usr/lib/pango1.0/installed-tests/pango/test-layout:1983):
Pango-WARNING **: 09:16:42.416: pango_layout_set_markup_with_accel:
Error on line 2 char 28: Invalid UTF-8 encoded text in name - not valid
'\xf0U<'
FAIL: pango/test-layout.test (Child process killed by signal 5)
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/662717/log.gz
/layout/valid-1.markup:
(/usr/lib/pango1.0/installed-tests/pango/test-layout:1987):
Pango-WARNING **: 09:15:23.974: pango_layout_set_markup_with_accel:
Error on line 2 char 28: 'VU<' is not a valid name: '<'
FAIL: pango/test-layout.test (Child process killed by signal 5)
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
On Tue, 24 Jul 2018 15:36:51 +0200 Paul Gevers <[email protected]> wrote:
While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times² without apparent changes and passed
later again. Recent cases had the error that I copied below, I haven't
checked older history.
This seems to have improved over time. Let's close this bug. (I was
about to raise it's severity as we nowadays consider this RC).
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
