tests: make UUIDs under data/ctf-traces/intersection unique
authorSimon Marchi <simon.marchi@efficios.com>
Tue, 10 Sep 2019 20:03:28 +0000 (16:03 -0400)
committerSimon Marchi <simon.marchi@efficios.com>
Mon, 16 Sep 2019 18:28:03 +0000 (14:28 -0400)
commit0713ec72ea9f82718c4d54324d6f80eec9c357e0
tree6b2b91f6c18211b155c6c7db61b0fe4387e0bdf0
parent9f7cf1d279424a217ca573f854b6da5cb464df32
tests: make UUIDs under data/ctf-traces/intersection unique

Traces under data/ctf-traces/intersection currently share some UUID
values, even though they are different traces.  I presume it was not
really the initial intention (although it doesn't really matter when
handling them separately).  However, this prevents using them
simultaneously for testing, as they will get treated as part of the same
trace, when that's not what we want.

This patch assigns new, random UUIDs to all duplicated trace and clock
UUIDs.

Change-Id: I7b426640a787a70635162a3c8f1a6c7854072305
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/2025
Tested-by: jenkins <jenkins@lttng.org>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
tests/data/ctf-traces/intersection/3eventsintersectreverse/metadata
tests/data/ctf-traces/intersection/nostream/metadata
tests/data/ctf-traces/intersection/onestream/metadata
This page took 0.024818 seconds and 4 git commands to generate.