Sponsored Content
Full Discussion: validate test failed
Operating Systems Linux Red Hat validate test failed Post 302101973 by newbie06 on Saturday 6th of January 2007 12:23:43 PM
Old 01-06-2007
validate test failed

hi everybody,

I am new in Linux. I have successfully installed knoppix in my laptop, however, when I want to install ns2.26, some errors occurs in validation test.. It returned "Some Test failed" and it give some comands to re-run the test. I have already set the path before the validation test. When I tried to run any example from the tcl/ex, it returned "bash:command not found"..Is there any different between setting path in redhat and setting path in knoppix although I use same version of ns (ns2.26)? because I've used redhat before and change to knoppix and I've used the same format of setting up the path..Or is there any other problems?..Can anybody help me with thid problem?..I get confius wether i need to edit .bashrc file or .bash_profile? for the time being I've editted .bash_profile. Thank you in advance for your help..
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bad day !! test condition failed --need a one liner to do --help

Hi all this is simple but bad day for me nothing work out .. Problem is that I wan to check the argument passed to my script and accordignly exit or setup ENV variable I have a script name src_cpcp_preproc.sh i want to pass 2 argumet from command line argumet and check it in the script... (13 Replies)
Discussion started by: jambesh
13 Replies

2. AIX

SFTP Failed---Request for subsystem 'sftp' failed on channel 0

Hi, While I am trying SFTP my machine to another unix machine , it was working fine till 10 min back. But now i am getting the below error "Request for subsystem 'sftp' failed on channel 0" Could you please someone help me to solve or analyise the root cause... Cheers:b:, Mahiban (0 Replies)
Discussion started by: mahiban
0 Replies

3. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

4. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

5. Shell Programming and Scripting

Prefixing test case methods with letter 'test'

Hi, I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies

6. UNIX for Advanced & Expert Users

Rngd: failed fips test

I have recently enabled the process rngd, but after couple of days i see it got stopped automatically . Below is what i could find from messages file . can someone shed light on what could be the reason and how can this can be taken care? Apr 1 08:12:05 sap01 rngd: failed fips test Apr 1... (3 Replies)
Discussion started by: radha254
3 Replies
App::Prove::State::Result::Test(3pm)			 Perl Programmers Reference Guide		      App::Prove::State::Result::Test(3pm)

NAME
App::Prove::State::Result::Test - Individual test results. VERSION
Version 3.26 DESCRIPTION
The "prove" command supports a "--state" option that instructs it to store persistent state across runs. This module encapsulates the results for a single test. SYNOPSIS
# Re-run failed tests $ prove --state=fail,save -rbv METHODS
Class Methods "new" Instance Methods "name" The name of the test. Usually a filename. "elapsed" The total elapsed times the test took to run, in seconds from the epoch.. "generation" The number for the "generation" of the test run. The first generation is 1 (one) and subsequent generations are 2, 3, etc. "last_pass_time" The last time the test program passed, in seconds from the epoch. Returns "undef" if the program has never passed. "last_fail_time" The last time the test suite failed, in seconds from the epoch. Returns "undef" if the program has never failed. "mtime" Returns the mtime of the test, in seconds from the epoch. "raw" Returns a hashref of raw test data, suitable for serialization by YAML. "result" Currently, whether or not the test suite passed with no 'problems' (such as TODO passed). "run_time" The total time it took for the test to run, in seconds. If "Time::HiRes" is available, it will have finer granularity. "num_todo" The number of tests with TODO directives. "sequence" The order in which this test was run for the given test suite result. "total_passes" The number of times the test has passed. "total_failures" The number of times the test has failed. "parser" The underlying parser object. This is useful if you need the full information for the test program. perl v5.18.2 2014-01-06 App::Prove::State::Result::Test(3pm)
All times are GMT -4. The time now is 09:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy