-
Notifications
You must be signed in to change notification settings - Fork 22
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
Stability issues wrt Scheduled Benchmark Tests on Self Hosted Runner #60
Comments
@hershd23 thanks for this! @alphaX86 will you kindly investigate the auth issue? // @theBeginner86 |
Rog' seems I need to see the script file again and tackle the auth issue |
Just to point out the auth issue doesn't happen everytime, it's flaky but this seems to be one of the most clear reasons as to why random tests are failing |
Understood, I kinda figured where it went wrong, but still I need to investigate further... The fix for this will be done by tomorrow for sure. Thanks @hershd23 👍 |
Great. Do let me know if the scripts need to change in lieu of your changes to meshery or ctl |
Description
Multiple issues of the Scheduled Benchmark Tests on Self Hosted Runner generate different results
While here just one combination failed :- https://github.com/layer5io/meshery-smp-action/runs/7770247406 (linkerd-wrk-soak)
Here a couple failed :- https://github.com/layer5io/meshery-smp-action/actions/runs/2832186044
And here one runner startup itself failed :- https://github.com/layer5io/meshery-smp-action/actions/runs/2833335073
Expected Behavior
The behaviour should be consistent across Scheduled Benchmark Test run on self hosted runners. Given we are working with external hardware where connections can fail, ideally we should have a retry mechanism and we should work to considerably reduce the consistency
Logs
In the logs Auth seems to be a common culprit
This is seen for istio
Environment:
The text was updated successfully, but these errors were encountered: