From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/20600] parallel testsuite hang in [nd_]syscall.exp
Date: Wed, 06 Dec 2023 20:55:15 +0000 [thread overview]
Message-ID: <bug-20600-6586-VFO4B2H0zT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20600-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20600
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wcohen at redhat dot com
--- Comment #9 from William Cohen <wcohen at redhat dot com> ---
Not possible to replicate this issue now "make installcheck-parallel" was
removed by commit 12c28db3271:
Author: Frank Ch. Eigler <fche@redhat.com> 2023-10-12 12:45:09
Committer: Frank Ch. Eigler <fche@redhat.com> 2023-10-12 13:11:35
Parent: 3b2b14c5d095e7c82594d79aabca5d407692eab4 (Teach stap-prep to use new
versions of dnf (if available))
Child: 823fcc4143c254bd847a1b4592b1580ee842239d (testsuite: drop busybox test
case)
Branches: master, mcermak-pr3040, remotes/origin/master,
remotes/origin/mcermak-pr3040, remotes/origin/uprobe-reg2, wcohen/dwarf5callee
Follows: release-4.9a
Precedes: release-5.0a
testsuite: simplify Makefile drivers
It was reported that "make installcheck" broke with commit
218c26a523816. Investigation pointed at quoting mishaps somewhere in
the Makefile machinery related to parallel / partial testsuite runs.
While this logic was clever and appeared useful for a time, it seems
fragile in practice and not in active use after all. So let's nuke
all of it.
Moved the environment_sanity.exp test into the systemtap/ subdirectory
to apprx. guarantee that it's run first, no Makefile magic needed. It
still exits dejagnu entirely if it fails.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-12-06 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:58 [Bug testsuite/20600] New: parallet " dsmith at redhat dot com
2016-09-15 14:28 ` [Bug testsuite/20600] " dsmith at redhat dot com
2016-09-15 19:40 ` dsmith at redhat dot com
2016-09-15 19:53 ` [Bug testsuite/20600] parallel " dsmith at redhat dot com
2016-09-15 20:13 ` dsmith at redhat dot com
2016-09-22 14:26 ` dsmith at redhat dot com
2016-09-22 18:09 ` dsmith at redhat dot com
2017-02-28 16:13 ` dsmith at redhat dot com
2017-03-02 7:29 ` mcermak at redhat dot com
2017-03-03 19:17 ` dsmith at redhat dot com
2023-12-06 20:55 ` wcohen at redhat dot com [this message]
2024-02-21 13:25 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-20600-6586-VFO4B2H0zT@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).