emacs-bug-tracker
[Top][All Lists]
Advanced

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

bug#55866: closed ([PATCH 0/2] Disable tests failing due to YAMA’s ptrac


From: GNU bug Tracking System
Subject: bug#55866: closed ([PATCH 0/2] Disable tests failing due to YAMA’s ptrace_scope.)
Date: Fri, 10 Jun 2022 09:44:02 +0000

Your message dated Fri, 10 Jun 2022 11:43:10 +0200
with message-id <YqMSLqthlR2xKSht@noor.fritz.box>
and subject line Re: [bug#55866] [PATCH 0/2] Disable tests failing due to 
YAMA’s ptrace_scope.
has caused the debbugs.gnu.org bug report #55866,
regarding [PATCH 0/2] Disable tests failing due to YAMA’s ptrace_scope.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
55866: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55866
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/2] Disable tests failing due to YAMA’s ptrace_scope. Date: Thu, 9 Jun 2022 10:51:10 +0200
Hi,

I noticed that some tests fail on my foreign distribution,
but not on Guix System, because they differ in their
/proc/sys/kernel/yama/ptrace_scope. Guix sets it to 0 (no limitations),
whereas most distributions default to 1 (only children can be ptrace’d),
causing a reproducibility issue. The following patches therefore disable
tests, which fail with a setting of >0.

Cheers,
Lars

Lars-Dominik Braun (2):
  gnu: python-pydevd: Skip tests failing due to YAMA.
  gnu: python-debugpy: Disable tests.

 gnu/packages/python-xyz.scm | 29 +++++++++++++++++------------
 1 file changed, 17 insertions(+), 12 deletions(-)

-- 
2.35.1




--- End Message ---
--- Begin Message --- Subject: Re: [bug#55866] [PATCH 0/2] Disable tests failing due to YAMA’s ptrace_scope. Date: Fri, 10 Jun 2022 11:43:10 +0200
Hi Maxime,

> Sounds reasonable to me, though I recommend reporting the issue
> upstream such that they can adjust their test suites to skip the tests
> when YAMA interferes.
pushed as 9d2ef7344e340747640dc00413aa6a7b054f022a and
3e6bc1edca0c7ee4e8bfe0d8e783db48d2bb647c. I added a link to the upstream
report in the comments. Doesn’t make much sense for python-debugpy
though, since we’d end up with no test suite at all.

Thank you very much,
Lars



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]