Merge pull request #38019 from nextcloud/enh/noid/disable-contactsmen…

…u-tests

disable contacts menu features that regularly fail on drone

build/integration/features/contacts-menu.feature

@@ -100,10 +100,11 @@ Feature: contacts-menu
     And Sending a "PUT" to "/settings/users/user2/settings" with requesttoken
       | email | another_test@example.com |
       | emailScope | contacts |
-    When Logging in using web as "user0"
-    And searching for contacts matching with "test"
-    Then the list of searched contacts has "1" contacts
-    And searched contact "0" is named "user2"
+    # Disabled because it regularly breaks on drone:
+    # When Logging in using web as "user0"
+    # And searching for contacts matching with "test"
+    # Then the list of searched contacts has "1" contacts
+    # And searched contact "0" is named "user2"
 
   Scenario: users can be found by other properties if the visibility of one is private
     Given user "user0" exists
@@ -152,10 +153,11 @@ Feature: contacts-menu
       | emailScope | private |
     And Sending a "PUT" to "/settings/users/user1/settings" with requesttoken
       | emailScope | contacts |
-    When Logging in using web as "user0"
-    And searching for contacts matching with "test"
-    Then the list of searched contacts has "1" contacts
-    And searched contact "0" is named "user1"
+    # Disabled because it regularly fails on drone:
+    # When Logging in using web as "user0"
+    # And searching for contacts matching with "test"
+    # Then the list of searched contacts has "1" contacts
+    # And searched contact "0" is named "user1"