mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-09-12 06:08:30 +09:00
[Test] (Espryt): assert a glTexParameter on a texture that only ever was an attachment, an image binding or a copy endpoint reaches the driver
This commit is contained in:
@@ -133,6 +133,7 @@ add_executable(MobileGLIntegrationTest
|
||||
Scenarios/HandleRecycleScenario.cpp
|
||||
Scenarios/CsoContentAddressingScenario.cpp
|
||||
Scenarios/ResourceSubsystemControlScenario.cpp
|
||||
Scenarios/TextureParamsWithoutASamplerViewScenario.cpp
|
||||
)
|
||||
|
||||
target_include_directories(MobileGLIntegrationTest PRIVATE
|
||||
@@ -1321,6 +1322,25 @@ gtest_discover_tests(MobileGLIntegrationTest
|
||||
ENVIRONMENT "${MGL_ITEST_GLES_ARENA_SUBSYSTEM_OFF_ENVIRONMENT}"
|
||||
)
|
||||
|
||||
# --- G9: the mandatory red-before scenario -------------------------------------------
|
||||
#
|
||||
# TextureParamsWithoutASamplerViewScenario needs NO lane of its own, and that is deliberate rather
|
||||
# than an omission. It reads no counter and no log - its observable is a sampled colour - and its
|
||||
# claim is about the SHIPPING configuration, so the two ambient registrations at the top of this
|
||||
# file (which run at the build's default mask) are exactly the arms it wants. A lane here would pin
|
||||
# a mask and make the entry stop describing what ships the next time the default moved. The
|
||||
# DirectVulkan ambient entries skip in the scenario's SetUp, naming the backend: the gap it is about
|
||||
# is Espryt's SyncAttachmentObject / SyncNeccessaryTextures pair and P4a touches no DirectVulkan
|
||||
# source but MagmaPipeArms.h (D-Q).
|
||||
#
|
||||
# D-E3 expects its second case, AReadAttachmentOnlyTexturesDepthStencilModeReachesTheDriver, to be
|
||||
# RED until package esprytobj lands. MEASURED ON THE CONTRACT COMMIT IT IS GREEN, and the scenario's
|
||||
# header carries the mechanism: a texture parameter's only public-GL observable is a sample, and the
|
||||
# sample repairs the state it was meant to catch (the unit sync list re-syncs whenever the params
|
||||
# version moved). Nothing about any of that is expressed in this file - a registration that
|
||||
# "expected" a red would be a gate that could never go green - and the ruling on the missing
|
||||
# artefact is the integrator's, recorded in the gates result document.
|
||||
|
||||
if (MOBILEGL_PIPE_VERIFY)
|
||||
# 900s, not the ambient 120: the comparator re-reads every field of the fill mask at the verb
|
||||
# boundary and again at every accessor read, which the design budgets at 5-10x.
|
||||
|
||||
Reference in New Issue
Block a user