[
https://issues.apache.org/jira/browse/MINIFICPP-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Zink updated MINIFICPP-1641:
-----------------------------------
Description:
Currently docker tests (docker-verify target) is run sequentially. This is not
scalable. Consider exploring the parallelization options of behave,
multiprocess and multithreading under Python. Also pay attention to available
CPU cores on GitHub CI and if it is possible to increase them.
The main problem is that containers are referenced by name only. We should
postfix them based on the scenario and iron out any problems that arise.
* attributes_to_json.feature
* azure_storage.feature
* core_functionality.feature
* defragtextflowfiles.feature
* elasticsearch.feature
* file_system_operations.feature
* google_cloud_storage.feature
* hashcontent.feature
* http.feature
* https.feature
* kafka.feature
* kubernetes_logging.feature
* kubernetes_metrics.feature
* lua_script.feature
* minifi_c2_server.feature
* mqtt.feature
* network_listener.feature
* opcua.feature
* opensearch.feature
* prometheus.feature
* python.feature
* python_script.feature
* python_with_modules.feature
* replace_text.feature
* routetext.feature
* s2s.feature
* s3.feature
* splunk.feature
* sql.feature
* syslog_listener.feature
was:Currently docker tests (docker-verify target) is run sequentially. This
is not scalable. Consider exploring the parallelization options of behave,
multiprocess and multithreading under Python. Also pay attention to available
CPU cores on GitHub CI and if it is possible to increase them.
> Parallel running of docker tests
> --------------------------------
>
> Key: MINIFICPP-1641
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1641
> Project: Apache NiFi MiNiFi C++
> Issue Type: Test
> Reporter: Ádám Markovics
> Assignee: Martin Zink
> Priority: Minor
>
> Currently docker tests (docker-verify target) is run sequentially. This is
> not scalable. Consider exploring the parallelization options of behave,
> multiprocess and multithreading under Python. Also pay attention to available
> CPU cores on GitHub CI and if it is possible to increase them.
> The main problem is that containers are referenced by name only. We should
> postfix them based on the scenario and iron out any problems that arise.
> * attributes_to_json.feature
> * azure_storage.feature
> * core_functionality.feature
> * defragtextflowfiles.feature
> * elasticsearch.feature
> * file_system_operations.feature
> * google_cloud_storage.feature
> * hashcontent.feature
> * http.feature
> * https.feature
> * kafka.feature
> * kubernetes_logging.feature
> * kubernetes_metrics.feature
> * lua_script.feature
> * minifi_c2_server.feature
> * mqtt.feature
> * network_listener.feature
> * opcua.feature
> * opensearch.feature
> * prometheus.feature
> * python.feature
> * python_script.feature
> * python_with_modules.feature
> * replace_text.feature
> * routetext.feature
> * s2s.feature
> * s3.feature
> * splunk.feature
> * sql.feature
> * syslog_listener.feature
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
