-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to record results for remote endpoints #62
Comments
Happens on |
are you using the same exact version of flood on each machine? try installing latest flood commit on each |
As per @mattsse suggestion I tried running flood locally on those machines and it was failing with this error:
This was fixed by For reference they are both running flood |
To shine more light on this. What happens is the remote server command sort-of fails (it produces generates results) but for some reason I'm not aware prints I worked around it for now by silencing the panic: diff --git a/flood/tests/load_tests/load_test_runs.py b/flood/tests/load_tests/load_test_runs.py
index 0bd1d09..1e497f4 100644
--- a/flood/tests/load_tests/load_test_runs.py
+++ b/flood/tests/load_tests/load_test_runs.py
@@ -377,7 +377,12 @@ def _run_load_test_remotely(
extra_kwargs=extra_kwargs.lstrip(),
)
cmd = cmd.strip()
- subprocess.check_output(cmd.split(' '), stderr=subprocess.DEVNULL)
+ try:
+ subprocess.check_output(cmd.split(' '), stderr=subprocess.DEVNULL)
+ except subprocess.CalledProcessError as cpe_error:
+ print(f"CalledProcessError: {cpe_error}")
+ decoded_output = cpe_error.output.decode('utf-8', errors='replace')
+ print(f"Output (stdout + stderr): {decoded_output}")
# retrieve benchmark results
if verbose: |
Version
v0.3.1
Platform
Darwin Mac-mini 22.6.0
Description
I have two remote RPC endpoints. I have installed flood and vegeta both locally and on those machines. When I try the following command:
it proceeds to execute the tests, however at the end when it wants to record the results I get this exception:
(I get one such exception from each endpoint)
The text was updated successfully, but these errors were encountered: