You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by sz...@apache.org on 2025/07/15 14:03:11 UTC
(nifi-minifi-cpp) 04/04: MINIFICPP-2588 Improve flaky docker tests
This is an automated email from the ASF dual-hosted git repository.
szaszm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi-minifi-cpp.git
commit aaf268b803c57e873a6ef80d9285a9f908417c15
Author: Martin Zink <ma...@apache.org>
AuthorDate: Tue Jul 15 15:44:55 2025 +0200
MINIFICPP-2588 Improve flaky docker tests
Closes #1991
Signed-off-by: Marton Szasz <sz...@apache.org>
---
.../integration/cluster/containers/KafkaBrokerContainer.py | 6 ++++++
docker/test/integration/features/consume_kafka.feature | 3 ++-
.../test/integration/features/core_functionality.feature | 2 +-
docker/test/integration/features/couchbase.feature | 12 ++++++++++--
docker/test/integration/features/grafana_loki.feature | 14 +++++++-------
docker/test/integration/features/http.feature | 14 +++++++-------
docker/test/integration/features/kinesis.feature | 1 +
docker/test/integration/features/llamacpp.feature | 2 +-
docker/test/integration/features/replace_text.feature | 2 +-
docker/test/integration/features/s3.feature | 12 ++++++------
docker/test/integration/features/sql.feature | 10 +++++-----
11 files changed, 47 insertions(+), 31 deletions(-)
diff --git a/docker/test/integration/cluster/containers/KafkaBrokerContainer.py b/docker/test/integration/cluster/containers/KafkaBrokerContainer.py
index 9e76d776e..55a7de25d 100644
--- a/docker/test/integration/cluster/containers/KafkaBrokerContainer.py
+++ b/docker/test/integration/cluster/containers/KafkaBrokerContainer.py
@@ -18,6 +18,7 @@ import logging
import tempfile
import docker.types
import jks
+import os
from OpenSSL import crypto
from .Container import Container
@@ -37,6 +38,8 @@ class KafkaBrokerContainer(Container):
server_keystore.save(server_keystore_file.name, 'abcdefgh')
self.server_keystore_file_path = server_keystore_file.name
+ os.chmod(self.server_keystore_file_path, 0o644)
+
trusted_cert = jks.TrustedCertEntry.new(
'root-ca', # Alias for the certificate
crypto.dump_certificate(crypto.FILETYPE_ASN1, feature_context.root_ca_cert)
@@ -49,6 +52,8 @@ class KafkaBrokerContainer(Container):
truststore.save(server_truststore_file.name, 'abcdefgh')
self.server_truststore_file_path = server_truststore_file.name
+ os.chmod(self.server_truststore_file_path, 0o644)
+
with tempfile.NamedTemporaryFile(delete=False, mode="w", encoding="utf-8") as jaas_config_file:
jaas_config_file.write("""
KafkaServer {
@@ -66,6 +71,7 @@ Client {
};
""")
self.jaas_config_file_path = jaas_config_file.name
+ os.chmod(self.jaas_config_file_path, 0o644)
def get_startup_finished_log_entry(self):
return "Kafka Server started"
diff --git a/docker/test/integration/features/consume_kafka.feature b/docker/test/integration/features/consume_kafka.feature
index cddb29f8f..176339edc 100644
--- a/docker/test/integration/features/consume_kafka.feature
+++ b/docker/test/integration/features/consume_kafka.feature
@@ -304,7 +304,8 @@ Feature: Receiving data from using Kafka streaming platform using ConsumeKafka
Then exactly these flowfiles are in the monitored directory's "processed" subdirectory in less than 15 seconds: "<contents_after_tiberius>"
And exactly these flowfiles are in the monitored directory's "committed" subdirectory in less than 15 seconds: "<contents_after_tiberius>"
- When a message with content "Caligula" is published to the "ConsumeKafkaTest" topic
+ When "kafka-consumer-flow" flow is stopped
+ And a message with content "Caligula" is published to the "ConsumeKafkaTest" topic
Then exactly these flowfiles are in the monitored directory's "processed" subdirectory in less than 15 seconds: "<contents_after_caligula>"
When a message with content "Claudius" is published to the "ConsumeKafkaTest" topic
diff --git a/docker/test/integration/features/core_functionality.feature b/docker/test/integration/features/core_functionality.feature
index 21b071f64..ee5290ec8 100644
--- a/docker/test/integration/features/core_functionality.feature
+++ b/docker/test/integration/features/core_functionality.feature
@@ -59,7 +59,7 @@ Feature: Core flow functionalities
Given a transient MiNiFi flow with the name "transient-minifi" is set up
And a LogOnDestructionProcessor processor with the name "logOnDestruction" in the "transient-minifi" flow
When the MiNiFi instance starts up
- Then the Minifi logs contain the following message: "LogOnDestructionProcessor is being destructed" in less than 100 seconds
+ Then the Minifi logs contain the following message: "LogOnDestructionProcessor is being destructed" in less than 40 seconds
@CORE
Scenario: Agent does not crash when using provenance repositories
diff --git a/docker/test/integration/features/couchbase.feature b/docker/test/integration/features/couchbase.feature
index 90cb0df0d..88c75020f 100644
--- a/docker/test/integration/features/couchbase.feature
+++ b/docker/test/integration/features/couchbase.feature
@@ -30,6 +30,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the LogAttribute
When a Couchbase server is started
@@ -55,6 +56,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the LogAttribute
When a Couchbase server is started
@@ -83,6 +85,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
And the "success" relationship of the GetCouchbaseKey processor is connected to the PutFile
And the "success" relationship of the PutFile processor is connected to the LogAttribute
@@ -113,6 +116,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
And the "success" relationship of the GetCouchbaseKey processor is connected to the PutFile
And the "success" relationship of the PutFile processor is connected to the LogAttribute
@@ -144,6 +148,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
And the "success" relationship of the GetCouchbaseKey processor is connected to the PutFile
And the "success" relationship of the PutFile processor is connected to the LogAttribute
@@ -173,6 +178,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
When a Couchbase server is started
@@ -197,6 +203,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
And the "success" relationship of the GetCouchbaseKey processor is connected to the PutFile
And the "success" relationship of the PutFile processor is connected to the LogAttribute
@@ -204,7 +211,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
When a Couchbase server is started
And all instances start up
- Then a flowfile with the JSON content '{"field1": "value1", "field2": "value2"}' is placed in the monitored directory in less than 6000 seconds
+ Then a flowfile with the JSON content '{"field1": "value1", "field2": "value2"}' is placed in the monitored directory in less than 60 seconds
And the Minifi logs contain the following message: "key:couchbase.bucket value:test_bucket" in less than 10 seconds
And the Minifi logs contain the following message: "key:couchbase.doc.id value:test_doc_id" in less than 1 seconds
And the Minifi logs match the following regex: "key:couchbase.doc.cas value:[1-9][0-9]*" in less than 1 seconds
@@ -226,6 +233,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
And the "failure" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
+ And the "retry" relationship of the PutCouchbaseKey processor is connected to the PutCouchbaseKey
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
And the "success" relationship of the GetCouchbaseKey processor is connected to the PutFile
And the "success" relationship of the PutFile processor is connected to the LogAttribute
@@ -233,7 +241,7 @@ Feature: Executing Couchbase operations from MiNiFi-C++
When a Couchbase server is started
And all instances start up
- Then a flowfile with the JSON content '{"field1": "value1", "field2": "value2"}' is placed in the monitored directory in less than 6000 seconds
+ Then a flowfile with the JSON content '{"field1": "value1", "field2": "value2"}' is placed in the monitored directory in less than 60 seconds
And the Minifi logs contain the following message: "key:couchbase.bucket value:test_bucket" in less than 10 seconds
And the Minifi logs contain the following message: "key:couchbase.doc.id value:test_doc_id" in less than 1 seconds
And the Minifi logs match the following regex: "key:couchbase.doc.cas value:[1-9][0-9]*" in less than 1 seconds
diff --git a/docker/test/integration/features/grafana_loki.feature b/docker/test/integration/features/grafana_loki.feature
index 3ef91c448..478d4c043 100644
--- a/docker/test/integration/features/grafana_loki.feature
+++ b/docker/test/integration/features/grafana_loki.feature
@@ -27,7 +27,7 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "Stream Labels" property of the PushGrafanaLokiREST processor is set to "job=minifi,id=docker-test"
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiREST
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published to the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published to the Grafana Loki server in less than 60 seconds
Scenario: Logs are published to Loki server to a specific tenant through REST API
Given a Grafana Loki server is set up with multi-tenancy enabled
@@ -38,7 +38,7 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "Tenant ID" property of the PushGrafanaLokiREST processor is set to "mytenant"
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiREST
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published to the "mytenant" tenant on the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published to the "mytenant" tenant on the Grafana Loki server in less than 60 seconds
Scenario: Logs are published to Loki server through REST API using SSL
Given a Grafana Loki server with SSL is set up
@@ -49,7 +49,7 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiREST
And a SSL context service is set up for Grafana Loki processor "PushGrafanaLokiREST"
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published using SSL to the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published using SSL to the Grafana Loki server in less than 60 seconds
Scenario: Logs are published to Loki server with basic authentication through REST API using a reverse proxy
Given a Grafana Loki server is set up
@@ -62,7 +62,7 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "Password" property of the PushGrafanaLokiREST processor is set to "password"
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiREST
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published to the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published to the Grafana Loki server in less than 60 seconds
Scenario: Logs are published to Loki server through gRPC
Given a Grafana Loki server is set up
@@ -72,7 +72,7 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "Stream Labels" property of the PushGrafanaLokiGrpc processor is set to "job=minifi,id=docker-test"
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiGrpc
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published to the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published to the Grafana Loki server in less than 60 seconds
Scenario: Logs are published to Loki server to a specific tenant through gRPC
Given a Grafana Loki server is set up with multi-tenancy enabled
@@ -83,7 +83,7 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "Tenant ID" property of the PushGrafanaLokiGrpc processor is set to "mytenant"
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiGrpc
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published to the "mytenant" tenant on the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published to the "mytenant" tenant on the Grafana Loki server in less than 60 seconds
Scenario: Logs are published to Loki server through gRPC using SSL
Given a Grafana Loki server with SSL is set up
@@ -94,4 +94,4 @@ Feature: MiNiFi can publish logs to Grafana Loki server
And the "success" relationship of the TailFile processor is connected to the PushGrafanaLokiGrpc
And a SSL context service is set up for Grafana Loki processor "PushGrafanaLokiGrpc"
When all instances start up
- Then "log line 1;log line 2;log line 3" lines are published using SSL to the Grafana Loki server in less than 120 seconds
+ Then "log line 1;log line 2;log line 3" lines are published using SSL to the Grafana Loki server in less than 60 seconds
diff --git a/docker/test/integration/features/http.feature b/docker/test/integration/features/http.feature
index 92789ab79..0cd01fbbb 100644
--- a/docker/test/integration/features/http.feature
+++ b/docker/test/integration/features/http.feature
@@ -35,7 +35,7 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the ListenHTTP processor is connected to the PutFile
When both instances start up
- Then at least one flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance sends data through a HTTP proxy and another one listens
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
@@ -58,7 +58,7 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the ListenHTTP processor is connected to the PutFile
When all instances start up
- Then at least one flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
And no errors were generated on the http-proxy regarding "http://minifi-listen-${feature_id}:8080/contentListener"
Scenario: A MiNiFi instance and transfers hashed data to another MiNiFi instance
@@ -76,7 +76,7 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the ListenHTTP processor is connected to the PutFile
When both instances start up
- Then at least one flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance transfers data to another MiNiFi instance without message body
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
@@ -92,7 +92,7 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the ListenHTTP processor is connected to the PutFile
When both instances start up
- Then at least one empty flowfile is placed in the monitored directory in less than 120 seconds
+ Then at least one empty flowfile is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance transfers data to a NiFi instance with message body
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
@@ -108,7 +108,7 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the ListenHTTP processor is connected to the PutFile
When both instances start up
- Then at least one flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance transfers data to another MiNiFi instance with message body and limited speed
Given a GenerateFlowFile processor with the "File Size" property set to "10 MB"
@@ -125,7 +125,7 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the ListenHTTP processor is connected to the PutFile
When both instances start up
- Then at least one flowfile with minimum size of "1 MB" is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with minimum size of "1 MB" is placed in the monitored directory in less than 60 seconds
And the Minifi logs contain the following message: "[warning] InvokeHTTP::onTrigger has been running for" in less than 10 seconds
Scenario: A MiNiFi instance retrieves data from another MiNiFi instance with message body and limited speed
@@ -148,5 +148,5 @@ Feature: Sending data using InvokeHTTP to a receiver using ListenHTTP
And the "success" relationship of the UpdateAttribute processor is connected to the ListenHTTP
When both instances start up
- Then at least one flowfile with minimum size of "10 MB" is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with minimum size of "10 MB" is placed in the monitored directory in less than 60 seconds
And the Minifi logs contain the following message: "[warning] InvokeHTTP::onTrigger has been running for" in less than 10 seconds
diff --git a/docker/test/integration/features/kinesis.feature b/docker/test/integration/features/kinesis.feature
index 2f68fd77c..95f5464fb 100644
--- a/docker/test/integration/features/kinesis.feature
+++ b/docker/test/integration/features/kinesis.feature
@@ -29,6 +29,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS Kinesis server
And a PutFile processor with the "Directory" property set to "/tmp/output"
And the "success" relationship of the GetFile processor is connected to the PutKinesisStream
And the "success" relationship of the PutKinesisStream processor is connected to the PutFile
+ And the "failure" relationship of the PutKinesisStream processor is connected to the PutKinesisStream
And a kinesis server is set up in correspondence with the PutKinesisStream
diff --git a/docker/test/integration/features/llamacpp.feature b/docker/test/integration/features/llamacpp.feature
index de8072d39..65f5a08db 100644
--- a/docker/test/integration/features/llamacpp.feature
+++ b/docker/test/integration/features/llamacpp.feature
@@ -29,4 +29,4 @@ Feature: Run language model inference using LlamaCpp processor
And the "success" relationship of the RunLlamaCppInference processor is connected to the LogAttribute
When all instances start up
- Then the Minifi logs contain the following message: "banana" in less than 120 seconds
+ Then the Minifi logs contain the following message: "banana" in less than 60 seconds
diff --git a/docker/test/integration/features/replace_text.feature b/docker/test/integration/features/replace_text.feature
index 71166e3a4..e283bcf35 100644
--- a/docker/test/integration/features/replace_text.feature
+++ b/docker/test/integration/features/replace_text.feature
@@ -31,7 +31,7 @@ Feature: Changing flowfile contents using the ReplaceText processor
And the "success" relationship of the GenerateFlowFile processor is connected to the ReplaceText
And the "success" relationship of the ReplaceText processor is connected to the PutFile
When the MiNiFi instance starts up
- Then a flowfile with the content "<output>" is placed in the monitored directory in less than 10 seconds
+ Then a flowfile with the content "<output>" is placed in the monitored directory in less than 100 seconds
Examples:
| input | replacement_strategy | search_value | replacement_value | output |
diff --git a/docker/test/integration/features/s3.feature b/docker/test/integration/features/s3.feature
index 6a85e0dea..1aa41e959 100644
--- a/docker/test/integration/features/s3.feature
+++ b/docker/test/integration/features/s3.feature
@@ -75,7 +75,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
And the http proxy server is set up
When all instances start up
- Then a flowfile with the content "test" is placed in the monitored directory in less than 150 seconds
+ Then a flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
And the object on the s3 server is "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"
And the object content type on the s3 server is "application/octet-stream" and the object metadata matches use metadata
And no errors were generated on the http-proxy regarding "http://s3-server-${feature_id}:9090/test_bucket/test_object_key"
@@ -96,7 +96,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
When both instances start up
- Then a flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then a flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
And the object bucket on the s3 server is empty
Scenario: Deletion of a non-existent s3 object succeeds
@@ -111,7 +111,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
When both instances start up
- Then a flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then a flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
And the object bucket on the s3 server is empty
Scenario: Deletion of a s3 object through a proxy-server succeeds
@@ -137,7 +137,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
When all instances start up
- Then a flowfile with the content "test" is placed in the monitored directory in less than 150 seconds
+ Then a flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
And the object bucket on the s3 server is empty
And no errors were generated on the http-proxy regarding "http://s3-server-${feature_id}:9090/test_bucket/test_object_key"
@@ -159,7 +159,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
When all instances start up
- Then a flowfile with the content "test" is placed in the monitored directory in less than 120 seconds
+ Then a flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance can download s3 bucket objects via a http-proxy
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
@@ -186,7 +186,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
When all instances start up
- Then a flowfile with the content "test" is placed in the monitored directory in less than 150 seconds
+ Then a flowfile with the content "test" is placed in the monitored directory in less than 60 seconds
And no errors were generated on the http-proxy regarding "http://s3-server-${feature_id}:9090/test_bucket/test_object_key"
Scenario: A MiNiFi instance can list an S3 bucket directly
diff --git a/docker/test/integration/features/sql.feature b/docker/test/integration/features/sql.feature
index e3edfdf06..722897bf4 100644
--- a/docker/test/integration/features/sql.feature
+++ b/docker/test/integration/features/sql.feature
@@ -31,7 +31,7 @@ Feature: Executing SQL operations from MiNiFi-C++
And an ODBCService is setup up for PutSQL with the name "ODBCService"
And a PostgreSQL server is set up
When all instances start up
- Then the query "SELECT * FROM test_table WHERE int_col = 42" returns 1 rows in less than 120 seconds on the PostgreSQL server
+ Then the query "SELECT * FROM test_table WHERE int_col = 42" returns 1 rows in less than 60 seconds on the PostgreSQL server
Scenario: A MiNiFi instance can query to test table with ExecuteSQL processor
Given a MiNiFi CPP server with yaml config
@@ -47,7 +47,7 @@ Feature: Executing SQL operations from MiNiFi-C++
And an ODBCService is setup up for ExecuteSQL with the name "ODBCService"
And a PostgreSQL server is set up
When all instances start up
- Then at least one flowfile with the content '[{"int_col":2,"text_col":"banana"},{"int_col":1,"text_col":"apple"}]' is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content '[{"int_col":2,"text_col":"banana"},{"int_col":1,"text_col":"apple"}]' is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance can query to test table containing mixed case column names with ExecuteSQL processor
Given a GenerateFlowFile processor with the "File Size" property set to "0B"
@@ -63,7 +63,7 @@ Feature: Executing SQL operations from MiNiFi-C++
And an ODBCService is setup up for ExecuteSQL with the name "ODBCService"
And a PostgreSQL server is set up
When all instances start up
- Then at least one flowfile with the content '[{"int_col":6,"tExT_Col":"BaNaNa"},{"int_col":5,"tExT_Col":"ApPlE"}]' is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content '[{"int_col":6,"tExT_Col":"BaNaNa"},{"int_col":5,"tExT_Col":"ApPlE"}]' is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance can query to test table with QueryDatabaseTable processor
Given a QueryDatabaseTable processor with the "Table Name" property set to "test_table"
@@ -75,7 +75,7 @@ Feature: Executing SQL operations from MiNiFi-C++
And an ODBCService is setup up for QueryDatabaseTable with the name "ODBCService"
And a PostgreSQL server is set up
When all instances start up
- Then at least one flowfile with the content '[{"text_col":"apple"}]' is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content '[{"text_col":"apple"}]' is placed in the monitored directory in less than 60 seconds
Scenario: A MiNiFi instance can query to test table containing mixed case column names with QueryDatabaseTable processor
Given a QueryDatabaseTable processor with the "Table Name" property set to "test_table2"
@@ -87,4 +87,4 @@ Feature: Executing SQL operations from MiNiFi-C++
And an ODBCService is setup up for QueryDatabaseTable with the name "ODBCService"
And a PostgreSQL server is set up
When all instances start up
- Then at least one flowfile with the content '[{"tExT_Col":"ApPlE"}]' is placed in the monitored directory in less than 120 seconds
+ Then at least one flowfile with the content '[{"tExT_Col":"ApPlE"}]' is placed in the monitored directory in less than 60 seconds