Component
Harnesses
Describe the bug
There is a log file pod_log_response.txt in the fmperf repository (PR to remove it), and this file gets copied into the results of every benchmark run:
|
cp -f /workspace/fmperf/pod_log_response.txt /requests/\${LLMDBENCH_FMPERF_STACK_NAME}/\n\ |
This copy should either be removed or modified to copy an appropriate log file created by fmperf.
Steps to reproduce
Run any benchmarking experiment using the fmperf harness, and check the results directory for pod_log_response.txt matching that in https://github.com/fmperf-project/fmperf/blob/main/pod_log_response.txt
Additional context or screenshots
No response
Component
Harnesses
Describe the bug
There is a log file
pod_log_response.txtin the fmperf repository (PR to remove it), and this file gets copied into the results of every benchmark run:llm-d-benchmark/build/Dockerfile
Line 65 in 3df0c7c
This copy should either be removed or modified to copy an appropriate log file created by fmperf.
Steps to reproduce
Run any benchmarking experiment using the fmperf harness, and check the
resultsdirectory forpod_log_response.txtmatching that in https://github.com/fmperf-project/fmperf/blob/main/pod_log_response.txtAdditional context or screenshots
No response