I have a scenario that uses the K6 executor to apply a gRPC workload against a server. When I use bzt 1.16.26 to run the scenario, the test appears to execute successfully and I do see results in kpi.csv file. But during post processing, I see the following error in the console
...
22:31:17 ERROR: Child Process Error: Empty results, most likely context-create (K6Executor) failed. Actual reason for this can be found in logs under /Users/lambere/git/ftl/build/blazemeter/context-create/artifacts/2023-11-09_22-31-11.718091
...
snippet from bzt.log
[2023-11-09 22:31:17,629 INFO Engine] Post-processing...
[2023-11-09 22:31:17,629 DEBUG Engine.local] Post-process k6/context-create
[2023-11-09 22:31:17,629 DEBUG Engine] Add existing artifact (move=False): /Users/lambere/git/ftl/build/blazemeter/context-create/artifacts/2023-11-09_22-31-11.718091/kpi.csv
[2023-11-09 22:31:17,629 DEBUG Engine] No need to copy /Users/lambere/git/ftl/build/blazemeter/context-create/artifacts/2023-11-09_22-31-11.718091/kpi.csv
[2023-11-09 22:31:17,631 DEBUG Engine.local] Exception in post_process of K6Executor: Empty results, most likely context-create (K6Executor) failed. Actual reason for this can be found in logs under /Users/lambere/git/ftl/build/blazemeter/cont
ext-create/artifacts/2023-11-09_22-31-11.718091 Traceback (most recent call last):
File "/opt/homebrew/Cellar/bzt/1.16.26/libexec/lib/python3.12/site-packages/bzt/modules/provisioning.py", line 165, in post_process
raise ToolError(message, diagnostics)
bzt.ToolError: Empty results, most likely context-create (K6Executor) failed. Actual reason for this can be found in logs under /Users/lambere/git/ftl/build/blazemeter/context-create/artifacts/2023-11-09_22-31-11.718091
[2023-11-09 22:31:17,634 DEBUG Engine] post_process: Empty results, most likely context-create (K6Executor) failed. Actual reason for this can be found in logs under /Users/lambere/git/ftl/build/blazemeter/context-create/artifacts/2023-11-09_2
2-31-11.718091
Traceback (most recent call last):
File "/opt/homebrew/Cellar/bzt/1.16.26/libexec/lib/python3.12/site-packages/bzt/engine/engine.py", line 356, in post_process
module.post_process()
File "/opt/homebrew/Cellar/bzt/1.16.26/libexec/lib/python3.12/site-packages/bzt/modules/provisioning.py", line 174, in post_process
reraise(exc_info, exc_value)
As stated above, there are results in kpi.csv file. The file contains values for the following metrics:
metric_name,timestamp,metric_value,check,error,error_code,expected_response,group,method,name,proto,scenario,service,status,subproto,tls_version,url,extra_tags,metadata
data_sent,1699597873,0.000000,,,,,::setup,,,,,,,,,,,
data_received,1699597873,0.000000,,,,,::setup,,,,,,,,,,,
iteration_duration,1699597873,0.041542,,,,,::setup,,,,,,,,,,,
grpc_req_duration,1699597873,122.119750,,,,,,Create,<REDACTED>,,default,<REDACTED>,0,,,<REDACTED>,,
checks,1699597873,1.000000,status is OK,,,,,,,,default,,,,,,,
...
Note, I've redacted some values from the contents of the file.
I DO NOT see this problem when I use the K6 Executor to run a "REST" based workload.
I have a scenario that uses the K6 executor to apply a gRPC workload against a server. When I use
bzt 1.16.26
to run the scenario, the test appears to execute successfully and I do see results inkpi.csv
file. But during post processing, I see the following error in the consolesnippet from
bzt.log
As stated above, there are results in kpi.csv file. The file contains values for the following metrics:
Note, I've redacted some values from the contents of the file.
I DO NOT see this problem when I use the K6 Executor to run a "REST" based workload.
Environment Details