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)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Thu, 3 Oct 2019 14:45:10 +0000 (10:45 -0400)
commitbd4eea6fed308f4f0954b563b25471cc373161f1
treefc3aaea282faf4ede3c8fb4192ad806ef1366178
parent555c125c51560253ec1c1820cbf583b8e5baa8cb
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.027107 seconds and 4 git commands to generate.