From 53877cfb6b8b08dd788d6f3ca40ceea580025568 Mon Sep 17 00:00:00 2001 From: Swung0x48 Date: Mon, 12 Oct 2026 03:51:59 -0400 Subject: [PATCH] [Docs] (cts): ReadBuffer waiver names GL_INVALID_OPERATION, not GL_INVALID_ENUM --- tools/cts/waivers/mobilegl-fbo-harness.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/cts/waivers/mobilegl-fbo-harness.xml b/tools/cts/waivers/mobilegl-fbo-harness.xml index fc7d57a1..61c39cbb 100644 --- a/tools/cts/waivers/mobilegl-fbo-harness.xml +++ b/tools/cts/waivers/mobilegl-fbo-harness.xml @@ -17,7 +17,7 @@ implicitly rebinds framebuffer target 0, the TRUE default framebuffer this time, not the wrapper. Restoring the captured GL_COLOR_ATTACHMENTn value against the true default framebuffer - correctly raises GL_INVALID_ENUM per spec (only FRONT/BACK style + correctly raises GL_INVALID_OPERATION per spec (only FRONT/BACK style tokens are valid there), so the test fails with a fully spec conformant driver. This can only happen when the harness's "default framebuffer" is a real dEQP created FBO instead of a