googleapis / google-cloud-java

Google Cloud Client Library for Java
https://cloud.google.com/java/docs/reference
Apache License 2.0
1.9k stars 1.06k forks source link

Nightly IT Failure (java-talent): Tenant Already Exists error. #10445

Open mpeddada1 opened 8 months ago

mpeddada1 commented 8 months ago

Stacktrace:

09:11:03:351 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.964 s <<< FAILURE! -- in com.google.cloud.talent.v4.it.ITSystemTest
09:11:03:352 [ERROR] com.google.cloud.talent.v4.it.ITSystemTest -- Time elapsed: 1.964 s <<< FAILURE!
org.opentest4j.MultipleFailuresError: 
Multiple Failures (2 failures)
    com.google.api.gax.rpc.AlreadyExistsException: io.grpc.StatusRuntimeException: ALREADY_EXISTS: Tenant tenants/8c475cfa-baae-43ff-82de-943da0ac673c already exists. Related tenant external ID: 1709197861.. Request ID for tracking: bbc27bec-3f00-4c4d-863b-75eb1e399439:APAb7ITtGiits7l+tmrHstwqsiq7UfSY5w==
    java.lang.NullPointerException: <no message>
    at org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:200)
    at org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:248)
    at org.junit.vintage.engine.execution.RunListenerAdapter.reportContainerFinished(RunListenerAdapter.java:114)
    at org.junit.vintage.engine.execution.RunListenerAdapter.testRunFinished(RunListenerAdapter.java:102)
    at org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
    at org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
    at org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
    at org.junit.runner.notification.RunNotifier.fireTestRunFinished(RunNotifier.java:100)

Fusion Link

cc/ @zhumin8

zhumin8 commented 8 months ago

similar issue in the past: https://github.com/googleapis/google-cloud-java/issues/9039

lqiu96 commented 5 months ago

Going to downgrade to p3 as this seems to be a rare occurrence and might have been a transient server-side issue.