Reduce the flakyness in E2E tests and increase test coverage #7128
Assignees
Milestone
Comments
|
The first point in the issue is resolved by dapr/community#361 |
|
/assign |
This was referenced Nov 16, 2023
This was referenced Nov 28, 2023
|
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
|
This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
|
/keep-alive |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What needs to be done:
DAPR Test badge that was shown is showing only 34% success rate. Fix the yaml file to reflect the correct value for the pass rate.
Reduce the flakiness in dapr-tests workflow : dapr-test · dapr/dapr@d284d63 (github.com)
Tests on Windows are failing so frequently due to deployment issues “ Failed Platform.addApps(), deployment "bindinginput" is not in desired state, received: &v1.Deployment{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"", GenerateName:"", Namespace:"", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil),?.
We should investigate why it is failing and fix the issue so that tests will be green.
The current E2E tests execution got upto 80% pass rate. Fix the tests that are >2% failures so that the overall test execution success rate can reach to 90%. Test execution status can be downloaded from here: dapr-e2e-tests-crawler · dapr/test-infra@e2e3a83 (github.com)
DAPR SDK tests are continuously failing for JAVA & JS; dapr-test-sdk · dapr/dapr@4d4c8b9 (github.com).
JS SDK errors :
ime="2023-10-24T00:32:22.704408275Z" level=error msg="error getting topic list from app: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:50001: connect: connection refused"" app_id=test-suite instance=fv-az1098-683 scope=dapr.runtime.processor.pubsub type=log ver=edge
762time="2023-10-24T00:32:22.704494083Z" level=info msg="Error processing operation DaprBuiltInInitializationRetries. Retrying in 576.008928ms…" app_id=test-suite instance=fv-az1098-683 scope=dapr.runtime type=log ver=edge
763time="2023-10-24T00:32:23.892100446Z" level=warning msg="[DEPRECATION NOTICE] InvokeService is deprecated and will be removed in the future, please use proxy mode instead." app_id=test-suite instance=fv-az1098-683 scope=dapr.runtime.grpc.api type=log ver=edge
764== APP == console.log
765== APP == Error: 14 UNAVAILABLE: connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:50001: connect: connection refused"
766== APP == at callErrorFromStatus (/home/runner/work/dapr/dapr/js-sdk/node_modules/@grpc/grpc-js/src/call.ts:82:17)
JAVA SDK Erros:
Errors:
9560Error: ActorExceptionIT.exceptionTest:51 » Runtime org.opentest4j.AssertionFailedError: expected: but was:
9561Error: ActorStateIT.writeReadState:82 » Runtime io.dapr.exceptions.DaprException: ERR_ACTOR_INVOKE_METHOD: error invoke actor method: did not find address for actor StatefulActorTest/1698108256595-true-true
The text was updated successfully, but these errors were encountered: