tests: fix: Run packet-set-buf tracing test

Context
-------

Currently, the packet-set-buf test is not run even though the test was
added as a regression test for a bug fix (0a5733a). The fix commit
message says:

    Adding a test with a custom platform calling
    barectf_packet_set_buf() with a `NULL` buffer after closing a
    completely full packet. Without this patch (in `barectf.c.j2`), this
    test leads to a segmentation fault.

It looks like this new test case was accidentally not added to the list
of valid test categories:

    * Sep 24, 2020 - Filter for valid test categories added (in 5b906ca)
    * Oct 6, 2020 - packet-set-buf test added, but not to valid
       categories (in 0a5733a)

Changes
-------

Add `packet-set-buf` to the valid test categories so the test will run.

Change-Id: I43a90bafe08897eaf107336fd8b629bad512b996
Signed-off-by: Erica Bugden <ebugden@efficios.com>

diff --git a/tests/tracing/conftest.py b/tests/tracing/conftest.py
index 3555844094037db6ba646023b04788c514f7e9df..fe9824a581dae19a60fff006770da6d8bbc2d232 100644 (file)
--- a/tests/tracing/conftest.py
+++ b/tests/tracing/conftest.py
@@ -60,6 +60,7 @@ def pytest_collect_file(parent, path):
         'basic',
         'counter-clock',
         'basic-extra-pc-ft-members',
+        'packet-set-buf',
     }
 
     if cat not in valid_cats or os.path.basename(configs_dir) != 'configs':