public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/13977] rlimit tests fail as-root portions
Date: Fri, 21 Jun 2013 17:20:00 -0000	[thread overview]
Message-ID: <bug-13977-6586-QTN1uJCvLv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13977-6586@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13977

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |dsmith at redhat dot com

--- Comment #3 from David Smith <dsmith at redhat dot com> ---
When fixing some tcl errors I saw in the testsuite, I made some changes to this
test case in the following commit:

====
commit 2b70fd7894ed74c39e69d7d3a73f25984107f6f2
Author: David Smith <dsmith@redhat.com>
Date:   Tue Jun 18 14:18:47 2013 -0500

    Fix tcl and logic errors in rlimit.exp.

    * testsuite/systemtap.base/rlimit.exp: To make sure "sudo stap" works
      correctly, use the full path.
    * testsuite/lib/systemtap.exp (as_non_root): If we're running as root, use
      user "nobody" to run commands.
====

Then Josh pointed out that my 'as_non_root' fix wasn't quite correct, so I made
another change:

====
commit edb7542edea73adeb3e15e8a36af18acff4f517a
Author: David Smith <dsmith@redhat.com>
Date:   Tue Jun 18 15:46:48 2013 -0500

    Another 'as_non_root' improvement.
====

I believe those commits should fix all the problems with rlimit.exp.

Josh's original problem was that it was picking the wrong stap. The change to
rlimit.exp to use the full path of the test executable should fix that problem.

I'm not 100% sure, but I'll bet Mark's problem of those two tests failing were
because of the 2nd fix above. If you were logged in as root, 'as_non_root'
still ran the command as root. Now, if you are logged in as root, 'as_non_root'
runs the command as the user 'nobody'.

Josh and Mark, could you test and see if the above commits fix things for you?

On rawhide, this test now passes for me when run by root, run by my login, or
run with sudo.

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

  parent reply	other threads:[~2013-06-21 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 20:54 [Bug testsuite/13977] New: " jistone at redhat dot com
2012-12-14 10:36 ` [Bug testsuite/13977] " mjw at redhat dot com
2013-06-20 17:30 ` fche at redhat dot com
2013-06-20 21:35   ` Hien Nguyen
2013-06-21 17:20 ` dsmith at redhat dot com [this message]
2013-06-21 18:14 ` mjw at redhat dot com
2013-06-21 18:15 ` jistone at redhat dot com
2013-06-21 18:29 ` jistone at redhat dot com
2013-06-21 21:57 ` dsmith at redhat dot com
2013-06-24 16:04 ` dsmith at redhat dot com
2013-06-24 16:10 ` dsmith 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-13977-6586-QTN1uJCvLv@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).