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
Occasionally tests fail and leave behind resource in our test environments. We automatically clean up resources with a tf-test prefix on a regular basis. However, some Dataproc tests currently use a tf-dataproc prefix, which does not automatically get cleaned up. Although the random suffixes on the resource ids will generally prevent conflicts, this may eventually cause quota issues.
The Dataproc tests that use tf-dataproc as the prefix should be updated to start with tf-test
b/309162860#comment7
b/309934501
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Occasionally tests fail and leave behind resource in our test environments. We automatically clean up resources with a
tf-test
prefix on a regular basis. However, some Dataproc tests currently use atf-dataproc
prefix, which does not automatically get cleaned up. Although the random suffixes on the resource ids will generally prevent conflicts, this may eventually cause quota issues.The Dataproc tests that use
tf-dataproc
as the prefix should be updated to start withtf-test
b/309162860#comment7
b/309934501
The text was updated successfully, but these errors were encountered: