[MG_IntegrationTest] (P7): the split poison control says which role fired, not merely that someone did

- ReadChildLog concatenated the child's two role halves and the assertion searched the union, so VerifySplitPoisonOmitted. would have been just as green if the stamp the knob withheld had been the CLIENT's - which is the case it exists to rule out, the mechanism under test being the server-side verb stamp honouring MOBILEGL_PIPE_POISON_OMIT
- kOmittedPairs carries FiresOnTheServer; ReadChildLogHalves keeps Client, Server and the union apart; the split pair now asserts the Fatal in the child's SERVER half under MOBILEGL_BUILD_DISAGGREGATED, the monolith pair keeps the union because it has one role
- measured on both backends: client half 0 Fatal{UnmigratedPipeInput lines, server half 1 each - the union search could not tell them apart
- monolith PoisonOmitted. entries stay green (2/2), split VerifySplitPoisonOmitted. stay green (2/2)
This commit is contained in:
2026-09-22 21:35:06 -04:00
parent e9b3f5fe04
commit 2424c8209d
2 changed files with 61 additions and 10 deletions
@@ -213,6 +213,13 @@ server 半边日志:
[mgl-srv-apply/FATAL]: MGPipe: Fatal{UnmigratedPipeInput, "GetPixelStoreParameters@ReadPixels"}
```
**正形条目断言的是「哪个角色」,不是「有没有人」(V1 修复轮补)。** `ReadChildLog()` 把子进程的 client 与 server
两个半边连起来,原断言查的是并集——而这一对配对存在的理由恰恰是 **server 自己的 verb stamp 遵守 knob**
(`ServerPoisonOmission`),一个 client 侧的触发会同样满足并集、却证明了相反的事。现在 `kOmittedPairs` 每对带
`FiresOnTheServer`,split 那一对额外断言 Fatal 出现在**子进程的 server 半边**里。实测两后端:client 半边
`Fatal{UnmigratedPipeInput` **0 行**,server 半边**各 1 行**——并集断言此前确实分辨不出来。monolith 那一对只有一个
角色,仍查并集。
正形条目 `VerifySplitCorrupted.` / `VerifySplitReadCorrupted.` / `VerifySplitPoisonOmitted.` 两后端 6/6 绿。
### 3.2 发现 C:monolith 的 POISON_OMIT 配对在 split 臂上是哑的