-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
compute/apiv1: TestCapitalLetter failed #5988
Comments
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. commit: 9a60d95 Test outputsmoke_test.go:490: retry failed with context deadline exceeded; last error: googleapi: Error 404: The resource 'projects/dulcet-port-762/global/firewalls/gogapic-20220505-61993224015989-0001' was not found |
Operations should be waited on and not just created. This was causing tests to fail because the operation was finishing silently and then subsquent delete operations could not find the resulting instance that had already been deleted. Fixes: googleapis#5988
Operations should be waited on and not just created. This was causing tests to fail because the operation was finishing silently and then subsquent delete operations could not find the resulting instance that had already been deleted. Fixes: #5988
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: c0a0c20 Test outputsmoke_test.go:484: googleapi: Error 400: The resource 'projects/dulcet-port-762/global/firewalls/gogapic-20220701-6971834107891-0001' is not ready panic: runtime error: invalid memory address or nil pointer dereference /usr/local/go/src/testing/testing.go:1072 +0x46a /usr/local/go/src/testing/testing.go:1075 +0x636 /usr/local/go/src/runtime/panic.go:975 +0x47a /tmpfs/src/google-cloud-go/compute/apiv1/operations.go:51 +0x7f /tmpfs/src/google-cloud-go/compute/apiv1/smoke_test.go:486 +0x30d /tmpfs/src/google-cloud-go/compute/apiv1/smoke_test.go:500 +0xd06 /usr/local/go/src/testing/testing.go:1123 +0x203 /usr/local/go/src/testing/testing.go:1168 +0x5bc |
Add retry around the creation of the operation as even though it is fetched right away this does not mean it can be delted yet. Fixes: googleapis#5988
Just because a firewall has been fetched does not mean it can be deleted yet. Retry the delete operation as the resource is not always full allocated enough to delete it right away. Fixes: googleapis#5988
Add retry around the creation of the operation as even though it is fetched right away this does not mean it can be delted yet. Fixes: googleapis#5988
Add retry around the creation of the operation as even though it is fetched right away this does not mean it can be delted yet. Fixes: #5988
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 5ea92cf Test outputretry.go:44: FAILED after 20 attempts: smoke_test.go:486: googleapi: Error 404: The resource 'projects/dulcet-port-762/global/firewalls/gogapic-20220711-29510602544337-0001' was not found smoke_test.go:490: |
@FrodoTheTrue PTAL |
@codyoss reassigning back to you as this looks like a flaky smoke test. Please decide if you'd like to turn it off or address differently. |
This test has been flaky for a long time. If we want something like this test in the future I think it needs to be re-structured to be successful. For now we will remove it as it is not providing value as is and since writing there are now many tests in our samples that should cover these types of use-cases. Fixes: googleapis#5988
This test has been flaky for a long time. If we want something like this test in the future I think it needs to be re-structured to be successful. For now we will remove it as it is not providing value as is and since writing there are now many tests in our samples that should cover these types of use-cases. Fixes: #5988
This test has been flaky for a long time. If we want something like this test in the future I think it needs to be re-structured to be successful. For now we will remove it as it is not providing value as is and since writing there are now many tests in our samples that should cover these types of use-cases. Fixes: googleapis#5988
Note: #4741 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 3972c38
buildURL: Build Status, Sponge
status: failed
Test output
The text was updated successfully, but these errors were encountered: