Skip to content

fix(e2e): treat ERR_PROXY_TUNNEL as proxy wiring success in M12 test #3880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kagura-agent wants to merge 1 commit into from
Closed

fix(e2e): treat ERR_PROXY_TUNNEL as proxy wiring success in M12 test #3880

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion test/e2e/docs/parity-inventory.generated.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8849,7 +8849,15 @@
},
{
"script": "test/e2e/test-messaging-providers.sh",
"line": 1264,
"line": 1263,
"text": "M12: Node.js routed through proxy (proxy policy blocked destination: ${tg_reach:0:160})",
"polarity": "pass",
"normalized_id": "m12.node.js.routed.through.proxy.policy.blocked.destination",
"mapping_status": "deferred"
},
{
"script": "test/e2e/test-messaging-providers.sh",
"line": 1270,
"text": "M12: Node.js could not reach api.telegram.org (${tg_reach:0:200})",
"polarity": "fail",
"normalized_id": "m12.node.js.could.not.reach.api.telegram.org.tg.reach.0.200",
Expand Down
5 changes: 5 additions & 0 deletions test/e2e/test-messaging-providers.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1282,6 +1282,11 @@ if echo "$tg_reach" | grep -q "HTTP_"; then
pass "M12: Node.js reached api.telegram.org (${tg_reach})"
elif echo "$tg_reach" | grep -q "TIMEOUT"; then
skip "M12: api.telegram.org timed out (network may be slow)"
elif echo "$tg_reach" | grep -qiE "ERROR:.*(ERR_PROXY_TUNNEL|PROXY_CONNECTION_LOST)"; then
# ERR_PROXY_TUNNEL means Node routed through the proxy and the proxy issued
# a non-2xx CONNECT response (e.g. 403 Forbidden). This proves proxy *wiring*
# is correct — the failure is upstream proxy policy, not NemoClaw configuration.
pass "M12: Node.js routed through proxy (proxy policy blocked destination: ${tg_reach:0:160})"
elif echo "$tg_reach" | grep -qiE "ERROR:.*(ECONNRESET|reset|socket hang up|ENETUNREACH|EHOSTUNREACH|ETIMEDOUT)"; then
skip "M12: api.telegram.org unreachable from this network (${tg_reach:0:160})"
else
Expand Down
Loading