v8.1.0-1799-g38ee0a7dfb: FAIL: 2 regressions: 8 progressions

Description

Commit: https://gitlab.com/qemu-project/qemu/commit/38ee0a7dfb4b15407678df26448e4a18fd9a51d4
commit v8.1.0-1799-g38ee0a7dfb
Author: Richard Henderson <richard.henderson@linaro.org>
Date: Sat Sep 30 12:05:11 2023 -0700

linux-user: Remap guest SIGABRT

Distinguish host SIGABRT from guest SIGABRT by mapping
the guest signal onto one of the host RT signals.

This prevents a cycle by which a host assertion failure
is caught and handled by host_signal_handler, queued for
... 6 lines of the commit log omitted.

Latest data: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/sha1/38ee0a7dfb4b15407678df26448e4a18fd9a51d4/jira/yaml

Activity

Show:

Richard Henderson February 6, 2024 at 3:17 AM

How odd. The test is 100% stable for me, on multiple host architectures.

Maxim Kuvyrkov February 5, 2024 at 7:54 AM

Thanks, .

As a final note, 30_threads/thread/native_handle/cancel.cc test now has flaky behavior when run on QEMU. It sometimes FAILs and sometimes PASSes.

Let me know if you are interested investigating this.

See testsuite re-run logs

  1. https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1249/artifact/artifacts/00-sumfiles/libstdc++.log.0.xz and

  2. https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1249/artifact/artifacts/00-sumfiles/libstdc++.log.1.xz

Richard Henderson February 3, 2024 at 10:26 PM

VDSO fix merged as 6400be014f80.

Richard Henderson February 3, 2024 at 7:16 AM

No. There were two bugs:

  • 38ee0a7d (linux-user: Remap guest SIGABRT), fixed by 02d9f5b6 (linux-user: Fix guest signal remapping after adjusting SIGABRT)

  • ee95fae0 (linux-user/aarch64: Add vdso), fixed by yesterday’s patch.

The two breakages did not overlap.

Christophe Lyon February 2, 2024 at 11:03 AM

So this means the bug was latent before your commit v8.1.0-1799-g38ee0a7dfb ?

Committed

Details

Assignee

Reporter

Start date

Components

Priority

Checklist

Sentry

Created October 21, 2023 at 8:58 AM
Updated February 6, 2024 at 3:17 AM
Resolved February 3, 2024 at 10:26 PM

Flag notifications