Bug 1664 – fix random streams in some test suites

Bug 1664 - fix random streams in some test suites


Summary:	fix random streams in some test suites

Status:	CONFIRMED

Product:	ns-3
Classification:	Unclassified
Component:	test framework
Version:	pre-release
Hardware:	All All

Importance:	P5 normal
Assigned To:	Tom Henderson

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-01 09:34 EDT by Tom Henderson
Modified:	2013-12-14 02:08 EST (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 Tom Henderson 2013-05-01 09:34:51 EDT

When the test order is perturbed by running them like this:

./waf --run "test-runner --test-type=unit"

a few tests fail:

mobility-trace, devices-wifi, ipv6-raw, and ipv6-address-helper

this is most likely because there is usage of random variables in these tests that are not fixed to particular streams.  Another possible reason is that the seed and/or run number need to be fixed.

This changeset shows the nature of the fixes that are likely needed:

changeset:   9735:f514ef70e2f4
tag:         tip
user:        Tom Henderson <tomh@tomh.org>
date:        Wed May 01 06:29:57 2013 -0700
summary:     assign streams to burst error model test case

(reported by Daniel L.)

Comment 1 Tom Henderson 2013-05-01 09:37:58 EDT

before closing this bug, I'd like to see one of the jenkins scripts extended to run the tests this way, as well as the deep valgrind runs.