[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#956956: lazarus: flaky autopkgtest on arm64: EAccessViolation, EInOutError

Source: lazarus
Version: 2.0.6+dfsg-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
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).

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

An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation

An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation

Some other recent test failures:


Attachment: log.gz
Description: application/gzip

Reply to: