All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: LTP <ltp-list@lists.sourceforge.net>
Cc: Matt Helsley <matthltc@linux.vnet.ibm.com>
Subject: [LTP] Fix for running freezer testcases
Date: Tue, 9 Mar 2010 12:28:52 +0530	[thread overview]
Message-ID: <20100309065852.GA5875@linux.vnet.ibm.com> (raw)

commit 58854395050b8a3bb2fa4e5e4401546925f6aad8
Author: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
Date:   Tue Mar 9 12:24:47 2010 +0530

    Commenting "make all" in run_freezer.sh file as it is stopping to
run the freezer testcase
    

    Signed-off By: Rishikesh K Rajak<risrajak@linux.vnet.ibm.com>

diff --git a/testcases/kernel/controllers/freezer/run_freezer.sh
b/testcases/kernel/controllers/freezer/run_freezer.sh
index 3baf968..f66e321 100755
--- a/testcases/kernel/controllers/freezer/run_freezer.sh
+++ b/testcases/kernel/controllers/freezer/run_freezer.sh
@@ -69,7 +69,8 @@ function test_setup()
        export LTPBIN PATH TCID TST_COUNT TST_TOTAL CGROUPS_TESTROOT
        tst_resm TINFO "Preparing to run: ${P} $@"
 
-       make all
+       # this is not require here
+       #make all
 }
 
 function test_prereqs()

-- 
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

                 reply	other threads:[~2010-03-09  6: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=20100309065852.GA5875@linux.vnet.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=matthltc@linux.vnet.ibm.com \
    /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.