You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workload benchmark testing were performed for Release of v4.6.0-pre-alpha1
Running manually reliability/test_cluster/test_cluster_logs/test_cluster_connection/test_cluster_connection.py::test_cluster_connection over artifacts created by workload benchmark pipeline (It should be fixed #4299) it is possible to find that the cluster_connection test is not finding the correct pattern in cluster log releasing the following message:
Failed: Could not find "Sucessfully connected to master" message in the worker_21
However, checking manually the logs, it could be checked that the message was in the worker_21's cluster.log
2023/07/25 09:27:01 INFO: [Worker CLUSTER-Workload_benchmarks_metrics_B274_manager_21] [Main] Successfully connected to master.
Current behavior
Error message:
Failed: Could not find "Sucessfully connected to master" message in the worker_21
Expected behavior
Finding the log and passing the test without error messages.
The text was updated successfully, but these errors were encountered:
Description
Workload benchmark testing were performed for Release of v4.6.0-pre-alpha1
Running manually reliability/test_cluster/test_cluster_logs/test_cluster_connection/test_cluster_connection.py::test_cluster_connection over artifacts created by workload benchmark pipeline (It should be fixed #4299) it is possible to find that the cluster_connection test is not finding the correct pattern in cluster log releasing the following message:
Failed: Could not find "Sucessfully connected to master" message in the worker_21
However, checking manually the logs, it could be checked that the message was in the worker_21's cluster.log
Current behavior
Error message:
Expected behavior
Finding the log and passing the test without error messages.
The text was updated successfully, but these errors were encountered: