From 227eaaf3bc2ca2fb4d3c0d96433406cd0d3892b7 Mon Sep 17 00:00:00 2001
From: Igor Bernstein <igorbernstein@google.com>
Date: Wed, 31 Jul 2019 22:31:08 -0400
Subject: [PATCH] Bigtable: remove integration tests from the default failsafe
 execution

This was a bug introduced in #5756. When integration profiles were introduced,
I forgot to remove the test from the default execution of the failsafe plugin.
The new way integration tests are run are via profile activation: by default
the bigtable-emulator-it profile is active.
---
 google-cloud-clients/google-cloud-bigtable/pom.xml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/google-cloud-clients/google-cloud-bigtable/pom.xml b/google-cloud-clients/google-cloud-bigtable/pom.xml
index 53b9ecb65c92..42b8bc9c35c6 100644
--- a/google-cloud-clients/google-cloud-bigtable/pom.xml
+++ b/google-cloud-clients/google-cloud-bigtable/pom.xml
@@ -188,8 +188,6 @@
           <perCoreThreadCount>true</perCoreThreadCount>
           <threadCount>2</threadCount>
           <trimStackTrace>false</trimStackTrace>
-          <test>com.google.cloud.bigtable.data.v2.it.**</test>
-          <test>com.google.cloud.bigtable.admin.v2.it.**</test>
         </configuration>
         <dependencies>
           <dependency>