Bug 549 – ./waf --regression -v generates a python error

Bug 549 - ./waf --regression -v generates a python error


Summary:	./waf --regression -v generates a python error

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	build system
Version:	ns-3-dev
Hardware:	All All

Importance:	P5 normal
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-16 04:03 UTC by Mathieu Lacage
Modified:	2009-04-20 13:04 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mathieu Lacage 2009-04-16 04:03:47 UTC

SKIP: 1 of 22 tests have been skipped (test-tcp-nsc-lfn)
FAIL: 2 of 22 tests have failed (test-second, test-third)
Build failed
 -> task failed (err #1): 
	{task: regression_test_collector_task }
  File "./waf", line 127, in <module>
	Scripting.prepare(t, cwd, VERSION, wafdir)
  File "/home/mlacage/code/ns-3-dev/.waf-1.5.3-ee19efc5fb177979684a69740de63fc8/wafadmin/Scripting.py", line 123, in prepare
	prepare_impl(t,cwd,ver,wafdir)
  File "/home/mlacage/code/ns-3-dev/.waf-1.5.3-ee19efc5fb177979684a69740de63fc8/wafadmin/Scripting.py", line 116, in prepare_impl
	main()
  File "/home/mlacage/code/ns-3-dev/.waf-1.5.3-ee19efc5fb177979684a69740de63fc8/wafadmin/Scripting.py", line 186, in main
	bld.compile()
  File "/home/mlacage/code/ns-3-dev/.waf-1.5.3-ee19efc5fb177979684a69740de63fc8/wafadmin/Build.py", line 152, in compile
	raise BuildError(self,self.task_manager.tasks_done)
  File "/home/mlacage/code/ns-3-dev/.waf-1.5.3-ee19efc5fb177979684a69740de63fc8/wafadmin/Build.py", line 18, in __init__
	Utils.WafError.__init__(self,self.format_error())
[mlacage@diese ns-3-dev]$

Comment 1 Gustavo J. A. M. Carneiro 2009-04-17 07:36:45 UTC

I think this is just WAF being excessively verbose about its internal state at a time a task failed.  Not really a bug, perhaps?

Let me see what the WAF maintainer thinks...

=> http://code.google.com/p/waf/issues/detail?id=426

Comment 2 Gustavo J. A. M. Carneiro 2009-04-20 13:04:55 UTC

fixed by waf 1.5.5 upgrade