Parameters values for filelog perflogs #2577
Description
Feel free to tell me that you don't want to support this use case if it's not useful for your sites.
We have a unit test that executes on each IB NIC/HCA on a node, this is done through a parameterized test:
hca = parameter(["mlx5_0", "mlx5_1", "mlx5_2", "mlx5_3", "mlx5_6", "mlx5_7", "mlx5_8", "mlx5_9"])With the naming scheme in 3.12.0, we could simply access the historical performance for one HCA given that the path was predictable:
$ cat ./logs/node0042/perflogs/ib_write_bw_loopback_mlx5_6.log
2022-08-07T09:54:13|reframe 3.12.0|ib_write_bw_loopback %hca=mlx5_6 ....
2022-08-08T10:28:11|reframe 3.12.0|ib_write_bw_loopback %hca=mlx5_6 ....
With 833c6ea, it's now a little more complex as the output file name is not predictable anymore, we would have to grep across all logs for this test to find the right HCA.
I understand the limitations of the old naming scheme mentioned in https://github.com/reframe-hpc/reframe/blob/833c6ea3582bdcf4cceb6dc7a1aa667d0ca029e2/docs/manpage.rst#test-naming-scheme, but perhaps we could have a way to modify the name of the filelog output file (doesn't seem possible today: https://reframe-hpc.readthedocs.io/en/stable/config_reference.html#the-filelog-log-handler)? And then a new log record attribute that would allow to get parameters names in the file name.