You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
willdavsmith opened this issue
Mar 19, 2024
· 3 comments
Assignees
Labels
importantThis item is a high priority Issue we intend to address as soon as possibletriagedThis item has been triaged by project maintainers and is in the backlog
The major failure happens only when eshop is being deployed to k3d cluster. testing it on EKS cluster is always stable. My hypothesis is that it might be related to resource constraints of single vm cluster. I would check whether the root cause of this problem stems from resource limitation or not by switching k3d cluster to aks cluster and running it for at least a week.
I will schedule a meeting with you, @youngbupark and @willdavsmith. We can discuss about these flaky tests. I am also working on a task right now which is also related to this.
sylvainsf
added
triaged
This item has been triaged by project maintainers and is in the backlog
important
This item is a high priority Issue we intend to address as soon as possible
labels
Mar 21, 2024
I have added retries, better logging, and improved the workflows. I added the video recordings of the failure and changed the readiness checks to liveness checks. I am closing this for now and, going forward, we can focus on the issues that pop up in the tests.
importantThis item is a high priority Issue we intend to address as soon as possibletriagedThis item has been triaged by project maintainers and is in the backlog
We have seen some issues with the playwright tests with network issues.
#885
#883
#907
We should consider improving the reliability of these tests through retries, better logging, etc.
AB#11555
The text was updated successfully, but these errors were encountered: