<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">The backport of arm64 support to FPC
3.0.x has been found to be somewhat shaky in the past.<br>
<br>
Given that fpc 3.2.x has now reached the release-candidate stage
and I would hope it will be available in time for the bullseye
freeze I would suggest we mark this is flaky for the time being
and than take another look when fpc 3.2 is in Debian.<br>
<br>
On 17/04/2020 09:31, Simon McVittie wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20200417083101.GA414167@espresso.pseudorandom.co.uk">
<pre class="moz-quote-pre" wrap="">Source: lazarus
Version: 2.0.6+dfsg-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: <a class="moz-txt-link-abbreviated" href="mailto:debian-ci@lists.debian.org">debian-ci@lists.debian.org</a>
User: <a class="moz-txt-link-abbreviated" href="mailto:debian-ci@lists.debian.org">debian-ci@lists.debian.org</a>
Usertags: flaky
The lazarus autopkgtest seems to pass reliably on amd64, but fails with an
access violation (NULL pointer dereference?) or an "Invalid file handle"
error about half the time on arm64.
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. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.
Because this test seems to be reliable on amd64, another option might be
to mark the test with the "skippable" restriction, and make it exit 77
if there's a crash on arm64 (but I'm not sure how that interacts with
detecting test failures via output on stderr).
<a class="moz-txt-link-freetext" href="https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/5007737/log.gz">https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/5007737/log.gz</a>
is a typical example, which shows both failure modes (full log attached).
The stderr is:
autopkgtest [03:54:00]: test build-lpk-lpi: - - - - - - - - - - stderr - - - - - - - - - -
An unhandled exception occurred at $0000AAAAE9A147A0:
EInOutError: Invalid file handle
$0000AAAAE9A147A0
$0000AAAAE9B17D8C
$0000AAAAE9A0B658
$0000AAAAE9A6E714
$0000AAAAE9B15E70
$0000AAAAEA03E464
$0000AAAAE9B247F4
$0000AAAAE9A0B658
$0000AAAAE9B16094
$0000AAAAE9B163A4
$0000AAAAE9B82690
$0000AAAAE9B825A8
$0000AAAAE9A0B658
$0000AAAAE9C68A48
$0000AAAAE9A2F454
$0000AAAAE9A2F3E0
$0000AAAAE9A2F008
An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation
$0000000000000000
An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation
$0000000000000000
Some other recent test failures:
<a class="moz-txt-link-freetext" href="https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/4879692/log.gz">https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/4879692/log.gz</a>
<a class="moz-txt-link-freetext" href="https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/4630413/log.gz">https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/4630413/log.gz</a>
<a class="moz-txt-link-freetext" href="https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/4381462/log.gz">https://ci.debian.net/data/autopkgtest/testing/arm64/l/lazarus/4381462/log.gz</a>
Thanks,
smcv
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Pkg-pascal-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pkg-pascal-devel@alioth-lists.debian.net">Pkg-pascal-devel@alioth-lists.debian.net</a>
<a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel</a></pre>
</blockquote>
<p><br>
</p>
</body>
</html>