Open jmarantz opened 7 months ago
I don't think it's a lock issue; 1 CPU is 100% while waiting for the second speed test above to exit.
the second test is still running after 4 hours.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
When I run stats-handler_speed_test it takes a surprising amount of time to initialize, and even longer to finish (return to the prompt).
Something n^2 might be happening in the mocks destruct sequence, or maybe a lock issue.
https://github.com/envoyproxy/envoy/pull/32197 enables a workaround by only initializing the host info when called for by a test, so someone can use a regex to run only the 'disabled' tests. With the above PR:
whereas by default: