DevOps: Fix bandwidth testing#3638
Conversation
for nodes, and non participating nodes.
Codecov Report
@@ Coverage Diff @@
## master #3638 +/- ##
==========================================
- Coverage 48.06% 48.05% -0.01%
==========================================
Files 381 381
Lines 62080 62080
==========================================
- Hits 29836 29832 -4
Misses 28822 28822
- Partials 3422 3426 +4
Continue to review full report at Codecov.
|
|
Successfully tested with Custom recipe and bandwidth testing enabled. #3638 |
tsachiherman
left a comment
There was a problem hiding this comment.
I wouldn't go that far and call this is bug.. But this change makes perfect sense.
It would be nice if you were to go over all the other recipes and update them as well, but it's perfectly fine as is.
algobarb
left a comment
There was a problem hiding this comment.
Can we document somewhere that "NetAddress": "{{NetworkPort}}", "APIEndpoint": "{{APIEndpoint}}"
is a requirement to run bandwidth testing? Maybe Confluence?
@algobarb good thinking, I added an info note here: https://algorand.atlassian.net/wiki/spaces/DEVOPS/pages/442433537/Automated+Performance+Testing+Framework |
Fixed problem running bandwidth performance testing with the custom and scenario2 recipes by enabling the API endpoints for nodes and nonparticipating nodes.
Fixed problem running bandwidth performance testing with the custom and scenario2 recipes by enabling the API endpoints for nodes and nonparticipating nodes.
Summary
Allow bandwidth testing with custom and scenario 2 recipes.
Test Plan
Tested using the updated custom recipe. The performance pipeline was completed successfully and the datadog bandwidth chart was updated.