From 0bc59ab239b92c11da6614f4c54f955f7b302066 Mon Sep 17 00:00:00 2001 From: Swung0x48 Date: Tue, 22 Sep 2026 21:31:47 -0400 Subject: [PATCH] [MG_IntegrationTest] (P7): the unarmed-expected file stops misquoting tier 3s count - the first class said its 22 names were "the same 13 entries per backend that tier 3 measured as reds", which is wrong twice: 13 was the whole count, not a per-backend one, and those 13 (AdvertisedLimitsScenario x8, SpirvShaderBinaryScenario x4, ProgramPipelineScenario's reserved name) are spread across this class and the next - the sentence now says what tier 3 actually measured and why it is the same property seen from the other side --- .../Harness/verify-split-unarmed-expected.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/MobileGL/MG_IntegrationTest/Harness/verify-split-unarmed-expected.txt b/MobileGL/MG_IntegrationTest/Harness/verify-split-unarmed-expected.txt index 5c6bc713..551f78a9 100644 --- a/MobileGL/MG_IntegrationTest/Harness/verify-split-unarmed-expected.txt +++ b/MobileGL/MG_IntegrationTest/Harness/verify-split-unarmed-expected.txt @@ -37,9 +37,11 @@ # CAPS, LIMITS AND EXTENSION ADVERTISEMENT - answered from the client's CapsMirror, no verb (22) # These call glGetIntegerv / glGetString / glGetInternalformativ and compare the answer # against a floor or against the other width of the same query. Nothing in them reaches a fill -# point, so the arming line - latched at the process's FIRST fill - is honestly absent. They are -# the same 13 entries per backend that tier 3 measured as reds under MGITEST_SPLIT_LANE=1, for -# the same reason (a query answered without moving the encoder's record ordinal). +# point, so the arming line - latched at the process's FIRST fill - is honestly absent. This is +# the same property tier 3 measured from the other side: its 13 reds under MGITEST_SPLIT_LANE=1 +# (AdvertisedLimitsScenario x8, SpirvShaderBinaryScenario x4, ProgramPipelineScenario's reserved +# name) were all queries answered without moving the encoder's record ordinal, and they are +# spread across this class and the next one - which is why this lane sets no such marker. # -------------------------------------------------------------------------------------------- DirectGLES.VerifySplit.AdvertisedLimitsScenario.ComputeLocalSizeComesFromTheLinkedProgram DirectGLES.VerifySplit.AdvertisedLimitsScenario.ComputeUniformBlocksIsAnAmountAnApplicationCouldActuallyAllocate