[Docs] (cts): ReadBuffer waiver names GL_INVALID_OPERATION, not GL_INVALID_ENUM

This commit is contained in:
2026-10-12 03:55:47 -04:00
parent 2a1920adce
commit 53877cfb6b
+1 -1
View File
@@ -17,7 +17,7 @@
implicitly rebinds framebuffer target 0, the TRUE default implicitly rebinds framebuffer target 0, the TRUE default
framebuffer this time, not the wrapper. Restoring the captured framebuffer this time, not the wrapper. Restoring the captured
GL_COLOR_ATTACHMENTn value against the true default framebuffer 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 tokens are valid there), so the test fails with a fully
spec conformant driver. This can only happen when the harness's spec conformant driver. This can only happen when the harness's
"default framebuffer" is a real dEQP created FBO instead of a "default framebuffer" is a real dEQP created FBO instead of a