REGRESSION: [ Macmini6,2 ] webgl/2.0.0/conformance/renderbuffers/framebuffer-object-attachment.html is failing
https://bugs.webkit.org/show_bug.cgi?id=205735
Summary REGRESSION: [ Macmini6,2 ] webgl/2.0.0/conformance/renderbuffers/framebuffer-...
Attachments
Radar WebKit Bug Importer
Comment 1 2020-01-03 11:04:38 PST
Alexey Proskuryakov
Comment 2 2020-01-03 12:21:08 PST
This looks like a Macmini6,2 issue, as the test started to fail on newer OS versions internally, but always on this hardware model. Which is surprising, because MacBookAir5,2 also has Intel HD Graphics 4000, and it hasn't failed once yet.
Kenneth Russell
Comment 3 2020-01-05 11:05:53 PST
The four portions of this test which fail are: ... +[ 469: PASS ] gl.checkFramebufferStatus(gl.FRAMEBUFFER) returned 36053 +[ 470: PASS ] gl.getParameter(gl.RED_BITS) + gl.getParameter(gl.GREEN_BITS) + gl.getParameter(gl.BLUE_BITS) + gl.getParameter(gl.ALPHA_BITS) >= 16 is true +[ 471: PASS ] gl.getParameter(gl.DEPTH_BITS) >= 16 is true +[ 472: PASS ] gl.getParameter(gl.STENCIL_BITS) >= 8 is true +[ 473: PASS ] gl.checkFramebufferStatus(gl.FRAMEBUFFER) is gl.FRAMEBUFFER_COMPLETE +[ 474: FAIL ] should be green at (0, 0) expected: 0,255,0,255 was 0,0,0,0 +[ 475: PASS ] gl.checkFramebufferStatus(gl.FRAMEBUFFER) is gl.FRAMEBUFFER_COMPLETE +[ 476: PASS ] getError was expected value: NO_ERROR : +[ 477: FAIL ] should be green at (0, 0) expected: 0,255,0,255 was 0,0,0,0 +[ 478: PASS ] gl.checkFramebufferStatus(gl.FRAMEBUFFER) is gl.FRAMEBUFFER_COMPLETE +[ 479: FAIL ] should be green at (0, 0) expected: 0,255,0,255 was 0,0,0,0 +[ 480: PASS ] gl.checkFramebufferStatus(gl.FRAMEBUFFER) is gl.FRAMEBUFFER_COMPLETE +[ 481: PASS ] getError was expected value: NO_ERROR : +[ 482: FAIL ] should be green at (0, 0) expected: 0,255,0,255 was 0,0,0,0 +[ 483: PASS ] gl.checkFramebufferStatus(gl.FRAMEBUFFER) is gl.FRAMEBUFFER_COMPLETE +[ 484: PASS ] should be green ... Rendering to one of the test's framebuffers is failing, and producing all black.
Note You need to log in before you can comment on or make changes to this bug.