Please make the CI pass, thanks!

I don't know why this ci error is reported here, Would you give me some suggestion.

Please make the CI pass, thanks!

I don't know why this ci error is reported here, Would you give me some suggestion.

The error message is:

Bailout called.  Further testing stopped:  t/plugin/prometheus.t TEST 42: fetch the prometheus multiple shared dict data - You asked for many requests, the expected results should be arrays as well.
FAILED--Further testing stopped: t/plugin/prometheus.t TEST 42: fetch the prometheus multiple shared dict data - You asked for many requests, the expected results should be arrays as well.

You can look up it.

Please make the CI pass, thanks!

I don't know why this ci error is reported here, Would you give me some suggestion.

The error message is:

Bailout called.  Further testing stopped:  t/plugin/prometheus.t TEST 42: fetch the prometheus multiple shared dict data - You asked for many requests, the expected results should be arrays as well.
FAILED--Further testing stopped: t/plugin/prometheus.t TEST 42: fetch the prometheus multiple shared dict data - You asked for many requests, the expected results should be arrays as well.

You can look up it.

The error message report that You asked for many requests, the expected results should be arrays as well., but the test case is:

=== TEST 42: fetch the prometheus multiple shared dict data
--- request eval
["GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics",
"GET /apisix/prometheus/metrics"]
--- response_body_like eval
[qr/.*apisix_shared_dict_capacity_bytes{name="internal-status"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="internal-status"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="upstream-healthcheck"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="upstream-healthcheck"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="worker-events"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="worker-events"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="lrucache-lock"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="lrucache-lock"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="balancer-ewma"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="balancer-ewma"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="balancer-ewma-locks"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="balancer-ewma-locks"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="balancer-ewma-last-touched-at"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="balancer-ewma-last-touched-at"} \d+.*/,
qr/.*apisix_shared_dict_capacity_bytes{name="etcd-cluster-health-check"} \d+(?:.|\n)*
apisix_shared_dict_free_space_bytes{name="etcd-cluster-health-check"} \d+.*/]

which has a array result. and commit dbf7e7e have a similar test case:

The error message report that You asked for many requests, the expected results should be arrays as well., but the test case is:

It does seem strange, so if you don't know how to modify it, consider a different type of validation.

The error message report that You asked for many requests, the expected results should be arrays as well., but the test case is:

It does seem strange, so if you don't know how to modify it, consider a different type of validation.

You are right! I found a new type of validation, it maybe more suitable.

Is the error a false report?

Is the error a false report?

rerun

@ccxhwmy could you update the apisix-grafana-dashboard meta for shared dict?

@ccxhwmy could you update the apisix-grafana-dashboard meta for shared dict?

Yes, I can.

@ccxhwmy could you update the apisix-grafana-dashboard meta for shared dict?

Yes, I can.

Thanks a lot, let's do it in another PR.

I have update the apisix-grafana-dashboard meta for shared dict in the (PR)[https://github.com//pull/7529].