public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31597] Systemtap not extracting all the data sent to the print data in the buffers before shutdown
Date: Fri, 26 Apr 2024 15:56:14 +0000	[thread overview]
Message-ID: <bug-31597-6586-KldbWobabx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31597-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31597

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
This has been addressed the following git commit:

commit eb1f039347f70838bfea922034c1aaa1b14a6379 (HEAD -> master, origin/master,
origin/HEAD)
Author: William Cohen <wcohen@redhat.com>
Date:   Fri Apr 26 11:20:27 2024 -0400

    PR31597: Allow time for data in buffers to be read out before shutdown

    On SystemTap scripts using the -c <command> option some data was
    dropped from the output.  This was observed with sporadic failures of
    the *syscall.exp tests.  The process of shutting down the transport
    layer moving data from the kernel- to user-space was not allowing time
    for data to be completely drained from the buffers. A delay has been
    added in the shutdown process to provided the needed time to drain the
    buffers.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2024-04-26 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 19:13 [Bug runtime/31597] New: " wcohen at redhat dot com
2024-04-17 14:42 ` [Bug runtime/31597] " wcohen at redhat dot com
2024-04-26 15:56 ` wcohen at redhat dot com [this message]

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-31597-6586-KldbWobabx@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).