All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
	John Ogness <john.ogness@linutronix.de>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nam Cao <namcao@linutronix.de>
Subject: [PATCH v2 0/3] selftests: coredump: Some bug fixes
Date: Fri, 11 Apr 2025 17:09:40 +0200	[thread overview]
Message-ID: <cover.1744383419.git.namcao@linutronix.de> (raw)

Hi,

While trying the coredump test on qemu-system-riscv64, I observed test
failures for various reasons.

This series makes the test works on qemu-system-riscv64.

Best regards,
Nam

v1->v2 https://lore.kernel.org/lkml/cover.1743438749.git.namcao@linutronix.de/
  - use getline() more precisely [John Ogness]
  - be absolutely safe: waitpid() for the child process, and still wait 10s
    for stack_values file to be created [John Ogness]

Nam Cao (3):
  selftests: coredump: Properly initialize pointer
  selftests: coredump: Fix test failure for slow machines
  selftests: coredump: Raise timeout to 2 minutes

 tools/testing/selftests/coredump/stackdump_test.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

-- 
2.39.5


             reply	other threads:[~2025-04-11 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 15:09 Nam Cao [this message]
2025-04-11 15:09 ` [PATCH v2 1/3] selftests: coredump: Properly initialize pointer Nam Cao
2025-04-11 15:27   ` ALOK TIWARI
2025-04-11 15:09 ` [PATCH v2 2/3] selftests: coredump: Fix test failure for slow machines Nam Cao
2025-04-11 15:09 ` [PATCH v2 3/3] selftests: coredump: Raise timeout to 2 minutes Nam Cao
2025-04-14 11:08 ` [PATCH v2 0/3] selftests: coredump: Some bug fixes Christian Brauner

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=cover.1744383419.git.namcao@linutronix.de \
    --to=namcao@linutronix.de \
    --cc=brauner@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.