public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: frysk-cvs@sourceware.org
Subject: [SCM]  master: Removed bogus (unresolved) test for (duplicate) bug #2915.
Date: Thu, 17 Apr 2008 17:59:00 -0000	[thread overview]
Message-ID: <20080417175919.14789.qmail@sourceware.org> (raw)

The branch, master has been updated
       via  45a781515286e1728edaae497713aa46b2312c26 (commit)
      from  9ff746a00ed1e054abaf5b44cc27be4061b51cd9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 45a781515286e1728edaae497713aa46b2312c26
Author: Mark Wielaard <mwielaard@redhat.com>
Date:   Thu Apr 17 19:57:28 2008 +0200

    Removed bogus (unresolved) test for (duplicate) bug #2915.
    
    frysk-core/frysk/proc/ChangeLog
    2008-04-17  Mark Wielaard  <mwielaard@redhat.com>
    
           * TestTaskSyscallObserver (testCreateAttachedAddSyscallObserver):
           Removed bogus (unresolved) test for (duplicate) bug #2915.

-----------------------------------------------------------------------

Summary of changes:
 frysk-core/frysk/proc/ChangeLog                    |    5 ++++
 frysk-core/frysk/proc/TestTaskSyscallObserver.java |   22 --------------------
 2 files changed, 5 insertions(+), 22 deletions(-)

First 500 lines of diff:
diff --git a/frysk-core/frysk/proc/ChangeLog b/frysk-core/frysk/proc/ChangeLog
index 2926b76..87b7eb6 100644
--- a/frysk-core/frysk/proc/ChangeLog
+++ b/frysk-core/frysk/proc/ChangeLog
@@ -1,5 +1,10 @@
 2008-04-17  Mark Wielaard  <mwielaard@redhat.com>
 
+	* TestTaskSyscallObserver (testCreateAttachedAddSyscallObserver):
+	Removed bogus (unresolved) test for (duplicate) bug #2915.
+
+2008-04-17  Mark Wielaard  <mwielaard@redhat.com>
+
 	* TestBreakpoints.java (testSteppingtestHitAndRun): No longer
 	unresolved because of bug #4847, but make unresolvedOnIA32
 	because of bug #6044.
diff --git a/frysk-core/frysk/proc/TestTaskSyscallObserver.java b/frysk-core/frysk/proc/TestTaskSyscallObserver.java
index eb32613..c1a7f30 100644
--- a/frysk-core/frysk/proc/TestTaskSyscallObserver.java
+++ b/frysk-core/frysk/proc/TestTaskSyscallObserver.java
@@ -312,28 +312,6 @@ public class TestTaskSyscallObserver extends TestLib {
 
   };
 
-  public void testCreateAttachedAddSyscallObserver ()
-  {
-    if (unresolved(2915))
-      return;
-
-    int count = 5;
-
-    Manager.host.requestCreateAttachedProc(new String[]
-	{
-	    getExecPath ("funit-syscallloop"),
-	    Integer.toString(count)
-	}, attachedObserver);
-
-    // assertRunUntilStop("run until program exits");
-    assertRunUntilStop("run until program exits");
-
-    assertTrue("enough syscall enter events", syscallObserver1.enter >= count);
-    assertTrue("enough syscall enter exit", syscallObserver1.exit >= count);
-    assertTrue("inSyscall (last call doesn't exit)", syscallObserver1.inSyscall);
-    assertTrue("Caught exec syscall", syscallObserver1.caughtExec);
-  }
-
   /**
    * Test system calls. XXX: How is this different to testSyscallLoop (other
    * than the program run). XXX: Also why is the last syscall expected to exit


hooks/post-receive
--
frysk system monitor/debugger


                 reply	other threads:[~2008-04-17 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080417175919.14789.qmail@sourceware.org \
    --to=mark@sourceware.org \
    --cc=frysk-cvs@sourceware.org \
    --cc=frysk@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).