anton-vinogradov commented on PR #13357: URL: https://github.com/apache/ignite/pull/13357#issuecomment-4939898182
CI verification on the affected suites (ci2, branch `pull/13357/head`): | Suite | Before (broken runs) | With this PR | |---|---|---| | Platform .NET (Windows) | hung at 1490 passed → 120 min execution timeout | **SUCCESS, 2039 tests, full run** (build 9199018) | | Platform .NET (Windows) 2 | hung at 1342 | **full run, 1428 tests** (build 9199016); the single failure is `IgniteConfigurationTest.TestMulticastIpFinder` — a pre-existing flaky (28 failures in the last 40 runs across master and unrelated PRs) | | Platform .NET (Windows) 3 | hung at 78, then at 285 | **full run, all 301 tests executed** (build 9199026; the second commit was needed — see below): 7 fast failures instead of an endless hang | Two findings from these runs: 1. **A second hang point existed in Windows 3** (matches historical master timeouts at "passed: 277-285", e.g. build 9196929): `EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup` starts a node through the parameterless `IgniteDbConfiguration()`, which reads the `igniteConfiguration` section of the *EntityFramework tests' own* `app.config` — and that section had the same copy-pasted pattern: `myGrid1` without `localhost`, while `myGrid2` next to it has one. Same for `AspNet.Tests/App.config`. The second commit adds `localhost` / `joinTimeout` there as well; after it, Windows 3 runs to completion. 2. **The root environment problem on the agents is now visible** thanks to the fail-fast: the `ClientClusterDiscoveryTestsNoLocalhost` failures show the node resolving its local addresses to `addrs=[10.19.0.202]` — **the loopback interface is missing from the enumeration** on the CI Windows agents (healthy runs announce loopback too and interconnect via `::1`/`127.0.0.1`). Such a node does not recognize the IP finder's `127.0.0.1:47500` as itself, sends a join request to its own listener and waits for an answer that never comes: "Failed to send message to address [addr=/127.0.0.1:47500, msg=TcpDiscoveryJoinRequestMessage...]". With the default `joinTimeout=0` this retried forever — that was the hang; now it fails in ~2 minutes with a clear message. The remaining 7 red tests in Windows 3 are exactly this environment issue and should disappear once loopback enumeration on publicagent01..03 is fixed (it broke around Jul 6-8) — that part is for INFRA/agent admins, the suites the mselves no longer hang either way. (Note: build 9199026 formally shows "Canceled" — the agent process died during artifact publishing after all 301 tests had executed; yet another symptom of the current agent instability. Re-run queued for a clean status.) -- 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]
