about the test.py

53 views
Skip to first unread message

jman

unread,
Sep 9, 2010, 4:13:10 AM9/9/10
to ns-3-...@googlegroups.com
Hi, all
 
I am a newbie for ns, and I encounter the problem as below.
 
I have downloaded the ns-allinone-3.9.tar.bz2 and compiled
 
it successfully on the ubuntu10.4.1. In other words, build.py
 
got a perfect work. However, the test.py get a message which
 
is "146 of 149 tests passed (146 passed, 0 skipped, 0 failed, 3 crashed, 0 valgrind errors)".
 
The three crashed output message line list here.
 
CRASH: TestSuite nsc-tcp-loss
CRASH: TestSuite ns3-tcp-cwnd
CRASH: TestSuite ns3-tcp-interoperability
 
What I want to be sure is that if the ns3 installed successfully?
 
And should I correct the crashed tests? How?
 
Can I get accurate result if I work base on this ns3?
 
thanks for your help.
 
- rocky wang
 

Gilbran Silva de Andrade

unread,
Sep 9, 2010, 8:27:56 AM9/9/10
to ns-3-...@googlegroups.com
Hi Rocky,

I've got this same crash warning when i tried using tarball install on
my opensuse 11.3.

My solution was quick and easier, I downloaded and installed by
"mercurial version".
(http://www.nsnam.org/docs/release/tutorial.html#Downloading-ns_002d3)

Gilbran Silva de Andrade

> --
> You received this message because you are subscribed to the Google Groups
> "ns-3-users" group.
> To post to this group, send email to ns-3-...@googlegroups.com.
> To unsubscribe from this group, send email to
> ns-3-users+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/ns-3-users?hl=en.
>

Tom Henderson

unread,
Sep 9, 2010, 9:56:58 AM9/9/10
to ns-3-...@googlegroups.com
On 9/9/10 5:27 AM, Gilbran Silva de Andrade wrote:
> Hi Rocky,
>
> I've got this same crash warning when i tried using tarball install on
> my opensuse 11.3.
>
> My solution was quick and easier, I downloaded and installed by
> "mercurial version".
> (http://www.nsnam.org/docs/release/tutorial.html#Downloading-ns_002d3)
>
> Gilbran Silva de Andrade


I believe that this is an instance of this bug, which we will try to fix
soon:
http://www.nsnam.org/bugzilla/show_bug.cgi?id=980

The problem is that ./waf configure detects that there is an nsc
directory present but nsc hasn't been successfully built, so the test
suite tries to use nsc in some test cases but the library is not there.

- Tom

Reply all
Reply to author
Forward
0 new messages