From ff286afbf1fd0fddef239449f7f5a8d870e46cba Mon Sep 17 00:00:00 2001 From: Wu Sheng Date: Sat, 7 Nov 2026 08:03:33 +0800 Subject: [PATCH] Keep the basic e2e trigger running until verification ends infra-e2e #132 (pulled in by the cf589b4 -> 56ac8be bump in #240) makes the http trigger stop after `times` requests. Before it, `times` only decided when the trigger reported its first result, and the requests kept going until the verify phase finished. The basic case's `times: 10` now means 30 seconds of traffic, and the nightly CI failed on 3 of the 4 nights since #240, every time on `metrics linear service_relation_client_cpm`, whose whole 30-minute window came back empty while the other 15 cases passed. `times: -1` (endless, infra-e2e #134) restores the continuous traffic, the same as the live-debugging case. --- test/cases/basic/test.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/test/cases/basic/test.yaml b/test/cases/basic/test.yaml index c094692..33c8df4 100644 --- a/test/cases/basic/test.yaml +++ b/test/cases/basic/test.yaml @@ -26,7 +26,10 @@ setup: trigger: action: http interval: 3s - times: 10 + # Continuous traffic until the verify phase ends. The client-side relation metrics + # (service_relation_client_cpm, ...) need the OAP to resolve the consumer's exit + # peer to the provider service, which a short burst of requests may not outlast. + times: -1 url: http://${consumer_host}:${consumer_9090}/users method: POST