[go: nahoru, domu]

Skip to content
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

ITAddressesTest is flaky #10902

Open
diegomarquezp opened this issue May 30, 2024 · 4 comments
Open

ITAddressesTest is flaky #10902

diegomarquezp opened this issue May 30, 2024 · 4 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@diegomarquezp
Copy link
Contributor
diegomarquezp commented May 30, 2024

https://github.com/googleapis/google-cloud-java/blob/main/java-compute/google-cloud-compute/src/test/java/com/google/cloud/compute/v1/integration/ITAddressesTest.java

Failing integration test check

com.google.cloud.compute.v1.integration.ITAddressesTest
20:21:17:526 [ERROR] com.google.cloud.compute.v1.integration.ITAddressesTest.testList -- Time elapsed: 1.558 s <<< ERROR!
java.lang.RuntimeException: Insert operation failed.
	at com.google.cloud.compute.v1.integration.ITAddressesTest.insertAddress(ITAddressesTest.java:121)
   ...
Caused by: java.util.concurrent.ExecutionException: com.google.api.gax.rpc.PermissionDeniedException: Operation with name "operation-1717014073929-6199d7df36e08-985f4196-d106a138" failed with status = HttpJsonStatusCode{statusCode=PERMISSION_DENIED} and message = FORBIDDEN

Links:

@burkedavison burkedavison changed the title ITAddressesTest fails with PERMISSION_DENIED in GraalVM checks ITAddressesTest fails with PERMISSION_DENIED in integration test May 30, 2024
@diegomarquezp
Copy link
Contributor Author

A local run of the tests was successful

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.07 s -- in com.google.cloud.compute.v1.integration.ITHeadersTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.46 s -- in com.google.cloud.compute.v1.integration.ITAddressesTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.63 s -- in com.google.cloud.compute.v1.integration.ITPaginationTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 856.7 s -- in com.google.cloud.compute.v1.integration.ITSmokeInstancesTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.07 s -- in com.google.cloud.compute.v1.integration.ITHeadersTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.46 s -- in com.google.cloud.compute.v1.integration.ITAddressesTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.63 s -- in com.google.cloud.compute.v1.integration.ITPaginationTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 856.7 s -- in com.google.cloud.compute.v1.integration.ITSmokeInstancesTest

I set the GOOGLE_APPLICATION_CREDENTIALS env var + setting GOOGLE_CLOUD_PROJECT to a personal one

@diegomarquezp diegomarquezp changed the title ITAddressesTest fails with PERMISSION_DENIED in integration test ITAddressesTest is flaky Jun 4, 2024
@diegomarquezp
Copy link
Contributor Author

It has lately passed, so this is a flake

@diegomarquezp
Copy link
Contributor Author
diegomarquezp commented Jun 4, 2024

The GraalVM ones started to consistently fail after 15:23 of today
image

The plain integration job is failing in a flaky fashion
image

@blakeli0 blakeli0 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 4, 2024
@diegomarquezp
Copy link
Contributor Author

Quick note: me and @blakeli0 confirmed that the tests pass on a local run using a different GCP project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants