Bug 1463

Summary:	./test.py --example should automatically detect the path
Product:	ns-3	Reporter:	Nicola Baldo <nicola>
Component:	test framework	Assignee:	Mitch Watrous <watrous>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	ns-bugs
Priority:	P5
Version:	ns-3-dev
Hardware:	All
OS:	All

Description Nicola Baldo 2012-06-25 10:49:35 UTC

This is a feature request, motivated by the following behavior:

(using ns-3-dev changeset:   8868:d06f5a8b84a6)

nicola@pcnbaldo:/locale/ns-3-dev$ ./test.py --example=lena-dual-stripe --verbose

[snip]

---------- begin standard out ----------

---------- begin standard err ----------
/bin/sh: /locale/ns-3-dev/build/ns3-dev-lena-dual-stripe-debug: not found

---------- end standard err ----------
CRASH: Example ns3-dev-lena-dual-stripe-debug
0 of 1 tests passed (0 passed, 0 skipped, 0 failed, 1 crashed, 0 valgrind errors)


The problem is just that test.py does not automatically detect the path of the example. The issue is that "./waf -run" does this, hence one might have the same expectation for test.py. It would be nice to have similar interfaces 

Note that test.py works correctly with the complete path, e.g.:

./test.py  --example=src/lte/examples/lena-dual-stripe

Comment 1 Mitch Watrous 2012-09-13 20:57:27 UTC

I think I can make this work for the C++ examples, but not the Python examples.

This would be the same situation as for waf, which requires paths for Python examples.

Is that still acceptable?

Comment 2 Nicola Baldo 2012-09-14 04:19:15 UTC

Thanks for your effort! Yes I think your approach makes sense, especially considering what you mentioned about the behavior of ./waf --run with python examples. So the behavior will be consistent between ./waf and ./test.py

Comment 3 Mitch Watrous 2012-09-14 14:50:32 UTC

Bug closed.

ns-3-dev changeset: 7c9f34fa2dd6