2019-08-12 16:55:34 -07:00
#! /usr/bin/env python3
2009-09-12 19:44:17 -07:00
## -*- Mode: python; py-indent-offset: 4; indent-tabs-mode: nil; coding: utf-8; -*-
#
# Copyright (c) 2009 University of Washington
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License version 2 as
# published by the Free Software Foundation;
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
#
import os
import sys
2009-10-12 14:01:36 -07:00
import time
2009-09-12 19:44:17 -07:00
import optparse
import subprocess
import threading
import signal
import xml . dom . minidom
2009-09-23 15:20:23 -07:00
import shutil
2020-01-09 14:03:13 +01:00
import fnmatch
2009-09-12 19:44:17 -07:00
2011-03-09 16:49:59 -08:00
from utils import get_list_from_file
2020-01-09 14:05:40 +01:00
# imported from waflib Logs
colors_lst = { ' USE ' : True , ' BOLD ' : ' \x1b [01;1m ' , ' RED ' : ' \x1b [01;31m ' , ' GREEN ' : ' \x1b [32m ' , ' YELLOW ' : ' \x1b [33m ' , ' PINK ' : ' \x1b [35m ' , ' BLUE ' : ' \x1b [01;34m ' , ' CYAN ' : ' \x1b [36m ' , ' GREY ' : ' \x1b [37m ' , ' NORMAL ' : ' \x1b [0m ' , ' cursor_on ' : ' \x1b [?25h ' , ' cursor_off ' : ' \x1b [?25l ' , }
def get_color ( cl ) :
if colors_lst [ ' USE ' ] :
return colors_lst . get ( cl , ' ' )
return ' '
class color_dict ( object ) :
def __getattr__ ( self , a ) :
return get_color ( a )
def __call__ ( self , a ) :
return get_color ( a )
colors = color_dict ( )
2015-09-03 21:14:55 -07:00
try :
import queue
except ImportError :
import Queue as queue
2009-09-12 19:44:17 -07:00
#
# XXX This should really be part of a waf command to list the configuration
# items relative to optional ns-3 pieces.
#
2018-12-27 12:24:03 +03:00
# A list of interesting configuration items in the waf configuration
2009-09-12 19:44:17 -07:00
# cache which we may be interested in when deciding on which examples
2018-12-27 12:24:03 +03:00
# to run and how to run them. These are set by waf during the
2009-09-12 19:44:17 -07:00
# configuration phase and the corresponding assignments are usually
# found in the associated subdirectory wscript files.
#
interesting_config_items = [
2011-03-09 16:49:59 -08:00
" NS3_ENABLED_MODULES " ,
2017-04-06 20:32:04 -07:00
" NS3_ENABLED_CONTRIBUTED_MODULES " ,
2009-09-12 19:44:17 -07:00
" NS3_MODULE_PATH " ,
" ENABLE_REAL_TIME " ,
2011-04-15 13:03:02 -07:00
" ENABLE_THREADING " ,
2009-10-06 19:34:29 -07:00
" ENABLE_EXAMPLES " ,
2011-05-19 11:54:32 -07:00
" ENABLE_TESTS " ,
2011-03-09 16:49:59 -08:00
" EXAMPLE_DIRECTORIES " ,
2010-04-17 17:36:53 +01:00
" ENABLE_PYTHON_BINDINGS " ,
2016-02-08 22:43:32 -08:00
" NSCLICK " ,
2012-12-04 11:53:47 -05:00
" ENABLE_BRITE " ,
2011-03-11 15:21:50 -05:00
" ENABLE_OPENFLOW " ,
2012-01-13 10:17:39 -08:00
" APPNAME " ,
" BUILD_PROFILE " ,
" VERSION " ,
2012-01-13 16:07:23 -08:00
" PYTHON " ,
2013-06-14 16:31:10 -07:00
" VALGRIND_FOUND " ,
2009-09-12 19:44:17 -07:00
]
2009-09-29 10:16:17 -07:00
ENABLE_REAL_TIME = False
2011-04-15 13:03:02 -07:00
ENABLE_THREADING = False
2009-10-06 19:34:29 -07:00
ENABLE_EXAMPLES = True
2011-05-19 11:54:32 -07:00
ENABLE_TESTS = True
2016-02-08 22:43:32 -08:00
NSCLICK = False
2012-12-04 11:53:47 -05:00
ENABLE_BRITE = False
2011-03-11 15:21:50 -05:00
ENABLE_OPENFLOW = False
2011-03-09 16:49:59 -08:00
EXAMPLE_DIRECTORIES = [ ]
2012-01-13 10:17:39 -08:00
APPNAME = " "
BUILD_PROFILE = " "
2013-06-19 11:17:17 -07:00
BUILD_PROFILE_SUFFIX = " "
2012-01-13 10:17:39 -08:00
VERSION = " "
2012-01-16 17:01:24 -08:00
PYTHON = " "
2013-06-14 16:31:10 -07:00
VALGRIND_FOUND = True
2012-01-13 10:17:39 -08:00
#
# This will be given a prefix and a suffix when the waf config file is
# read.
#
test_runner_name = " test-runner "
2009-10-06 19:34:29 -07:00
#
# If the user has constrained us to run certain kinds of tests, we can tell waf
# to only build
2009-10-09 12:54:54 -07:00
#
2020-01-18 10:28:47 +01:00
core_kinds = [ " core " , " performance " , " system " , " unit " ]
2009-09-29 10:16:17 -07:00
2009-10-09 12:54:54 -07:00
#
2021-12-02 21:30:16 -08:00
# Exclude tests that are problematic for valgrind.
2009-10-09 12:54:54 -07:00
#
core_valgrind_skip_tests = [
2011-05-23 11:51:29 -04:00
" routing-click " ,
2013-01-13 21:12:00 -08:00
" lte-rr-ff-mac-scheduler " ,
" lte-tdmt-ff-mac-scheduler " ,
" lte-fdmt-ff-mac-scheduler " ,
" lte-pf-ff-mac-scheduler " ,
" lte-tta-ff-mac-scheduler " ,
" lte-fdbet-ff-mac-scheduler " ,
" lte-ttbet-ff-mac-scheduler " ,
" lte-fdtbfq-ff-mac-scheduler " ,
" lte-tdtbfq-ff-mac-scheduler " ,
" lte-pss-ff-mac-scheduler " ,
2009-10-09 12:54:54 -07:00
]
2009-09-12 19:44:17 -07:00
#
2011-03-09 16:49:59 -08:00
# Parse the examples-to-run file if it exists.
2010-04-15 10:53:40 -07:00
#
2011-03-09 16:49:59 -08:00
# This function adds any C++ examples or Python examples that are to be run
# to the lists in example_tests and python_tests, respectively.
2010-04-15 10:53:40 -07:00
#
2011-03-09 16:49:59 -08:00
def parse_examples_to_run_file (
examples_to_run_path ,
cpp_executable_dir ,
python_script_dir ,
example_tests ,
2013-01-14 09:39:06 -08:00
example_names_original ,
2011-03-09 16:49:59 -08:00
python_tests ) :
2010-04-15 10:53:40 -07:00
2011-03-09 16:49:59 -08:00
# Look for the examples-to-run file exists.
if os . path . exists ( examples_to_run_path ) :
2010-04-15 10:53:40 -07:00
2011-03-09 16:49:59 -08:00
# Each tuple in the C++ list of examples to run contains
#
# (example_name, do_run, do_valgrind_run)
#
# where example_name is the executable to be run, do_run is a
# condition under which to run the example, and do_valgrind_run is
# a condition under which to run the example under valgrind. This
# is needed because NSC causes illegal instruction crashes with
# some tests when they are run under valgrind.
#
# Note that the two conditions are Python statements that
# can depend on waf configuration variables. For example,
2021-12-02 21:30:16 -08:00
# when NSC was in the codebase, we could write:
2011-03-09 16:49:59 -08:00
#
# ("tcp-nsc-lfn", "NSC_ENABLED == True", "NSC_ENABLED == False"),
#
cpp_examples = get_list_from_file ( examples_to_run_path , " cpp_examples " )
for example_name , do_run , do_valgrind_run in cpp_examples :
2013-01-14 09:39:06 -08:00
2018-06-27 10:50:27 +03:00
# Separate the example name from its arguments.
2013-01-14 09:39:06 -08:00
example_name_original = example_name
2012-04-25 19:08:07 -07:00
example_name_parts = example_name . split ( ' ' , 1 )
if len ( example_name_parts ) == 1 :
example_name = example_name_parts [ 0 ]
example_arguments = " "
else :
example_name = example_name_parts [ 0 ]
example_arguments = example_name_parts [ 1 ]
2012-01-13 10:17:39 -08:00
# Add the proper prefix and suffix to the example name to
# match what is done in the wscript file.
2014-01-10 17:20:26 -08:00
example_path = " %s %s - %s %s " % ( APPNAME , VERSION , example_name , BUILD_PROFILE_SUFFIX )
2012-04-25 19:08:07 -07:00
# Set the full path for the example.
2014-01-10 17:20:26 -08:00
example_path = os . path . join ( cpp_executable_dir , example_path )
example_name = os . path . join (
os . path . relpath ( cpp_executable_dir , NS3_BUILDDIR ) ,
example_name )
2011-03-09 16:49:59 -08:00
# Add all of the C++ examples that were built, i.e. found
# in the directory, to the list of C++ examples to run.
if os . path . exists ( example_path ) :
2012-04-25 19:08:07 -07:00
# Add any arguments to the path.
if len ( example_name_parts ) != 1 :
example_path = " %s %s " % ( example_path , example_arguments )
2014-01-10 17:20:26 -08:00
example_name = " %s %s " % ( example_name , example_arguments )
2011-03-09 16:49:59 -08:00
2012-04-25 19:08:07 -07:00
# Add this example.
2014-01-10 17:20:26 -08:00
example_tests . append ( ( example_name , example_path , do_run , do_valgrind_run ) )
2013-01-14 09:39:06 -08:00
example_names_original . append ( example_name_original )
2018-12-27 12:24:03 +03:00
2011-03-09 16:49:59 -08:00
# Each tuple in the Python list of examples to run contains
#
# (example_name, do_run)
#
# where example_name is the Python script to be run and
# do_run is a condition under which to run the example.
#
# Note that the condition is a Python statement that can
# depend on waf configuration variables. For example,
#
# ("realtime-udp-echo.py", "ENABLE_REAL_TIME == True"),
#
python_examples = get_list_from_file ( examples_to_run_path , " python_examples " )
for example_name , do_run in python_examples :
2018-06-27 10:50:27 +03:00
# Separate the example name from its arguments.
2012-04-25 19:08:07 -07:00
example_name_parts = example_name . split ( ' ' , 1 )
if len ( example_name_parts ) == 1 :
example_name = example_name_parts [ 0 ]
example_arguments = " "
else :
example_name = example_name_parts [ 0 ]
example_arguments = example_name_parts [ 1 ]
# Set the full path for the example.
2011-03-09 16:49:59 -08:00
example_path = os . path . join ( python_script_dir , example_name )
2012-04-25 19:08:07 -07:00
2011-03-09 16:49:59 -08:00
# Add all of the Python examples that were found to the
# list of Python examples to run.
if os . path . exists ( example_path ) :
2012-04-25 19:08:07 -07:00
# Add any arguments to the path.
if len ( example_name_parts ) != 1 :
example_path = " %s %s " % ( example_path , example_arguments )
# Add this example.
2011-03-09 16:49:59 -08:00
python_tests . append ( ( example_path , do_run ) )
2010-04-15 10:53:40 -07:00
2009-09-12 19:44:17 -07:00
#
# The test suites are going to want to output status. They are running
# concurrently. This means that unless we are careful, the output of
# the test suites will be interleaved. Rather than introducing a lock
# file that could unintentionally start serializing execution, we ask
2018-12-27 12:24:03 +03:00
# the tests to write their output to a temporary directory and then
2009-09-12 19:44:17 -07:00
# put together the final output file when we "join" the test tasks back
2009-10-12 14:01:36 -07:00
# to the main thread. In addition to this issue, the example programs
# often write lots and lots of trace files which we will just ignore.
# We put all of them into the temp directory as well, so they can be
# easily deleted.
2009-09-12 19:44:17 -07:00
#
2009-10-12 14:01:36 -07:00
TMP_OUTPUT_DIR = " testpy-output "
2009-09-12 19:44:17 -07:00
2011-07-29 03:38:59 -04:00
def read_test ( test ) :
result = test . find ( ' Result ' ) . text
name = test . find ( ' Name ' ) . text
2018-11-06 12:30:43 -08:00
if not test . find ( ' Reason ' ) is None :
reason = test . find ( ' Reason ' ) . text
else :
reason = ' '
2011-07-29 03:38:59 -04:00
if not test . find ( ' Time ' ) is None :
time_real = test . find ( ' Time ' ) . get ( ' real ' )
else :
time_real = ' '
2018-11-06 12:30:43 -08:00
return ( result , name , reason , time_real )
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# A simple example of writing a text file with a test result summary. It is
2009-09-30 20:26:33 -07:00
# expected that this output will be fine for developers looking for problems.
2009-09-12 19:44:17 -07:00
#
2020-06-04 12:12:30 -07:00
def node_to_text ( test , f , test_type = ' Suite ' ) :
2018-11-06 12:30:43 -08:00
( result , name , reason , time_real ) = read_test ( test )
if reason :
reason = " ( %s ) " % reason
2018-12-27 12:24:03 +03:00
2020-06-04 12:12:30 -07:00
output = " %s : Test %s \" %s \" ( %s ) %s \n " % ( result , test_type , name , time_real , reason )
2011-07-29 03:38:59 -04:00
f . write ( output )
for details in test . findall ( ' FailureDetails ' ) :
f . write ( " Details: \n " )
f . write ( " Message: %s \n " % details . find ( ' Message ' ) . text )
f . write ( " Condition: %s \n " % details . find ( ' Condition ' ) . text )
f . write ( " Actual: %s \n " % details . find ( ' Actual ' ) . text )
f . write ( " Limit: %s \n " % details . find ( ' Limit ' ) . text )
f . write ( " File: %s \n " % details . find ( ' File ' ) . text )
f . write ( " Line: %s \n " % details . find ( ' Line ' ) . text )
for child in test . findall ( ' Test ' ) :
2020-06-04 12:12:30 -07:00
node_to_text ( child , f , ' Case ' )
2011-07-29 03:38:59 -04:00
2009-09-12 19:44:17 -07:00
def translate_to_text ( results_file , text_file ) :
2018-11-06 12:30:43 -08:00
text_file + = ' .txt '
print ( ' Writing results to text file \" %s \" ... ' % text_file , end = ' ' )
2011-07-29 03:38:59 -04:00
import xml . etree . ElementTree as ET
2018-12-27 12:59:23 +03:00
et = ET . parse ( results_file )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
with open ( text_file , ' w ' ) as f :
for test in et . findall ( ' Test ' ) :
node_to_text ( test , f )
for example in et . findall ( ' Example ' ) :
result = example . find ( ' Result ' ) . text
name = example . find ( ' Name ' ) . text
if not example . find ( ' Time ' ) is None :
time_real = example . find ( ' Time ' ) . get ( ' real ' )
else :
time_real = ' '
output = " %s : Example \" %s \" ( %s ) \n " % ( result , name , time_real )
f . write ( output )
2018-11-06 12:30:43 -08:00
print ( ' done. ' )
2018-12-27 12:24:03 +03:00
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# A simple example of writing an HTML file with a test result summary. It is
2009-09-30 20:26:33 -07:00
# expected that this will eventually be made prettier as time progresses and
# we have time to tweak it. This may end up being moved to a separate module
# since it will probably grow over time.
2009-09-12 19:44:17 -07:00
#
def translate_to_html ( results_file , html_file ) :
2018-11-06 12:30:43 -08:00
html_file + = ' .html '
print ( ' Writing results to html file %s ... ' % html_file , end = ' ' )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
with open ( html_file , ' w ' ) as f :
f . write ( " <html> \n " )
f . write ( " <body> \n " )
f . write ( " <center><h1>ns-3 Test Results</h1></center> \n " )
2009-09-12 19:44:17 -07:00
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# Read and parse the whole results file.
2018-12-27 12:24:03 +03:00
#
2020-05-13 18:45:06 +01:00
import xml . etree . ElementTree as ET
et = ET . parse ( results_file )
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# Iterate through the test suites
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
f . write ( " <h2>Test Suites</h2> \n " )
for suite in et . findall ( ' Test ' ) :
#
# For each test suite, get its name, result and execution time info
#
( result , name , reason , time ) = read_test ( suite )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
#
# Print a level three header with the result, name and time. If the
# test suite passed, the header is printed in green. If the suite was
# skipped, print it in orange, otherwise assume something bad happened
# and print in red.
#
if result == " PASS " :
f . write ( " <h3 style= \" color:green \" > %s : %s ( %s )</h3> \n " % ( result , name , time ) )
elif result == " SKIP " :
f . write ( " <h3 style= \" color:#ff6600 \" > %s : %s ( %s ) ( %s )</h3> \n " % ( result , name , time , reason ) )
2009-10-09 12:54:54 -07:00
else :
2020-05-13 18:45:06 +01:00
f . write ( " <h3 style= \" color:red \" > %s : %s ( %s )</h3> \n " % ( result , name , time ) )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
#
# The test case information goes in a table.
#
f . write ( " <table border= \" 1 \" > \n " )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
#
# The first column of the table has the heading Result
#
f . write ( " <th> Result </th> \n " )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
#
# If the suite crashed or is skipped, there is no further information, so just
# declare a new table row with the result (CRASH or SKIP) in it. Looks like:
#
# +--------+
# | Result |
# +--------+
# | CRASH |
# +--------+
#
# Then go on to the next test suite. Valgrind and skipped errors look the same.
#
if result in [ " CRASH " , " SKIP " , " VALGR " ] :
f . write ( " <tr> \n " )
if result == " SKIP " :
f . write ( " <td style= \" color:#ff6600 \" > %s </td> \n " % result )
else :
f . write ( " <td style= \" color:red \" > %s </td> \n " % result )
f . write ( " </tr> \n " )
f . write ( " </table> \n " )
continue
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# If the suite didn't crash, we expect more information, so fill out
# the table heading row. Like,
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# +--------+----------------+------+
# | Result | Test Case Name | Time |
# +--------+----------------+------+
#
f . write ( " <th>Test Case Name</th> \n " )
f . write ( " <th> Time </th> \n " )
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# If the test case failed, we need to print out some failure details
# so extend the heading row again. Like,
#
# +--------+----------------+------+-----------------+
# | Result | Test Case Name | Time | Failure Details |
# +--------+----------------+------+-----------------+
2009-09-30 20:26:33 -07:00
#
2009-09-12 19:44:17 -07:00
if result == " FAIL " :
2020-05-13 18:45:06 +01:00
f . write ( " <th>Failure Details</th> \n " )
#
# Now iterate through all of the test cases.
#
for case in suite . findall ( ' Test ' ) :
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# Get the name, result and timing information from xml to use in
# printing table below.
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
( result , name , reason , time ) = read_test ( case )
2009-09-30 20:26:33 -07:00
2020-05-13 18:45:06 +01:00
#
# If the test case failed, we iterate through possibly multiple
# failure details
#
if result == " FAIL " :
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# There can be multiple failures for each test case. The first
# row always gets the result, name and timing information along
# with the failure details. Remaining failures don't duplicate
# this information but just get blanks for readability. Like,
#
# +--------+----------------+------+-----------------+
# | Result | Test Case Name | Time | Failure Details |
# +--------+----------------+------+-----------------+
# | FAIL | The name | time | It's busted |
# +--------+----------------+------+-----------------+
# | | | | Really broken |
# +--------+----------------+------+-----------------+
# | | | | Busted bad |
# +--------+----------------+------+-----------------+
2009-09-30 20:26:33 -07:00
#
2018-12-27 12:24:03 +03:00
2020-05-13 18:45:06 +01:00
first_row = True
for details in case . findall ( ' FailureDetails ' ) :
#
# Start a new row in the table for each possible Failure Detail
#
f . write ( " <tr> \n " )
if first_row :
first_row = False
f . write ( " <td style= \" color:red \" > %s </td> \n " % result )
f . write ( " <td> %s </td> \n " % name )
f . write ( " <td> %s </td> \n " % time )
else :
f . write ( " <td></td> \n " )
f . write ( " <td></td> \n " )
f . write ( " <td></td> \n " )
f . write ( " <td> " )
f . write ( " <b>Message: </b> %s , " % details . find ( ' Message ' ) . text )
f . write ( " <b>Condition: </b> %s , " % details . find ( ' Condition ' ) . text )
f . write ( " <b>Actual: </b> %s , " % details . find ( ' Actual ' ) . text )
f . write ( " <b>Limit: </b> %s , " % details . find ( ' Limit ' ) . text )
f . write ( " <b>File: </b> %s , " % details . find ( ' File ' ) . text )
f . write ( " <b>Line: </b> %s " % details . find ( ' Line ' ) . text )
f . write ( " </td> \n " )
#
# End the table row
#
f . write ( " </td> \n " )
else :
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# If this particular test case passed, then we just print the PASS
# result in green, followed by the test case name and its execution
# time information. These go off in <td> ... </td> table data.
# The details table entry is left blank.
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# +--------+----------------+------+---------+
# | Result | Test Case Name | Time | Details |
# +--------+----------------+------+---------+
# | PASS | The name | time | |
# +--------+----------------+------+---------+
#
f . write ( " <tr> \n " )
f . write ( " <td style= \" color:green \" > %s </td> \n " % result )
f . write ( " <td> %s </td> \n " % name )
f . write ( " <td> %s </td> \n " % time )
f . write ( " <td> %s </td> \n " % reason )
f . write ( " </tr> \n " )
#
# All of the rows are written, so we need to end the table.
#
f . write ( " </table> \n " )
2018-12-27 12:24:03 +03:00
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# That's it for all of the test suites. Now we have to do something about
# our examples.
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
f . write ( " <h2>Examples</h2> \n " )
2018-12-27 12:24:03 +03:00
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# Example status is rendered in a table just like the suites.
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
f . write ( " <table border= \" 1 \" > \n " )
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# The table headings look like,
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# +--------+--------------+--------------+---------+
# | Result | Example Name | Elapsed Time | Details |
# +--------+--------------+--------------+---------+
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
f . write ( " <th> Result </th> \n " )
f . write ( " <th>Example Name</th> \n " )
f . write ( " <th>Elapsed Time</th> \n " )
f . write ( " <th>Details</th> \n " )
2009-09-30 20:26:33 -07:00
2009-10-27 00:19:02 -07:00
#
2020-05-13 18:45:06 +01:00
# Now iterate through all of the examples
2009-10-27 00:19:02 -07:00
#
2020-05-13 18:45:06 +01:00
for example in et . findall ( " Example " ) :
#
# Start a new row for each example
#
f . write ( " <tr> \n " )
#
# Get the result and name of the example in question
#
( result , name , reason , time ) = read_test ( example )
#
# If the example either failed or crashed, print its result status
# in red; otherwise green. This goes in a <td> ... </td> table data
#
if result == " PASS " :
f . write ( " <td style= \" color:green \" > %s </td> \n " % result )
elif result == " SKIP " :
f . write ( " <td style= \" color:#ff6600 \" > %s </fd> \n " % result )
else :
f . write ( " <td style= \" color:red \" > %s </td> \n " % result )
#
# Write the example name as a new tag data.
#
f . write ( " <td> %s </td> \n " % name )
#
# Write the elapsed time as a new tag data.
#
f . write ( " <td> %s </td> \n " % time )
#
# Write the reason, if it exist
#
f . write ( " <td> %s </td> \n " % reason )
#
# That's it for the current example, so terminate the row.
#
f . write ( " </tr> \n " )
2009-10-27 00:19:02 -07:00
2018-11-06 12:30:43 -08:00
#
2020-05-13 18:45:06 +01:00
# That's it for the table of examples, so terminate the table.
2018-11-06 12:30:43 -08:00
#
2020-05-13 18:45:06 +01:00
f . write ( " </table> \n " )
2018-11-06 12:30:43 -08:00
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
# And that's it for the report, so finish up.
2009-09-30 20:26:33 -07:00
#
2020-05-13 18:45:06 +01:00
f . write ( " </body> \n " )
f . write ( " </html> \n " )
2009-09-12 19:44:17 -07:00
2018-11-06 12:30:43 -08:00
print ( ' done. ' )
2018-12-27 12:24:03 +03:00
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# Python Control-C handling is broken in the presence of multiple threads.
# Signals get delivered to the runnable/running thread by default and if
# it is blocked, the signal is simply ignored. So we hook sigint and set
2009-09-12 19:44:17 -07:00
# a global variable telling the system to shut down gracefully.
#
thread_exit = False
def sigint_hook ( signal , frame ) :
global thread_exit
thread_exit = True
return 0
#
# In general, the build process itself naturally takes care of figuring out
# which tests are built into the test runner. For example, if waf configure
# determines that ENABLE_EMU is false due to some missing dependency,
2018-12-27 12:24:03 +03:00
# the tests for the emu net device simply will not be built and will
2009-09-12 19:44:17 -07:00
# therefore not be included in the built test runner.
#
# Examples, however, are a different story. In that case, we are just given
# a list of examples that could be run. Instead of just failing, for example,
2021-12-02 21:30:16 -08:00
# an example if its library support is not present, we look into the waf
# saved configuration for relevant configuration items.
2009-09-12 19:44:17 -07:00
#
# XXX This function pokes around in the waf internal state file. To be a
2018-06-27 10:50:27 +03:00
# little less hacky, we should add a command to waf to return this info
2009-09-12 19:44:17 -07:00
# and use that result.
#
def read_waf_config ( ) :
2019-08-12 16:55:34 -07:00
f = None
try :
# sys.platform reports linux2 for python2 and linux for python3
f = open ( " .lock-waf_ " + sys . platform + " _build " , " rt " )
except FileNotFoundError :
try :
f = open ( " .lock-waf_linux2_build " , " rt " )
except FileNotFoundError :
print ( ' The .lock-waf ... directory was not found. You must do waf build before running test.py. ' , file = sys . stderr )
sys . exit ( 2 )
2020-01-09 14:05:40 +01:00
2019-08-12 16:55:34 -07:00
for line in f :
2012-02-17 11:46:13 -08:00
if line . startswith ( " top_dir = " ) :
key , val = line . split ( ' = ' )
top_dir = eval ( val . strip ( ) )
2011-09-12 14:54:27 +01:00
if line . startswith ( " out_dir = " ) :
key , val = line . split ( ' = ' )
out_dir = eval ( val . strip ( ) )
2020-05-13 18:45:06 +01:00
f . close ( )
2012-02-17 11:46:13 -08:00
global NS3_BASEDIR
NS3_BASEDIR = top_dir
2011-09-12 14:54:27 +01:00
global NS3_BUILDDIR
NS3_BUILDDIR = out_dir
2020-05-13 18:45:06 +01:00
with open ( " %s /c4che/_cache.py " % out_dir ) as f :
for line in f . readlines ( ) :
for item in interesting_config_items :
if line . startswith ( item ) :
exec ( line , globals ( ) )
2009-09-12 19:44:17 -07:00
if options . verbose :
for item in interesting_config_items :
2015-09-03 21:14:55 -07:00
print ( " %s == " % item , eval ( item ) )
2009-09-12 19:44:17 -07:00
#
# It seems pointless to fork a process to run waf to fork a process to run
2018-12-27 12:24:03 +03:00
# the test runner, so we just run the test runner directly. The main thing
2009-09-12 19:44:17 -07:00
# that waf would do for us would be to sort out the shared library path but
# we can deal with that easily and do here.
#
2018-12-27 12:24:03 +03:00
# There can be many different ns-3 repositories on a system, and each has
2009-09-12 19:44:17 -07:00
# its own shared libraries, so ns-3 doesn't hardcode a shared library search
# path -- it is cooked up dynamically, so we do that too.
#
2010-04-16 14:58:56 -07:00
def make_paths ( ) :
2009-10-26 23:44:04 -07:00
have_DYLD_LIBRARY_PATH = False
have_LD_LIBRARY_PATH = False
have_PATH = False
2010-04-16 14:58:56 -07:00
have_PYTHONPATH = False
2009-10-26 23:44:04 -07:00
2015-09-03 21:14:55 -07:00
keys = list ( os . environ . keys ( ) )
2009-10-26 23:44:04 -07:00
for key in keys :
if key == " DYLD_LIBRARY_PATH " :
have_DYLD_LIBRARY_PATH = True
if key == " LD_LIBRARY_PATH " :
have_LD_LIBRARY_PATH = True
if key == " PATH " :
have_PATH = True
2010-04-16 14:58:56 -07:00
if key == " PYTHONPATH " :
have_PYTHONPATH = True
2018-12-27 12:59:23 +03:00
pypath = os . environ [ " PYTHONPATH " ] = os . path . join ( NS3_BUILDDIR , " bindings " , " python " )
2010-04-16 14:58:56 -07:00
if not have_PYTHONPATH :
os . environ [ " PYTHONPATH " ] = pypath
else :
os . environ [ " PYTHONPATH " ] + = " : " + pypath
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " os.environ[ \" PYTHONPATH \" ] == %s " % os . environ [ " PYTHONPATH " ] )
2009-09-12 19:44:17 -07:00
if sys . platform == " darwin " :
2009-10-26 23:44:04 -07:00
if not have_DYLD_LIBRARY_PATH :
os . environ [ " DYLD_LIBRARY_PATH " ] = " "
for path in NS3_MODULE_PATH :
os . environ [ " DYLD_LIBRARY_PATH " ] + = " : " + path
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " os.environ[ \" DYLD_LIBRARY_PATH \" ] == %s " % os . environ [ " DYLD_LIBRARY_PATH " ] )
2009-09-12 19:44:17 -07:00
elif sys . platform == " win32 " :
2009-10-26 23:44:04 -07:00
if not have_PATH :
os . environ [ " PATH " ] = " "
for path in NS3_MODULE_PATH :
os . environ [ " PATH " ] + = ' ; ' + path
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " os.environ[ \" PATH \" ] == %s " % os . environ [ " PATH " ] )
2009-09-12 19:44:17 -07:00
elif sys . platform == " cygwin " :
2009-10-26 23:44:04 -07:00
if not have_PATH :
os . environ [ " PATH " ] = " "
for path in NS3_MODULE_PATH :
os . environ [ " PATH " ] + = " : " + path
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " os.environ[ \" PATH \" ] == %s " % os . environ [ " PATH " ] )
2009-10-26 23:44:04 -07:00
else :
if not have_LD_LIBRARY_PATH :
os . environ [ " LD_LIBRARY_PATH " ] = " "
for path in NS3_MODULE_PATH :
2015-09-03 21:14:55 -07:00
os . environ [ " LD_LIBRARY_PATH " ] + = " : " + str ( path )
2009-10-26 23:44:04 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " os.environ[ \" LD_LIBRARY_PATH \" ] == %s " % os . environ [ " LD_LIBRARY_PATH " ] )
2009-09-28 17:18:12 -07:00
2010-01-13 10:30:56 +01:00
#
# Short note on generating suppressions:
#
# See the valgrind documentation for a description of suppressions. The easiest
2018-12-27 12:24:03 +03:00
# way to generate a suppression expression is by using the valgrind
# --gen-suppressions option. To do that you have to figure out how to run the
2010-01-13 10:30:56 +01:00
# test in question.
#
# If you do "test.py -v -g -s <suitename> then test.py will output most of what
# you need. For example, if you are getting a valgrind error in the
# devices-mesh-dot11s-regression test suite, you can run:
#
2018-12-27 12:24:03 +03:00
# ./test.py -v -g -s devices-mesh-dot11s-regression
2010-01-13 10:30:56 +01:00
#
# You should see in the verbose output something that looks like:
#
# Synchronously execute valgrind --suppressions=/home/craigdo/repos/ns-3-allinone-dev/ns-3-dev/testpy.supp
2018-12-27 12:24:03 +03:00
# --leak-check=full --error-exitcode=2 /home/craigdo/repos/ns-3-allinone-dev/ns-3-dev/build/debug/utils/ns3-dev-test-runner-debug
# --suite=devices-mesh-dot11s-regression --basedir=/home/craigdo/repos/ns-3-allinone-dev/ns-3-dev
# --tempdir=testpy-output/2010-01-12-22-47-50-CUT
2010-01-13 10:30:56 +01:00
# --out=testpy-output/2010-01-12-22-47-50-CUT/devices-mesh-dot11s-regression.xml
#
2018-12-27 12:24:03 +03:00
# You need to pull out the useful pieces, and so could run the following to
2010-01-13 10:30:56 +01:00
# reproduce your error:
#
# valgrind --suppressions=/home/craigdo/repos/ns-3-allinone-dev/ns-3-dev/testpy.supp
2018-12-27 12:24:03 +03:00
# --leak-check=full --error-exitcode=2 /home/craigdo/repos/ns-3-allinone-dev/ns-3-dev/build/debug/utils/ns3-dev-test-runner-debug
# --suite=devices-mesh-dot11s-regression --basedir=/home/craigdo/repos/ns-3-allinone-dev/ns-3-dev
# --tempdir=testpy-output
2010-01-13 10:30:56 +01:00
#
2018-12-27 12:24:03 +03:00
# Hint: Use the first part of the command as is, and point the "tempdir" to
2010-01-13 10:30:56 +01:00
# somewhere real. You don't need to specify an "out" file.
#
2018-12-27 12:24:03 +03:00
# When you run the above command you should see your valgrind error. The
2010-01-13 10:30:56 +01:00
# suppression expression(s) can be generated by adding the --gen-suppressions=yes
# option to valgrind. Use something like:
#
# valgrind --gen-suppressions=yes --suppressions=/home/craigdo/repos/ns-3-allinone-dev/ns-3-dev/testpy.supp
2018-12-27 12:24:03 +03:00
# --leak-check=full --error-exitcode=2 /home/craigdo/repos/ns-3-allinone-dev/ns-3-dev/build/debug/utils/ns3-dev-test-runner-debug
# --suite=devices-mesh-dot11s-regression --basedir=/home/craigdo/repos/ns-3-allinone-dev/ns-3-dev
# --tempdir=testpy-output
2010-01-13 10:30:56 +01:00
#
# Now when valgrind detects an error it will ask:
#
# ==27235== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ----
#
# to which you just enter 'y'<ret>.
#
# You will be provided with a suppression expression that looks something like
# the following:
# {
# <insert_a_suppression_name_here>
# Memcheck:Addr8
# fun:_ZN3ns36dot11s15HwmpProtocolMac8SendPreqESt6vectorINS0_6IePreqESaIS3_EE
# fun:_ZN3ns36dot11s15HwmpProtocolMac10SendMyPreqEv
# fun:_ZN3ns36dot11s15HwmpProtocolMac18RequestDestinationENS_12Mac48AddressEjj
# ...
# the rest of the stack frame
# ...
# }
#
2018-12-27 12:24:03 +03:00
# You need to add a supression name which will only be printed out by valgrind in
2010-01-13 10:30:56 +01:00
# verbose mode (but it needs to be there in any case). The entire stack frame is
2018-12-27 12:24:03 +03:00
# shown to completely characterize the error, but in most cases you won't need
2010-01-13 10:30:56 +01:00
# all of that info. For example, if you want to turn off all errors that happen
# when the function (fun:) is called, you can just delete the rest of the stack
# frame. You can also use wildcards to make the mangled signatures more readable.
#
# I added the following to the testpy.supp file for this particular error:
#
# {
2018-06-27 10:50:27 +03:00
# Suppress invalid read size errors in SendPreq() when using HwmpProtocolMac
2010-01-13 10:30:56 +01:00
# Memcheck:Addr8
# fun:*HwmpProtocolMac*SendPreq*
# }
#
# Now, when you run valgrind the error will be suppressed.
#
VALGRIND_SUPPRESSIONS_FILE = " testpy.supp "
2011-04-26 12:53:50 -07:00
def run_job_synchronously ( shell_command , directory , valgrind , is_python , build_path = " " ) :
2018-12-27 12:59:23 +03:00
suppressions_path = os . path . join ( NS3_BASEDIR , VALGRIND_SUPPRESSIONS_FILE )
2010-04-15 10:53:40 -07:00
if is_python :
2018-12-27 12:59:23 +03:00
path_cmd = PYTHON [ 0 ] + " " + os . path . join ( NS3_BASEDIR , shell_command )
2010-04-15 10:53:40 -07:00
else :
2011-04-26 12:53:50 -07:00
if len ( build_path ) :
2018-12-27 12:59:23 +03:00
path_cmd = os . path . join ( build_path , shell_command )
2011-04-26 12:53:50 -07:00
else :
2018-12-27 12:59:23 +03:00
path_cmd = os . path . join ( NS3_BUILDDIR , shell_command )
2010-04-15 10:53:40 -07:00
2009-10-06 22:01:40 -07:00
if valgrind :
2017-05-24 18:41:21 +03:00
cmd = " valgrind --suppressions= %s --leak-check=full --show-reachable=yes --error-exitcode=2 --errors-for-leak-kinds=all %s " % ( suppressions_path ,
2010-01-19 16:56:44 +01:00
path_cmd )
2009-10-06 22:01:40 -07:00
else :
2009-10-26 23:44:04 -07:00
cmd = path_cmd
2009-10-06 22:01:40 -07:00
2009-09-12 19:44:17 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Synchronously execute %s " % cmd )
2009-10-06 22:01:40 -07:00
2009-10-27 00:19:02 -07:00
start_time = time . time ( )
2018-12-27 12:59:23 +03:00
proc = subprocess . Popen ( cmd , shell = True , cwd = directory , stdout = subprocess . PIPE , stderr = subprocess . PIPE )
2010-01-15 17:48:18 +01:00
stdout_results , stderr_results = proc . communicate ( )
2010-01-19 16:56:44 +01:00
elapsed_time = time . time ( ) - start_time
2010-01-15 17:48:18 +01:00
retval = proc . returncode
2015-10-30 14:58:58 -07:00
try :
stdout_results = stdout_results . decode ( )
except UnicodeDecodeError :
print ( " Non-decodable character in stdout output of %s " % cmd )
print ( stdout_results )
retval = 1
try :
stderr_results = stderr_results . decode ( )
except UnicodeDecodeError :
print ( " Non-decodable character in stderr output of %s " % cmd )
print ( stderr_results )
retval = 1
2010-01-19 16:56:44 +01:00
2009-10-26 23:44:04 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Return code = " , retval )
print ( " stderr = " , stderr_results )
2009-10-26 23:44:04 -07:00
2010-01-15 17:48:18 +01:00
return ( retval , stdout_results , stderr_results , elapsed_time )
2009-09-12 19:44:17 -07:00
#
# This class defines a unit of testing work. It will typically refer to
# a test suite to run using the test-runner, or an example to run directly.
#
2009-10-13 10:23:21 -07:00
class Job :
2009-09-12 19:44:17 -07:00
def __init__ ( self ) :
self . is_break = False
2009-10-09 12:54:54 -07:00
self . is_skip = False
2018-11-06 12:30:43 -08:00
self . skip_reason = " "
2009-09-12 19:44:17 -07:00
self . is_example = False
2010-04-15 10:53:40 -07:00
self . is_pyexample = False
2009-09-12 19:44:17 -07:00
self . shell_command = " "
self . display_name = " "
2009-10-09 12:54:54 -07:00
self . basedir = " "
2009-11-05 19:14:37 -08:00
self . tempdir = " "
2009-09-12 19:44:17 -07:00
self . cwd = " "
self . tmp_file_name = " "
self . returncode = False
2009-10-26 23:44:04 -07:00
self . elapsed_time = 0
2011-04-26 12:53:50 -07:00
self . build_path = " "
2009-09-12 19:44:17 -07:00
#
# A job is either a standard job or a special job indicating that a worker
2018-12-27 12:24:03 +03:00
# thread should exist. This special job is indicated by setting is_break
2009-09-12 19:44:17 -07:00
# to true.
#
def set_is_break ( self , is_break ) :
self . is_break = is_break
2009-10-09 12:54:54 -07:00
#
# If a job is to be skipped, we actually run it through the worker threads
# to keep the PASS, FAIL, CRASH and SKIP processing all in one place.
#
def set_is_skip ( self , is_skip ) :
self . is_skip = is_skip
2018-11-06 12:30:43 -08:00
#
# If a job is to be skipped, log the reason.
#
def set_skip_reason ( self , skip_reason ) :
self . skip_reason = skip_reason
2009-09-12 19:44:17 -07:00
#
# Examples are treated differently than standard test suites. This is
2018-12-27 12:24:03 +03:00
# mostly because they are completely unaware that they are being run as
2009-09-12 19:44:17 -07:00
# tests. So we have to do some special case processing to make them look
# like tests.
#
def set_is_example ( self , is_example ) :
self . is_example = is_example
2010-04-15 10:53:40 -07:00
#
# Examples are treated differently than standard test suites. This is
2018-12-27 12:24:03 +03:00
# mostly because they are completely unaware that they are being run as
2010-04-15 10:53:40 -07:00
# tests. So we have to do some special case processing to make them look
# like tests.
#
def set_is_pyexample ( self , is_pyexample ) :
self . is_pyexample = is_pyexample
2009-09-12 19:44:17 -07:00
#
# This is the shell command that will be executed in the job. For example,
#
2012-01-13 10:17:39 -08:00
# "utils/ns3-dev-test-runner-debug --test-name=some-test-suite"
2009-09-12 19:44:17 -07:00
#
def set_shell_command ( self , shell_command ) :
self . shell_command = shell_command
2011-04-26 12:53:50 -07:00
#
# This is the build path where ns-3 was built. For example,
#
# "/home/craigdo/repos/ns-3-allinone-test/ns-3-dev/build/debug"
#
def set_build_path ( self , build_path ) :
self . build_path = build_path
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# This is the display name of the job, typically the test suite or example
2009-09-12 19:44:17 -07:00
# name. For example,
#
# "some-test-suite" or "udp-echo"
#
def set_display_name ( self , display_name ) :
self . display_name = display_name
#
# This is the base directory of the repository out of which the tests are
# being run. It will be used deep down in the testing framework to determine
2018-12-27 12:24:03 +03:00
# where the source directory of the test was, and therefore where to find
2009-09-12 19:44:17 -07:00
# provided test vectors. For example,
#
# "/home/user/repos/ns-3-dev"
#
def set_basedir ( self , basedir ) :
self . basedir = basedir
2009-11-05 19:14:37 -08:00
#
2018-12-27 12:24:03 +03:00
# This is the directory to which a running test suite should write any
2009-11-05 19:14:37 -08:00
# temporary files.
#
def set_tempdir ( self , tempdir ) :
self . tempdir = tempdir
2009-09-12 19:44:17 -07:00
#
# This is the current working directory that will be given to an executing
# test as it is being run. It will be used for examples to tell them where
# to write all of the pcap files that we will be carefully ignoring. For
# example,
#
# "/tmp/unchecked-traces"
#
def set_cwd ( self , cwd ) :
self . cwd = cwd
#
2018-12-27 12:24:03 +03:00
# This is the temporary results file name that will be given to an executing
2009-09-12 19:44:17 -07:00
# test as it is being run. We will be running all of our tests in parallel
# so there must be multiple temporary output files. These will be collected
2018-12-27 12:24:03 +03:00
# into a single XML file at the end and then be deleted.
2009-09-12 19:44:17 -07:00
#
def set_tmp_file_name ( self , tmp_file_name ) :
self . tmp_file_name = tmp_file_name
#
# The return code received when the job process is executed.
#
def set_returncode ( self , returncode ) :
self . returncode = returncode
2009-10-26 23:44:04 -07:00
#
# The elapsed real time for the job execution.
#
def set_elapsed_time ( self , elapsed_time ) :
self . elapsed_time = elapsed_time
2009-09-12 19:44:17 -07:00
#
# The worker thread class that handles the actual running of a given test.
# Once spawned, it receives requests for work through its input_queue and
# ships the results back through the output_queue.
#
class worker_thread ( threading . Thread ) :
def __init__ ( self , input_queue , output_queue ) :
threading . Thread . __init__ ( self )
self . input_queue = input_queue
self . output_queue = output_queue
def run ( self ) :
while True :
job = self . input_queue . get ( )
#
# Worker threads continue running until explicitly told to stop with
# a special job.
#
if job . is_break :
return
#
# If the global interrupt handler sets the thread_exit variable,
# we stop doing real work and just report back a "break" in the
# normal command processing has happened.
#
if thread_exit == True :
job . set_is_break ( True )
self . output_queue . put ( job )
continue
2009-10-09 12:54:54 -07:00
#
# If we are actually supposed to skip this job, do so. Note that
# if is_skip is true, returncode is undefined.
#
if job . is_skip :
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Skip %s " % job . shell_command )
2009-10-09 12:54:54 -07:00
self . output_queue . put ( job )
2010-04-19 19:41:00 -07:00
continue
2009-10-09 12:54:54 -07:00
2009-09-12 19:44:17 -07:00
#
# Otherwise go about the business of running tests as normal.
#
else :
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Launch %s " % job . shell_command )
2009-09-12 19:44:17 -07:00
2010-04-15 10:53:40 -07:00
if job . is_example or job . is_pyexample :
2009-09-12 19:44:17 -07:00
#
# If we have an example, the shell command is all we need to
2018-12-27 12:24:03 +03:00
# know. It will be something like "examples/udp/udp-echo" or
2012-04-02 06:57:07 -07:00
# "examples/wireless/mixed-wireless.py"
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
( job . returncode , standard_out , standard_err , et ) = run_job_synchronously ( job . shell_command ,
2011-04-26 12:53:50 -07:00
job . cwd , options . valgrind , job . is_pyexample , job . build_path )
2009-09-12 19:44:17 -07:00
else :
#
# If we're a test suite, we need to provide a little more info
# to the test runner, specifically the base directory and temp
# file name
#
2011-07-29 03:38:59 -04:00
if options . update_data :
update_data = ' --update-data '
else :
update_data = ' '
2018-12-27 12:24:03 +03:00
( job . returncode , standard_out , standard_err , et ) = run_job_synchronously ( job . shell_command +
" --xml --tempdir= %s --out= %s %s " % ( job . tempdir , job . tmp_file_name , update_data ) ,
2010-04-15 10:53:40 -07:00
job . cwd , options . valgrind , False )
2009-09-12 19:44:17 -07:00
2009-10-26 23:44:04 -07:00
job . set_elapsed_time ( et )
2009-09-12 19:44:17 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " returncode = %d " % job . returncode )
print ( " ---------- begin standard out ---------- " )
print ( standard_out )
print ( " ---------- begin standard err ---------- " )
print ( standard_err )
print ( " ---------- end standard err ---------- " )
2009-09-12 19:44:17 -07:00
self . output_queue . put ( job )
#
2012-01-13 10:17:39 -08:00
# This is the main function that does the work of interacting with the
# test-runner itself.
2009-09-12 19:44:17 -07:00
#
def run_tests ( ) :
2012-01-13 10:17:39 -08:00
#
# Pull some interesting configuration information out of waf, primarily
# so we can know where executables can be found, but also to tell us what
2018-12-27 12:24:03 +03:00
# pieces of the system have been built. This will tell us what examples
2012-01-13 10:17:39 -08:00
# are runnable.
#
read_waf_config ( )
2013-06-19 11:17:17 -07:00
#
# Set the proper suffix.
#
2013-06-19 13:55:49 -07:00
global BUILD_PROFILE_SUFFIX
2018-12-27 12:24:03 +03:00
if BUILD_PROFILE == ' release ' :
2013-06-19 11:17:17 -07:00
BUILD_PROFILE_SUFFIX = " "
else :
BUILD_PROFILE_SUFFIX = " - " + BUILD_PROFILE
2012-01-13 10:17:39 -08:00
#
# Add the proper prefix and suffix to the test-runner name to
# match what is done in the wscript file.
#
2013-06-19 11:17:17 -07:00
test_runner_name = " %s %s - %s %s " % ( APPNAME , VERSION , " test-runner " , BUILD_PROFILE_SUFFIX )
2012-01-13 10:17:39 -08:00
2009-09-12 19:44:17 -07:00
#
# Run waf to make sure that everything is built, configured and ready to go
2009-10-06 19:34:29 -07:00
# unless we are explicitly told not to. We want to be careful about causing
# our users pain while waiting for extraneous stuff to compile and link, so
# we allow users that know what they''re doing to not invoke waf at all.
2009-09-12 19:44:17 -07:00
#
2009-10-06 19:34:29 -07:00
if not options . nowaf :
#
2018-12-27 12:24:03 +03:00
# If the user is running the "kinds" or "list" options, there is an
2009-10-06 19:34:29 -07:00
# implied dependency on the test-runner since we call that program
# if those options are selected. We will exit after processing those
# options, so if we see them, we can safely only build the test-runner.
#
# If the user has constrained us to running only a particular type of
# file, we can only ask waf to build what we know will be necessary.
# For example, if the user only wants to run BVT tests, we only have
# to build the test-runner and can ignore all of the examples.
#
2009-10-30 10:23:40 -07:00
# If the user only wants to run a single example, then we can just build
# that example.
#
# If there is no constraint, then we have to build everything since the
# user wants to run everything.
#
2009-10-06 19:34:29 -07:00
if options . kinds or options . list or ( len ( options . constrain ) and options . constrain in core_kinds ) :
2009-10-30 10:23:40 -07:00
if sys . platform == " win32 " :
2019-08-12 16:55:34 -07:00
waf_cmd = " ./waf --target=test-runner "
2009-10-30 10:23:40 -07:00
else :
2019-08-12 16:55:34 -07:00
waf_cmd = " ./waf --target=test-runner "
2009-10-30 10:23:40 -07:00
elif len ( options . example ) :
2015-09-03 21:14:55 -07:00
if sys . platform == " win32 " : #Modify for windows
2019-08-12 16:55:34 -07:00
waf_cmd = " ./waf --target= %s " % os . path . basename ( options . example )
2009-10-30 10:23:40 -07:00
else :
2019-08-12 16:55:34 -07:00
waf_cmd = " ./waf --target= %s " % os . path . basename ( options . example )
2009-10-06 19:34:29 -07:00
else :
2015-09-03 21:14:55 -07:00
if sys . platform == " win32 " : #Modify for windows
2019-08-12 16:55:34 -07:00
waf_cmd = " ./waf "
2009-10-30 10:23:40 -07:00
else :
2019-08-12 16:55:34 -07:00
waf_cmd = " ./waf "
2009-10-30 10:23:40 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Building: %s " % waf_cmd )
2009-10-06 19:34:29 -07:00
2009-10-30 10:23:40 -07:00
proc = subprocess . Popen ( waf_cmd , shell = True )
2009-09-12 19:44:17 -07:00
proc . communicate ( )
2010-05-22 09:33:38 -07:00
if proc . returncode :
2015-09-03 21:14:55 -07:00
print ( " Waf died. Not running tests " , file = sys . stderr )
2010-05-22 09:33:38 -07:00
return proc . returncode
2009-09-12 19:44:17 -07:00
2015-09-03 21:14:55 -07:00
2009-09-12 19:44:17 -07:00
#
2012-01-13 10:17:39 -08:00
# Dynamically set up paths.
2009-09-12 19:44:17 -07:00
#
2010-04-16 14:58:56 -07:00
make_paths ( )
2009-09-12 19:44:17 -07:00
2012-09-14 11:48:14 -07:00
#
2011-04-29 09:53:35 -07:00
# Get the information from the build status file.
2012-09-14 11:48:14 -07:00
#
2018-12-27 12:59:23 +03:00
build_status_file = os . path . join ( NS3_BUILDDIR , ' build-status.py ' )
2011-04-29 09:53:35 -07:00
if os . path . exists ( build_status_file ) :
ns3_runnable_programs = get_list_from_file ( build_status_file , " ns3_runnable_programs " )
ns3_runnable_scripts = get_list_from_file ( build_status_file , " ns3_runnable_scripts " )
else :
2015-09-03 21:14:55 -07:00
print ( ' The build status file was not found. You must do waf build before running test.py. ' , file = sys . stderr )
2011-04-29 09:53:35 -07:00
sys . exit ( 2 )
2012-09-14 11:48:14 -07:00
#
# Make a dictionary that maps the name of a program to its path.
#
ns3_runnable_programs_dictionary = { }
for program in ns3_runnable_programs :
# Remove any directory names from path.
program_name = os . path . basename ( program )
ns3_runnable_programs_dictionary [ program_name ] = program
2011-03-09 16:49:59 -08:00
# Generate the lists of examples to run as smoke tests in order to
# ensure that they remain buildable and runnable over time.
#
example_tests = [ ]
2013-01-14 09:39:06 -08:00
example_names_original = [ ]
2011-03-09 16:49:59 -08:00
python_tests = [ ]
for directory in EXAMPLE_DIRECTORIES :
2018-12-27 12:24:03 +03:00
# Set the directories and paths for this example.
2011-03-09 16:49:59 -08:00
example_directory = os . path . join ( " examples " , directory )
examples_to_run_path = os . path . join ( example_directory , " examples-to-run.py " )
2011-09-12 14:54:27 +01:00
cpp_executable_dir = os . path . join ( NS3_BUILDDIR , example_directory )
2011-03-09 16:49:59 -08:00
python_script_dir = os . path . join ( example_directory )
# Parse this example directory's file.
parse_examples_to_run_file (
examples_to_run_path ,
cpp_executable_dir ,
python_script_dir ,
example_tests ,
2013-01-14 09:39:06 -08:00
example_names_original ,
2011-03-09 16:49:59 -08:00
python_tests )
for module in NS3_ENABLED_MODULES :
# Remove the "ns3-" from the module name.
module = module [ len ( " ns3- " ) : ]
2018-12-27 12:24:03 +03:00
# Set the directories and paths for this example.
2011-03-09 16:49:59 -08:00
module_directory = os . path . join ( " src " , module )
example_directory = os . path . join ( module_directory , " examples " )
examples_to_run_path = os . path . join ( module_directory , " test " , " examples-to-run.py " )
2011-09-12 14:54:27 +01:00
cpp_executable_dir = os . path . join ( NS3_BUILDDIR , example_directory )
2011-03-09 16:49:59 -08:00
python_script_dir = os . path . join ( example_directory )
# Parse this module's file.
parse_examples_to_run_file (
examples_to_run_path ,
cpp_executable_dir ,
python_script_dir ,
example_tests ,
2013-01-14 09:39:06 -08:00
example_names_original ,
2011-03-09 16:49:59 -08:00
python_tests )
2018-12-27 12:24:03 +03:00
2017-04-06 20:32:04 -07:00
for module in NS3_ENABLED_CONTRIBUTED_MODULES :
# Remove the "ns3-" from the module name.
module = module [ len ( " ns3- " ) : ]
2018-12-27 12:24:03 +03:00
# Set the directories and paths for this example.
2017-04-06 20:32:04 -07:00
module_directory = os . path . join ( " contrib " , module )
example_directory = os . path . join ( module_directory , " examples " )
examples_to_run_path = os . path . join ( module_directory , " test " , " examples-to-run.py " )
cpp_executable_dir = os . path . join ( NS3_BUILDDIR , example_directory )
python_script_dir = os . path . join ( example_directory )
# Parse this module's file.
parse_examples_to_run_file (
examples_to_run_path ,
cpp_executable_dir ,
python_script_dir ,
example_tests ,
example_names_original ,
python_tests )
2011-03-09 16:49:59 -08:00
2010-02-26 09:34:54 -08:00
#
2018-12-27 12:24:03 +03:00
# If lots of logging is enabled, we can crash Python when it tries to
2010-02-26 09:34:54 -08:00
# save all of the text. We just don't allow logging to be turned on when
# test.py runs. If you want to see logging output from your tests, you
# have to run them using the test-runner directly.
#
os . environ [ " NS_LOG " ] = " "
2009-09-12 19:44:17 -07:00
#
# There are a couple of options that imply we can to exit before starting
2018-12-27 12:24:03 +03:00
# up a bunch of threads and running tests. Let's detect these cases and
2009-09-12 19:44:17 -07:00
# handle them without doing all of the hard work.
#
if options . kinds :
2012-01-13 10:17:39 -08:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-type-list " )
2010-04-15 10:53:40 -07:00
( rc , standard_out , standard_err , et ) = run_job_synchronously ( path_cmd , os . getcwd ( ) , False , False )
2020-01-09 14:04:35 +01:00
print ( standard_out )
2009-09-12 19:44:17 -07:00
if options . list :
2012-09-11 15:29:26 -07:00
if len ( options . constrain ) :
2012-09-12 14:59:21 -07:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-name-list --print-test-types --test-type= %s " % options . constrain )
2012-09-11 15:29:26 -07:00
else :
2012-09-12 14:59:21 -07:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-name-list --print-test-types " )
2010-04-15 10:53:40 -07:00
( rc , standard_out , standard_err , et ) = run_job_synchronously ( path_cmd , os . getcwd ( ) , False , False )
2014-06-30 11:09:35 -07:00
if rc != 0 :
# This is usually a sign that ns-3 crashed or exited uncleanly
2015-09-03 21:14:55 -07:00
print ( ( ' test.py error: test-runner return code returned {} ' . format ( rc ) ) )
print ( ( ' To debug, try running {} \n ' . format ( ' \' ./waf --run \" test-runner --print-test-name-list \" \' ' ) ) )
2014-06-30 11:09:35 -07:00
return
2015-09-03 21:14:55 -07:00
if isinstance ( standard_out , bytes ) :
standard_out = standard_out . decode ( )
2012-07-23 17:45:28 -07:00
list_items = standard_out . split ( ' \n ' )
2012-09-12 14:59:21 -07:00
list_items . sort ( )
2015-09-03 21:14:55 -07:00
print ( " Test Type Test Name " )
print ( " --------- --------- " )
2012-09-12 14:59:21 -07:00
for item in list_items :
if len ( item . strip ( ) ) :
2015-09-03 21:14:55 -07:00
print ( item )
2013-01-14 09:39:06 -08:00
example_names_original . sort ( )
for item in example_names_original :
2015-09-03 21:14:55 -07:00
print ( " example " , item )
print ( )
2009-09-12 19:44:17 -07:00
if options . kinds or options . list :
return
#
2018-12-27 12:24:03 +03:00
# We communicate results in two ways. First, a simple message relating
# PASS, FAIL, CRASH or SKIP is always written to the standard output. It
2009-10-09 12:54:54 -07:00
# is expected that this will be one of the main use cases. A developer can
2018-12-27 12:24:03 +03:00
# just run test.py with no options and see that all of the tests still
2009-09-12 19:44:17 -07:00
# pass.
#
# The second main use case is when detailed status is requested (with the
2018-06-27 10:50:27 +03:00
# --text or --html options). Typically this will be text if a developer
2009-09-12 19:44:17 -07:00
# finds a problem, or HTML for nightly builds. In these cases, an
# XML file is written containing the status messages from the test suites.
# This file is then read and translated into text or HTML. It is expected
2009-10-12 14:01:36 -07:00
# that nobody will really be interested in the XML, so we write it somewhere
# with a unique name (time) to avoid collisions. In case an error happens, we
# provide a runtime option to retain the temporary files.
2009-09-12 19:44:17 -07:00
#
# When we run examples as smoke tests, they are going to want to create
# lots and lots of trace files. We aren't really interested in the contents
2009-10-12 14:01:36 -07:00
# of the trace files, so we also just stash them off in the temporary dir.
# The retain option also causes these unchecked trace files to be kept.
2009-09-12 19:44:17 -07:00
#
2009-10-12 14:01:36 -07:00
date_and_time = time . strftime ( " % Y- % m- %d - % H- % M- % S-CUT " , time . gmtime ( ) )
2009-09-12 19:44:17 -07:00
if not os . path . exists ( TMP_OUTPUT_DIR ) :
os . makedirs ( TMP_OUTPUT_DIR )
2009-10-12 14:01:36 -07:00
testpy_output_dir = os . path . join ( TMP_OUTPUT_DIR , date_and_time ) ;
if not os . path . exists ( testpy_output_dir ) :
os . makedirs ( testpy_output_dir )
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# Create the main output file and start filling it with XML. We need to
2009-09-12 19:44:17 -07:00
# do this since the tests will just append individual results to this file.
#
2009-10-12 14:01:36 -07:00
xml_results_file = os . path . join ( testpy_output_dir , " results.xml " )
2020-05-13 18:45:06 +01:00
with open ( xml_results_file , ' w ' ) as f :
f . write ( ' <?xml version= " 1.0 " ?> \n ' )
f . write ( ' <Results> \n ' )
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# We need to figure out what test suites to execute. We are either given one
2010-04-15 10:53:40 -07:00
# suite or example explicitly via the --suite or --example/--pyexample option,
# or we need to call into the test runner and ask it to list all of the available
2009-09-12 19:44:17 -07:00
# test suites. Further, we need to provide the constraint information if it
# has been given to us.
2018-12-27 12:24:03 +03:00
#
# This translates into allowing the following options with respect to the
2009-09-12 19:44:17 -07:00
# suites
#
2009-10-06 19:34:29 -07:00
# ./test,py: run all of the suites and examples
# ./test.py --constrain=core: run all of the suites of all kinds
2009-09-12 19:44:17 -07:00
# ./test.py --constrain=unit: run all unit suites
2012-04-02 06:57:07 -07:00
# ./test.py --suite=some-test-suite: run a single suite
# ./test.py --example=examples/udp/udp-echo: run single example
# ./test.py --pyexample=examples/wireless/mixed-wireless.py: run python example
# ./test.py --suite=some-suite --example=some-example: run the single suite
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# We can also use the --constrain option to provide an ordering of test
2009-09-12 19:44:17 -07:00
# execution quite easily.
#
2016-08-02 14:17:01 -07:00
# Flag indicating a specific suite was explicitly requested
single_suite = False
2018-12-27 12:24:03 +03:00
2009-09-12 19:44:17 -07:00
if len ( options . suite ) :
2011-08-09 16:27:17 -07:00
# See if this is a valid test suite.
2012-01-13 10:17:39 -08:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-name-list " )
2011-08-09 16:27:17 -07:00
( rc , suites , standard_err , et ) = run_job_synchronously ( path_cmd , os . getcwd ( ) , False , False )
2020-01-09 14:03:13 +01:00
2015-09-03 21:14:55 -07:00
if isinstance ( suites , bytes ) :
suites = suites . decode ( )
2020-01-09 14:03:13 +01:00
suites_found = fnmatch . filter ( suites . split ( ' \n ' ) , options . suite )
if not suites_found :
2015-09-03 21:14:55 -07:00
print ( ' The test suite was not run because an unknown test suite name was requested. ' , file = sys . stderr )
2011-08-09 16:27:17 -07:00
sys . exit ( 2 )
2020-01-09 14:03:13 +01:00
elif len ( suites_found ) == 1 :
single_suite = True
suites = ' \n ' . join ( suites_found )
2011-08-09 16:27:17 -07:00
2010-04-15 10:53:40 -07:00
elif len ( options . example ) == 0 and len ( options . pyexample ) == 0 :
2009-09-12 19:44:17 -07:00
if len ( options . constrain ) :
2012-01-13 10:17:39 -08:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-name-list --test-type= %s " % options . constrain )
2010-04-15 10:53:40 -07:00
( rc , suites , standard_err , et ) = run_job_synchronously ( path_cmd , os . getcwd ( ) , False , False )
2009-09-12 19:44:17 -07:00
else :
2012-01-13 10:17:39 -08:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-name-list " )
2010-04-15 10:53:40 -07:00
( rc , suites , standard_err , et ) = run_job_synchronously ( path_cmd , os . getcwd ( ) , False , False )
2009-09-12 19:44:17 -07:00
else :
suites = " "
#
2018-12-27 12:24:03 +03:00
# suite_list will either a single test suite name that the user has
2009-09-12 19:44:17 -07:00
# indicated she wants to run or a list of test suites provided by
# the test-runner possibly according to user provided constraints.
2018-12-27 12:24:03 +03:00
# We go through the trouble of setting up the parallel execution
2016-08-02 14:17:01 -07:00
# even in the case of a single suite to avoid having to process the
2009-09-12 19:44:17 -07:00
# results in two different places.
#
2015-09-03 21:14:55 -07:00
if isinstance ( suites , bytes ) :
suites = suites . decode ( )
2009-09-12 19:44:17 -07:00
suite_list = suites . split ( ' \n ' )
#
2012-09-10 17:15:07 -07:00
# Performance tests should only be run when they are requested,
# i.e. they are not run by default in test.py.
2016-08-02 14:17:01 -07:00
# If a specific suite was requested we run it, even if
# it is a performance test.
if not single_suite and options . constrain != ' performance ' :
2012-09-10 17:15:07 -07:00
# Get a list of all of the performance tests.
path_cmd = os . path . join ( " utils " , test_runner_name + " --print-test-name-list --test-type= %s " % " performance " )
( rc , performance_tests , standard_err , et ) = run_job_synchronously ( path_cmd , os . getcwd ( ) , False , False )
2015-09-03 21:14:55 -07:00
if isinstance ( performance_tests , bytes ) :
performance_tests = performance_tests . decode ( )
2012-09-10 17:15:07 -07:00
performance_test_list = performance_tests . split ( ' \n ' )
# Remove any performance tests from the suites list.
for performance_test in performance_test_list :
if performance_test in suite_list :
suite_list . remove ( performance_test )
2009-09-12 19:44:17 -07:00
# We now have a possibly large number of test suites to run, so we want to
# run them in parallel. We're going to spin up a number of worker threads
# that will run our test jobs for us.
#
2015-09-03 21:14:55 -07:00
input_queue = queue . Queue ( 0 )
output_queue = queue . Queue ( 0 )
2009-09-12 19:44:17 -07:00
jobs = 0
threads = [ ]
2009-09-28 10:04:32 -07:00
#
# In Python 2.6 you can just use multiprocessing module, but we don't want
# to introduce that dependency yet; so we jump through a few hoops.
#
processors = 1
2009-10-26 23:44:04 -07:00
if sys . platform != " win32 " :
if ' SC_NPROCESSORS_ONLN ' in os . sysconf_names :
processors = os . sysconf ( ' SC_NPROCESSORS_ONLN ' )
else :
2018-12-27 12:59:23 +03:00
proc = subprocess . Popen ( " sysctl -n hw.ncpu " , shell = True , stdout = subprocess . PIPE , stderr = subprocess . PIPE )
2009-10-26 23:44:04 -07:00
stdout_results , stderr_results = proc . communicate ( )
2015-10-27 12:50:42 -07:00
stdout_results = stdout_results . decode ( )
stderr_results = stderr_results . decode ( )
2009-10-26 23:44:04 -07:00
if len ( stderr_results ) == 0 :
processors = int ( stdout_results )
2009-09-28 10:04:32 -07:00
2020-03-24 14:56:26 -07:00
if ( options . process_limit ) :
if ( processors < options . process_limit ) :
print ( ' Using all %s processors ' % processors )
else :
processors = options . process_limit
print ( ' Limiting to %s worker processes ' % processors )
2009-09-28 10:04:32 -07:00
#
# Now, spin up one thread per processor which will eventually mean one test
# per processor running concurrently.
#
2009-09-12 19:44:17 -07:00
for i in range ( processors ) :
thread = worker_thread ( input_queue , output_queue )
threads . append ( thread )
thread . start ( )
2009-10-09 12:54:54 -07:00
#
# Keep track of some summary statistics
#
total_tests = 0
skipped_tests = 0
2014-04-30 13:06:17 -07:00
skipped_testnames = [ ]
2009-10-09 12:54:54 -07:00
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# We now have worker threads spun up, and a list of work to do. So, run
2009-09-12 19:44:17 -07:00
# through the list of test suites and dispatch a job to run each one.
2018-12-27 12:24:03 +03:00
#
# Dispatching will run with unlimited speed and the worker threads will
2009-09-12 19:44:17 -07:00
# execute as fast as possible from the queue.
#
2018-12-27 12:24:03 +03:00
# Note that we actually dispatch tests to be skipped, so all of the
2009-10-09 12:54:54 -07:00
# PASS, FAIL, CRASH and SKIP processing is done in the same place.
#
2009-09-12 19:44:17 -07:00
for test in suite_list :
2009-10-27 01:05:46 -07:00
test = test . strip ( )
2009-09-12 19:44:17 -07:00
if len ( test ) :
job = Job ( )
job . set_is_example ( False )
2010-04-15 10:53:40 -07:00
job . set_is_pyexample ( False )
2009-09-12 19:44:17 -07:00
job . set_display_name ( test )
2009-10-12 14:01:36 -07:00
job . set_tmp_file_name ( os . path . join ( testpy_output_dir , " %s .xml " % test ) )
2009-09-12 19:44:17 -07:00
job . set_cwd ( os . getcwd ( ) )
job . set_basedir ( os . getcwd ( ) )
2009-11-05 19:14:37 -08:00
job . set_tempdir ( testpy_output_dir )
2009-09-30 20:26:33 -07:00
if ( options . multiple ) :
multiple = " "
2011-07-29 03:38:59 -04:00
else :
multiple = " --stop-on-failure "
2013-03-19 13:14:12 -07:00
if ( len ( options . fullness ) ) :
fullness = options . fullness . upper ( )
fullness = " --fullness= %s " % fullness
2013-03-14 14:54:45 -07:00
else :
2013-03-19 13:14:12 -07:00
fullness = " --fullness=QUICK "
2013-03-14 14:54:45 -07:00
2013-03-19 13:14:12 -07:00
path_cmd = os . path . join ( " utils " , test_runner_name + " --test-name= %s %s %s " % ( test , multiple , fullness ) )
2009-09-30 20:26:33 -07:00
2009-10-26 23:44:04 -07:00
job . set_shell_command ( path_cmd )
2009-09-12 19:44:17 -07:00
2009-10-09 12:54:54 -07:00
if options . valgrind and test in core_valgrind_skip_tests :
job . set_is_skip ( True )
2018-11-06 12:30:43 -08:00
job . set_skip_reason ( " crashes valgrind " )
2009-10-09 12:54:54 -07:00
2009-09-12 19:44:17 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Queue %s " % test )
2009-09-12 19:44:17 -07:00
input_queue . put ( job )
jobs = jobs + 1
2009-09-28 21:57:59 -07:00
total_tests = total_tests + 1
2018-12-27 12:24:03 +03:00
2009-09-12 19:44:17 -07:00
#
# We've taken care of the discovered or specified test suites. Now we
# have to deal with examples run as smoke tests. We have a list of all of
# the example programs it makes sense to try and run. Each example will
# have a condition associated with it that must evaluate to true for us
# to try and execute it. This is used to determine if the example has
2021-12-02 21:30:16 -08:00
# a dependency that is not satisfied.
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# We don't care at all how the trace files come out, so we just write them
2009-09-12 19:44:17 -07:00
# to a single temporary directory.
#
# XXX As it stands, all of the trace files have unique names, and so file
# collisions can only happen if two instances of an example are running in
# two versions of the test.py process concurrently. We may want to create
# uniquely named temporary traces directories to avoid this problem.
#
2018-12-27 12:24:03 +03:00
# We need to figure out what examples to execute. We are either given one
2009-09-12 19:44:17 -07:00
# suite or example explicitly via the --suite or --example option, or we
2018-12-27 12:24:03 +03:00
# need to walk the list of examples looking for available example
2009-09-12 19:44:17 -07:00
# conditions.
#
2018-12-27 12:24:03 +03:00
# This translates into allowing the following options with respect to the
2009-09-12 19:44:17 -07:00
# suites
#
2012-09-10 17:15:07 -07:00
# ./test.py: run all of the examples
2009-09-12 19:44:17 -07:00
# ./test.py --constrain=unit run no examples
2009-10-06 19:34:29 -07:00
# ./test.py --constrain=example run all of the examples
2010-04-15 10:53:40 -07:00
# ./test.py --suite=some-test-suite: run no examples
# ./test.py --example=some-example: run the single example
# ./test.py --suite=some-suite --example=some-example: run the single example
2009-09-12 19:44:17 -07:00
#
#
2010-04-15 10:53:40 -07:00
if len ( options . suite ) == 0 and len ( options . example ) == 0 and len ( options . pyexample ) == 0 :
2009-09-12 19:44:17 -07:00
if len ( options . constrain ) == 0 or options . constrain == " example " :
2009-10-06 19:34:29 -07:00
if ENABLE_EXAMPLES :
2014-01-10 17:20:26 -08:00
for name , test , do_run , do_valgrind_run in example_tests :
2012-04-25 19:08:07 -07:00
# Remove any arguments and directory names from test.
2018-12-27 12:24:03 +03:00
test_name = test . split ( ' ' , 1 ) [ 0 ]
2012-04-25 19:08:07 -07:00
test_name = os . path . basename ( test_name )
2011-04-29 09:53:35 -07:00
# Don't try to run this example if it isn't runnable.
2015-09-03 21:14:55 -07:00
if test_name in ns3_runnable_programs_dictionary :
2011-04-29 09:53:35 -07:00
if eval ( do_run ) :
job = Job ( )
job . set_is_example ( True )
job . set_is_pyexample ( False )
2014-01-10 17:20:26 -08:00
job . set_display_name ( name )
2011-04-29 09:53:35 -07:00
job . set_tmp_file_name ( " " )
job . set_cwd ( testpy_output_dir )
job . set_basedir ( os . getcwd ( ) )
job . set_tempdir ( testpy_output_dir )
job . set_shell_command ( test )
2012-01-13 10:17:39 -08:00
job . set_build_path ( options . buildpath )
2011-04-29 09:53:35 -07:00
if options . valgrind and not eval ( do_valgrind_run ) :
2018-12-27 12:59:23 +03:00
job . set_is_skip ( True )
2018-11-06 12:30:43 -08:00
job . set_skip_reason ( " skip in valgrind runs " )
2011-04-29 09:53:35 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Queue %s " % test )
2011-04-29 09:53:35 -07:00
input_queue . put ( job )
jobs = jobs + 1
total_tests = total_tests + 1
2009-09-28 21:57:59 -07:00
2009-09-12 19:44:17 -07:00
elif len ( options . example ) :
2012-01-13 10:17:39 -08:00
# Add the proper prefix and suffix to the example name to
# match what is done in the wscript file.
2013-06-19 11:17:17 -07:00
example_name = " %s %s - %s %s " % ( APPNAME , VERSION , options . example , BUILD_PROFILE_SUFFIX )
2012-01-13 10:17:39 -08:00
2020-01-09 14:03:13 +01:00
key_list = [ ]
for key in ns3_runnable_programs_dictionary :
key_list . append ( key )
example_name_key_list = fnmatch . filter ( key_list , example_name )
if len ( example_name_key_list ) == 0 :
print ( " No example matching the name %s " % options . example )
2011-04-29 09:53:35 -07:00
else :
#
# If you tell me to run an example, I will try and run the example
# irrespective of any condition.
#
2020-01-09 14:03:13 +01:00
for example_name_iter in example_name_key_list :
example_path = ns3_runnable_programs_dictionary [ example_name_iter ]
example_path = os . path . abspath ( example_path )
job = Job ( )
job . set_is_example ( True )
job . set_is_pyexample ( False )
job . set_display_name ( example_path )
job . set_tmp_file_name ( " " )
job . set_cwd ( testpy_output_dir )
job . set_basedir ( os . getcwd ( ) )
job . set_tempdir ( testpy_output_dir )
job . set_shell_command ( example_path )
job . set_build_path ( options . buildpath )
2010-04-15 10:53:40 -07:00
2020-01-09 14:03:13 +01:00
if options . verbose :
print ( " Queue %s " % example_name_iter )
2011-04-29 09:53:35 -07:00
2020-01-09 14:03:13 +01:00
input_queue . put ( job )
jobs = jobs + 1
total_tests = total_tests + 1
2010-04-15 10:53:40 -07:00
#
# Run some Python examples as smoke tests. We have a list of all of
# the example programs it makes sense to try and run. Each example will
# have a condition associated with it that must evaluate to true for us
# to try and execute it. This is used to determine if the example has
# a dependency that is not satisfied.
#
2018-12-27 12:24:03 +03:00
# We don't care at all how the trace files come out, so we just write them
2010-04-15 10:53:40 -07:00
# to a single temporary directory.
#
2018-12-27 12:24:03 +03:00
# We need to figure out what python examples to execute. We are either
2010-04-15 10:53:40 -07:00
# given one pyexample explicitly via the --pyexample option, or we
# need to walk the list of python examples
#
2018-12-27 12:24:03 +03:00
# This translates into allowing the following options with respect to the
2010-04-15 10:53:40 -07:00
# suites
#
# ./test.py --constrain=pyexample run all of the python examples
# ./test.py --pyexample=some-example.py: run the single python example
#
if len ( options . suite ) == 0 and len ( options . example ) == 0 and len ( options . pyexample ) == 0 :
if len ( options . constrain ) == 0 or options . constrain == " pyexample " :
2010-04-19 09:03:24 -07:00
if ENABLE_EXAMPLES :
2010-04-15 10:53:40 -07:00
for test , do_run in python_tests :
2012-04-25 19:08:07 -07:00
# Remove any arguments and directory names from test.
2018-12-27 12:24:03 +03:00
test_name = test . split ( ' ' , 1 ) [ 0 ]
2012-04-25 19:08:07 -07:00
test_name = os . path . basename ( test_name )
2011-04-29 09:53:35 -07:00
# Don't try to run this example if it isn't runnable.
2012-04-25 19:08:07 -07:00
if test_name in ns3_runnable_scripts :
2011-04-29 09:53:35 -07:00
if eval ( do_run ) :
job = Job ( )
job . set_is_example ( False )
job . set_is_pyexample ( True )
job . set_display_name ( test )
job . set_tmp_file_name ( " " )
job . set_cwd ( testpy_output_dir )
job . set_basedir ( os . getcwd ( ) )
job . set_tempdir ( testpy_output_dir )
job . set_shell_command ( test )
job . set_build_path ( " " )
#
# Python programs and valgrind do not work and play
# well together, so we skip them under valgrind.
# We go through the trouble of doing all of this
# work to report the skipped tests in a consistent
2018-06-27 10:50:27 +03:00
# way through the output formatter.
2011-04-29 09:53:35 -07:00
#
if options . valgrind :
2018-12-27 12:59:23 +03:00
job . set_is_skip ( True )
2018-11-06 12:30:43 -08:00
job . set_skip_reason ( " skip in valgrind runs " )
2011-04-29 09:53:35 -07:00
#
# The user can disable python bindings, so we need
# to pay attention to that and give some feedback
# that we're not testing them
#
if not ENABLE_PYTHON_BINDINGS :
2018-12-27 12:59:23 +03:00
job . set_is_skip ( True )
2018-11-06 12:30:43 -08:00
job . set_skip_reason ( " requires Python bindings " )
2011-04-29 09:53:35 -07:00
if options . verbose :
2015-09-03 21:14:55 -07:00
print ( " Queue %s " % test )
2011-04-29 09:53:35 -07:00
input_queue . put ( job )
jobs = jobs + 1
total_tests = total_tests + 1
2010-04-15 10:53:40 -07:00
elif len ( options . pyexample ) :
2011-04-29 09:53:35 -07:00
# Don't try to run this example if it isn't runnable.
example_name = os . path . basename ( options . pyexample )
2020-01-19 02:23:40 +01:00
if example_name not in ns3_runnable_scripts :
print ( " Example %s is not runnable. " % example_name )
2011-04-29 09:53:35 -07:00
else :
2020-01-19 02:23:40 +01:00
#
# If you tell me to run a python example, I will try and run the example
# irrespective of any condition.
#
job = Job ( )
job . set_is_pyexample ( True )
job . set_display_name ( options . pyexample )
job . set_tmp_file_name ( " " )
job . set_cwd ( testpy_output_dir )
job . set_basedir ( os . getcwd ( ) )
job . set_tempdir ( testpy_output_dir )
job . set_shell_command ( options . pyexample )
job . set_build_path ( " " )
2009-09-12 19:44:17 -07:00
2020-01-19 02:23:40 +01:00
if options . verbose :
print ( " Queue %s " % options . pyexample )
2011-04-29 09:53:35 -07:00
2020-01-19 02:23:40 +01:00
input_queue . put ( job )
jobs = jobs + 1
total_tests = total_tests + 1
2009-09-12 19:44:17 -07:00
#
# Tell the worker threads to pack up and go home for the day. Each one
# will exit when they see their is_break task.
#
for i in range ( processors ) :
job = Job ( )
job . set_is_break ( True )
input_queue . put ( job )
#
# Now all of the tests have been dispatched, so all we have to do here
# in the main thread is to wait for them to complete. Keyboard interrupt
# handling is broken as mentioned above. We use a signal handler to catch
# sigint and set a global variable. When the worker threads sense this
# they stop doing real work and will just start throwing jobs back at us
2018-12-27 12:24:03 +03:00
# with is_break set to True. In this case, there are no real results so we
2009-09-12 19:44:17 -07:00
# ignore them. If there are real results, we always print PASS or FAIL to
# standard out as a quick indication of what happened.
#
2009-09-28 21:57:59 -07:00
passed_tests = 0
failed_tests = 0
2014-04-30 13:06:17 -07:00
failed_testnames = [ ]
2009-09-28 21:57:59 -07:00
crashed_tests = 0
2014-04-30 13:06:17 -07:00
crashed_testnames = [ ]
2009-10-06 22:01:40 -07:00
valgrind_errors = 0
2014-04-30 13:06:17 -07:00
valgrind_testnames = [ ]
2009-09-12 19:44:17 -07:00
for i in range ( jobs ) :
job = output_queue . get ( )
if job . is_break :
continue
2010-04-15 15:11:49 -07:00
if job . is_example or job . is_pyexample :
2009-09-12 19:44:17 -07:00
kind = " Example "
else :
kind = " TestSuite "
2009-10-09 12:54:54 -07:00
if job . is_skip :
status = " SKIP "
2020-01-09 14:05:40 +01:00
status_print = colors . GREY + status + colors . NORMAL
2009-10-09 12:54:54 -07:00
skipped_tests = skipped_tests + 1
2018-11-06 12:30:43 -08:00
skipped_testnames . append ( job . display_name + ( " ( %s ) " % job . skip_reason ) )
2009-09-28 21:57:59 -07:00
else :
2009-10-09 12:54:54 -07:00
if job . returncode == 0 :
status = " PASS "
2020-01-09 14:05:40 +01:00
status_print = colors . GREEN + status + colors . NORMAL
2009-10-09 12:54:54 -07:00
passed_tests = passed_tests + 1
elif job . returncode == 1 :
failed_tests = failed_tests + 1
2014-04-30 13:06:17 -07:00
failed_testnames . append ( job . display_name )
2009-10-09 12:54:54 -07:00
status = " FAIL "
2020-01-09 14:05:40 +01:00
status_print = colors . RED + status + colors . NORMAL
2009-10-09 12:54:54 -07:00
elif job . returncode == 2 :
valgrind_errors = valgrind_errors + 1
2014-04-30 13:06:17 -07:00
valgrind_testnames . append ( job . display_name )
2009-10-09 12:54:54 -07:00
status = " VALGR "
2020-01-09 14:05:40 +01:00
status_print = colors . CYAN + status + colors . NORMAL
2009-10-09 12:54:54 -07:00
else :
crashed_tests = crashed_tests + 1
2014-04-30 13:06:17 -07:00
crashed_testnames . append ( job . display_name )
2009-10-09 12:54:54 -07:00
status = " CRASH "
2020-01-09 14:05:40 +01:00
status_print = colors . PINK + status + colors . NORMAL
2009-09-12 19:44:17 -07:00
2020-02-02 17:50:37 +05:30
print ( " [ %d / %d ] " % ( passed_tests + failed_tests + skipped_tests + crashed_tests , total_tests ) , end = ' ' )
2012-09-10 17:15:07 -07:00
if options . duration or options . constrain == " performance " :
2020-01-09 14:05:40 +01:00
print ( " %s ( %.3f ): %s %s " % ( status_print , job . elapsed_time , kind , job . display_name ) )
2012-09-10 17:15:07 -07:00
else :
2020-01-09 14:05:40 +01:00
print ( " %s : %s %s " % ( status_print , kind , job . display_name ) )
2009-09-12 19:44:17 -07:00
2010-04-15 10:53:40 -07:00
if job . is_example or job . is_pyexample :
2009-09-12 19:44:17 -07:00
#
# Examples are the odd man out here. They are written without any
2018-12-27 12:24:03 +03:00
# knowledge that they are going to be run as a test, so we need to
2009-09-12 19:44:17 -07:00
# cook up some kind of output for them. We're writing an xml file,
# so we do some simple XML that says we ran the example.
#
# XXX We could add some timing information to the examples, i.e. run
# them through time and print the results here.
#
2020-05-13 18:45:06 +01:00
with open ( xml_results_file , ' a ' ) as f :
f . write ( ' <Example> \n ' )
example_name = " <Name> %s </Name> \n " % job . display_name
f . write ( example_name )
if status == " PASS " :
f . write ( ' <Result>PASS</Result> \n ' )
elif status == " FAIL " :
f . write ( ' <Result>FAIL</Result> \n ' )
elif status == " VALGR " :
f . write ( ' <Result>VALGR</Result> \n ' )
elif status == " SKIP " :
f . write ( ' <Result>SKIP</Result> \n ' )
else :
f . write ( ' <Result>CRASH</Result> \n ' )
2009-09-12 19:44:17 -07:00
2020-05-13 18:45:06 +01:00
f . write ( ' <Time real= " %.3f " /> \n ' % job . elapsed_time )
f . write ( ' </Example> \n ' )
2009-10-06 22:01:40 -07:00
2009-09-12 19:44:17 -07:00
else :
#
# If we're not running an example, we're running a test suite.
# These puppies are running concurrently and generating output
# that was written to a temporary file to avoid collisions.
#
# Now that we are executing sequentially in the main thread, we can
2018-12-27 12:24:03 +03:00
# concatenate the contents of the associated temp file to the main
2009-09-12 19:44:17 -07:00
# results file and remove that temp file.
#
# One thing to consider is that a test suite can crash just as
2018-12-27 12:24:03 +03:00
# well as any other program, so we need to deal with that
2009-09-12 19:44:17 -07:00
# possibility as well. If it ran correctly it will return 0
# if it passed, or 1 if it failed. In this case, we can count
2018-12-27 12:24:03 +03:00
# on the results file it saved being complete. If it crashed, it
# will return some other code, and the file should be considered
2009-09-12 19:44:17 -07:00
# corrupt and useless. If the suite didn't create any XML, then
# we're going to have to do it ourselves.
#
2009-10-06 22:01:40 -07:00
# Another issue is how to deal with a valgrind error. If we run
# a test suite under valgrind and it passes, we will get a return
# code of 0 and there will be a valid xml results file since the code
# ran to completion. If we get a return code of 1 under valgrind,
# the test case failed, but valgrind did not find any problems so the
# test case return code was passed through. We will have a valid xml
2018-12-27 12:24:03 +03:00
# results file here as well since the test suite ran. If we see a
2009-10-06 22:01:40 -07:00
# return code of 2, this means that valgrind found an error (we asked
# it to return 2 if it found a problem in run_job_synchronously) but
# the suite ran to completion so there is a valid xml results file.
2018-12-27 12:24:03 +03:00
# If the suite crashes under valgrind we will see some other error
2009-10-06 22:01:40 -07:00
# return code (like 139). If valgrind finds an illegal instruction or
# some other strange problem, it will die with its own strange return
# code (like 132). However, if the test crashes by itself, not under
# valgrind we will also see some other return code.
#
2018-12-27 12:24:03 +03:00
# If the return code is 0, 1, or 2, we have a valid xml file. If we
2009-10-06 22:01:40 -07:00
# get another return code, we have no xml and we can't really say what
# happened -- maybe the TestSuite crashed, maybe valgrind crashed due
# to an illegal instruction. If we get something beside 0-2, we assume
# a crash and fake up an xml entry. After this is all done, we still
# need to indicate a valgrind error somehow, so we fake up an xml entry
# with a VALGR result. Thus, in the case of a working TestSuite that
# fails valgrind, we'll see the PASS entry for the working TestSuite
# followed by a VALGR failing test suite of the same name.
#
2009-10-09 12:54:54 -07:00
if job . is_skip :
2020-05-13 18:45:06 +01:00
with open ( xml_results_file , ' a ' ) as f :
2011-07-29 03:38:59 -04:00
f . write ( " <Test> \n " )
f . write ( " <Name> %s </Name> \n " % job . display_name )
2020-05-13 18:45:06 +01:00
f . write ( ' <Result>SKIP</Result> \n ' )
f . write ( " <Reason> %s </Reason> \n " % job . skip_reason )
2011-07-29 03:38:59 -04:00
f . write ( " </Test> \n " )
2020-05-13 18:45:06 +01:00
else :
if job . returncode == 0 or job . returncode == 1 or job . returncode == 2 :
with open ( xml_results_file , ' a ' ) as f_to , open ( job . tmp_file_name ) as f_from :
f_to . write ( f_from . read ( ) )
else :
with open ( xml_results_file , ' a ' ) as f :
f . write ( " <Test> \n " )
f . write ( " <Name> %s </Name> \n " % job . display_name )
f . write ( ' <Result>CRASH</Result> \n ' )
f . write ( " </Test> \n " )
2009-10-09 12:54:54 -07:00
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# We have all of the tests run and the results written out. One final
2009-09-12 19:44:17 -07:00
# bit of housekeeping is to wait for all of the threads to close down
# so we can exit gracefully.
#
for thread in threads :
thread . join ( )
2018-12-27 12:24:03 +03:00
2009-09-12 19:44:17 -07:00
#
# Back at the beginning of time, we started the body of an XML document
2018-12-27 12:24:03 +03:00
# since the test suites and examples were going to just write their
# individual pieces. So, we need to finish off and close out the XML
2009-09-12 19:44:17 -07:00
# document
#
2020-05-13 18:45:06 +01:00
with open ( xml_results_file , ' a ' ) as f :
f . write ( ' </Results> \n ' )
2009-09-12 19:44:17 -07:00
2009-09-28 21:57:59 -07:00
#
# Print a quick summary of events
#
2018-12-27 12:24:03 +03:00
print ( " %d of %d tests passed ( %d passed, %d skipped, %d failed, %d crashed, %d valgrind errors) " % ( passed_tests ,
2015-09-03 21:14:55 -07:00
total_tests , passed_tests , skipped_tests , failed_tests , crashed_tests , valgrind_errors ) )
2009-09-12 19:44:17 -07:00
#
2018-12-27 12:24:03 +03:00
# Repeat summary of skipped, failed, crashed, valgrind events
2014-04-30 13:06:17 -07:00
#
if skipped_testnames :
2014-10-15 11:29:30 -07:00
skipped_testnames . sort ( )
2015-09-03 21:14:55 -07:00
print ( ' List of SKIPped tests: \n %s ' % ' \n ' . join ( map ( str , skipped_testnames ) ) )
2014-04-30 13:06:17 -07:00
if failed_testnames :
2014-10-15 11:29:30 -07:00
failed_testnames . sort ( )
2015-09-03 21:14:55 -07:00
print ( ' List of FAILed tests: \n %s ' % ' \n ' . join ( map ( str , failed_testnames ) ) )
2014-04-30 13:06:17 -07:00
if crashed_testnames :
2014-10-15 11:29:30 -07:00
crashed_testnames . sort ( )
2015-09-03 21:14:55 -07:00
print ( ' List of CRASHed tests: \n %s ' % ' \n ' . join ( map ( str , crashed_testnames ) ) )
2014-04-30 13:06:17 -07:00
if valgrind_testnames :
2014-10-15 11:29:30 -07:00
valgrind_testnames . sort ( )
2015-09-03 21:14:55 -07:00
print ( ' List of VALGR failures: \n %s ' % ' \n ' . join ( map ( str , valgrind_testnames ) ) )
2014-04-30 13:06:17 -07:00
#
2009-09-12 19:44:17 -07:00
# The last things to do are to translate the XML results file to "human
2009-09-23 15:20:23 -07:00
# readable form" if the user asked for it (or make an XML file somewhere)
2009-09-12 19:44:17 -07:00
#
2018-11-06 12:30:43 -08:00
if len ( options . html ) + len ( options . text ) + len ( options . xml ) :
print ( )
2018-12-27 12:24:03 +03:00
2009-09-12 19:44:17 -07:00
if len ( options . html ) :
translate_to_html ( xml_results_file , options . html )
if len ( options . text ) :
translate_to_text ( xml_results_file , options . text )
2009-09-23 15:20:23 -07:00
if len ( options . xml ) :
2018-11-06 12:30:43 -08:00
xml_file = options . xml + ' .xml '
print ( ' Writing results to xml file %s ... ' % xml_file , end = ' ' )
shutil . copyfile ( xml_results_file , xml_file )
print ( ' done. ' )
2009-09-23 15:20:23 -07:00
2009-10-12 14:01:36 -07:00
#
2011-05-19 11:54:32 -07:00
# Let the user know if they need to turn on tests or examples.
#
if not ENABLE_TESTS or not ENABLE_EXAMPLES :
2015-09-03 21:14:55 -07:00
print ( )
2011-05-19 11:54:32 -07:00
if not ENABLE_TESTS :
2015-09-03 21:14:55 -07:00
print ( ' *** Note: ns-3 tests are currently disabled. Enable them by adding ' )
print ( ' *** " --enable-tests " to ./waf configure or modifying your .ns3rc file. ' )
print ( )
2011-05-19 11:54:32 -07:00
if not ENABLE_EXAMPLES :
2015-09-03 21:14:55 -07:00
print ( ' *** Note: ns-3 examples are currently disabled. Enable them by adding ' )
print ( ' *** " --enable-examples " to ./waf configure or modifying your .ns3rc file. ' )
print ( )
2013-06-13 11:29:15 -07:00
2013-06-14 16:31:10 -07:00
#
# Let the user know if they tried to use valgrind but it was not
# present on their machine.
#
if options . valgrind and not VALGRIND_FOUND :
2015-09-03 21:14:55 -07:00
print ( )
print ( ' *** Note: you are trying to use valgrind, but valgrind could not be found ' )
print ( ' *** on your machine. All tests and examples will crash or be skipped. ' )
print ( )
2013-06-14 16:31:10 -07:00
2011-05-19 11:54:32 -07:00
#
2009-10-12 14:01:36 -07:00
# If we have been asked to retain all of the little temporary files, we
# don't delete tm. If we do delete the temporary files, delete only the
# directory we just created. We don't want to happily delete any retained
# directories, which will probably surprise the user.
#
if not options . retain :
shutil . rmtree ( testpy_output_dir )
2009-10-09 15:52:01 -07:00
if passed_tests + skipped_tests == total_tests :
2009-10-01 14:12:56 -07:00
return 0 # success
2009-10-01 11:53:19 -07:00
else :
2009-10-01 14:12:56 -07:00
return 1 # catchall for general errors
2009-10-01 11:53:19 -07:00
2009-09-12 19:44:17 -07:00
def main ( argv ) :
parser = optparse . OptionParser ( )
2011-04-26 12:53:50 -07:00
parser . add_option ( " -b " , " --buildpath " , action = " store " , type = " string " , dest = " buildpath " , default = " " ,
metavar = " BUILDPATH " ,
help = " specify the path where ns-3 was built (defaults to the build directory for the current variant) " )
2009-09-12 19:44:17 -07:00
parser . add_option ( " -c " , " --constrain " , action = " store " , type = " string " , dest = " constrain " , default = " " ,
metavar = " KIND " ,
help = " constrain the test-runner by kind of test " )
2012-09-10 17:15:07 -07:00
parser . add_option ( " -d " , " --duration " , action = " store_true " , dest = " duration " , default = False ,
help = " print the duration of each test suite and example " )
2009-09-12 19:44:17 -07:00
parser . add_option ( " -e " , " --example " , action = " store " , type = " string " , dest = " example " , default = " " ,
metavar = " EXAMPLE " ,
2012-09-14 11:48:14 -07:00
help = " specify a single example to run (no relative path is needed) " )
2009-09-12 19:44:17 -07:00
2011-07-29 03:38:59 -04:00
parser . add_option ( " -u " , " --update-data " , action = " store_true " , dest = " update_data " , default = False ,
help = " If examples use reference data files, get them to re-generate them " )
2018-08-15 14:02:21 -07:00
parser . add_option ( " -f " , " --fullness " , action = " store " , type = " choice " , dest = " fullness " , default = " QUICK " ,
metavar = " FULLNESS " , choices = [ " QUICK " , " EXTENSIVE " , " TAKES_FOREVER " ] ,
2013-03-19 13:14:12 -07:00
help = " choose the duration of tests to run: QUICK, EXTENSIVE, or TAKES_FOREVER, where EXTENSIVE includes QUICK and TAKES_FOREVER includes QUICK and EXTENSIVE (only QUICK tests are run by default) " )
2013-03-14 14:54:45 -07:00
2009-10-06 22:01:40 -07:00
parser . add_option ( " -g " , " --grind " , action = " store_true " , dest = " valgrind " , default = False ,
help = " run the test suites and examples using valgrind " )
2009-09-12 19:44:17 -07:00
parser . add_option ( " -k " , " --kinds " , action = " store_true " , dest = " kinds " , default = False ,
help = " print the kinds of tests available " )
parser . add_option ( " -l " , " --list " , action = " store_true " , dest = " list " , default = False ,
help = " print the list of known tests " )
2009-09-30 20:26:33 -07:00
parser . add_option ( " -m " , " --multiple " , action = " store_true " , dest = " multiple " , default = False ,
help = " report multiple failures from test suites and test cases " )
2009-09-12 19:44:17 -07:00
parser . add_option ( " -n " , " --nowaf " , action = " store_true " , dest = " nowaf " , default = False ,
help = " do not run waf before starting testing " )
2010-04-15 10:53:40 -07:00
parser . add_option ( " -p " , " --pyexample " , action = " store " , type = " string " , dest = " pyexample " , default = " " ,
metavar = " PYEXAMPLE " ,
2011-04-26 12:53:50 -07:00
help = " specify a single python example to run (with relative path) " )
2010-04-15 10:53:40 -07:00
parser . add_option ( " -r " , " --retain " , action = " store_true " , dest = " retain " , default = False ,
help = " retain all temporary files (which are normally deleted) " )
2009-09-12 19:44:17 -07:00
parser . add_option ( " -s " , " --suite " , action = " store " , type = " string " , dest = " suite " , default = " " ,
metavar = " TEST-SUITE " ,
help = " specify a single test suite to run " )
2010-04-15 10:53:40 -07:00
parser . add_option ( " -t " , " --text " , action = " store " , type = " string " , dest = " text " , default = " " ,
metavar = " TEXT-FILE " ,
help = " write detailed test results into TEXT-FILE.txt " )
2009-09-12 19:44:17 -07:00
parser . add_option ( " -v " , " --verbose " , action = " store_true " , dest = " verbose " , default = False ,
help = " print progress and informational messages " )
parser . add_option ( " -w " , " --web " , " --html " , action = " store " , type = " string " , dest = " html " , default = " " ,
metavar = " HTML-FILE " ,
help = " write detailed test results into HTML-FILE.html " )
2009-09-23 15:20:23 -07:00
parser . add_option ( " -x " , " --xml " , action = " store " , type = " string " , dest = " xml " , default = " " ,
metavar = " XML-FILE " ,
help = " write detailed test results into XML-FILE.xml " )
2020-01-18 10:28:47 +01:00
parser . add_option ( " --nocolor " , action = " store_true " , dest = " nocolor " , default = False ,
help = " do not use colors in the standard output " )
2020-03-24 14:56:26 -07:00
parser . add_option ( " --jobs " , action = " store " , type = " int " , dest = " process_limit " , default = 0 ,
help = " limit number of worker threads " )
2020-01-18 10:28:47 +01:00
2009-09-12 19:44:17 -07:00
global options
options = parser . parse_args ( ) [ 0 ]
signal . signal ( signal . SIGINT , sigint_hook )
2020-03-23 13:11:14 -07:00
# From waf/waflib/Options.py
envcolor = os . environ . get ( ' NOCOLOR ' , ' ' ) and ' no ' or ' auto ' or ' yes '
2020-06-04 12:12:30 -07:00
2020-03-23 13:11:14 -07:00
if options . nocolor or envcolor == ' no ' :
2020-01-18 10:28:47 +01:00
colors_lst [ ' USE ' ] = False
2020-06-04 12:12:30 -07:00
2009-10-01 11:53:19 -07:00
return run_tests ( )
2009-09-12 19:44:17 -07:00
if __name__ == ' __main__ ' :
sys . exit ( main ( sys . argv ) )