removed regression tag from the two synchronization tests. The backgr…

…ound server needs to be rewritten somehow to synchronize when it is ready for incoming connections.

atest/asynchronous_messages/asynchronous_msg.txt

@@ -38,6 +38,7 @@ Multiple clients
     Server should receive response to sample
 Asynchronous messages on background
     [Setup]    Setup protocol, one client, background server, and define templates      Serve on background
+    [Tags]     in progress
     Load Template   sample
     Reset received messages
     Set client handler  my_handler.respond_to_sample     header_filter=messageType
@@ -47,6 +48,8 @@ Asynchronous messages on background
     client receives message    header_filter=messageType
     [Teardown]     Get background results and reset
 100 asynchronous messages on background
+    [Documentation]     This test is rather slow, so run with --exclude slow to skip this.
+    [Tags]     slow   in progress
     [Setup]    Setup protocol, one client, background server, and define templates      Loop on background
     Load Template   sample
     Reset received messages
@@ -81,7 +84,7 @@ Setup protocol, one client, background server, and define templates
     Define templates
     Start background process    ${background operation}
     Start TCP client    127.0.0.1   45555   name=client   protocol=Example
-    Sleep   2   # Unfortunately if connect fails, the same socket can not be reused. So polling becomes difficult
+    Sleep   3   # Unfortunately if connect fails, the same socket can not be reused. So polling becomes difficult
     Connect     127.0.0.1   44455
 Setup protocol, server, two clients, and define templates
     Define protocol, start tcp server and two clients    protocol=Example