envoyproxy/envoy

Non-hermetic DNS testing in eg dynamic_forward_proxy is causing recurring failure/slowness

Open

#42,217 建立於 2025年11月24日

在 GitHub 查看
 (24 留言) (0 反應) (0 負責人)C++ (27,997 star) (5,373 fork)batch import
area/ciarea/dynamic_forward_proxyarea/test flakesbughelp wanted

描述

I stumbled upon this issue with the mobile test //test/common/integration:client_integration_test

in that case the test had a total timeout and was querying dns for doesnotexist - dns was retrying 3x, and taking 5+ seconds to respond on each try - blowing the tests total timeout budget

im struggling to find how i resolved the issue in mobile - but it seems i got past it

this problem has again occurred when trying to update the build image - asan and gcc are reliably timeouting on similar tests - and it looks like for similar reasons

i would have thought these tests should not be calling any real dns - it should be mocked and hermetic

貢獻者指南

技術棧
cpp
領域
backendtestingperformance
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
C++ basicsUnderstanding of DNSFamiliarity with Envoy test framework
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the specific test `//test/common/integration:client integration test` and similar dynamic forward proxy tests to identify where real DNS queries are made. Look into mocking DNS responses using the test infrastructure, possibly by injecting a fake DNS resolver or using a simulated network. Examine any existing PRs or comments mentioning DNS mocking to understand prior attempts. The goal is to ensure all DNS queries in tests are hermetic and do not rely on external network calls.