mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-09-08 04:08:32 +09:00
BZLZHH
1c5f6c0986
Two harness settings were producing failures that say nothing about the backend: - dEQP's FboRenderContext picks the first entry of its own depth/stencil format list, GL_DEPTH32F_STENCIL8, when the config leaves the bit counts DONT_CARE. framebuffer_blit meanwhile hardcodes GL_DEPTH24_STENCIL8 for its own buffers as soon as it detects an FBO surface, and then blits depth between the two - which the spec forbids for mismatched formats, so a conformant driver has no choice but to fail it. Default to --deqp-gl-config-name=rgba8888d24s8 so the wrapper framebuffer and the test agree. - --deqp-watchdog aborts the whole process when one case exceeds a hardcoded 30 seconds (framework/common/tcuApp.hpp). That is not a hang on a CPU rasterizer: several texture_swizzle cases take ~17s each standalone and cross the limit once the process is warm, which came back as ten spurious Timeouts. dEQP's own default is off, and --chunk-timeout is what actually rescues a genuinely wedged case, so default it off too and leave it selectable.