DaanHoogland commented on PR #5588: URL: https://github.com/apache/cloudstack/pull/5588#issuecomment-1103187092
> @DaanHoogland travis failed again > ``` > Printing marvin logs /tmp//MarvinLogs/test_metrics_api_RXRJMF/results.txt : > test_list_clusters_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_clusters_metrics | Status : SUCCESS === > ok > test_list_db_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_db_metrics | Status : SUCCESS === > ok > test_list_hosts_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_hosts_metrics | Status : SUCCESS === > ok > test_list_infrastructure_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_infrastructure_metrics | Status : SUCCESS === > ok > test_list_management_server_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_management_server_metrics | Status : FAILED === > FAIL > test_list_pstorage_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_pstorage_metrics | Status : SUCCESS === > ok > test_list_usage_server_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_usage_server_metrics | Status : FAILED === > FAIL > test_list_vms_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_vms_metrics | Status : SUCCESS === > ok > test_list_volumes_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_volumes_metrics | Status : SUCCESS === > ok > test_list_zones_metrics (integration.smoke.test_metrics_api.TestMetrics) ... === TestName: test_list_zones_metrics | Status : SUCCESS === > ok > ``` I know @weizhouapache , ran those tests in a nested environment and they passed, I'll try a simulator tomorrow, maybe that is the problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
