Bug 229934 – webgl/1.0.x/conformance/extensions/webgl-depth-texture.html fails on AS

• Status: NEW
• Component: WebGL

[Kimmo Kinnunen]

webgl/1.0.x/conformance/extensions/webgl-depth-texture.html fails on AS

testing LINEAR filtering
PASS getError was expected value: INVALID_OPERATION : after evaluating: gl.texImage2D(gl.TEXTURE_2D, 1, gl.DEPTH_COMPONENT, 1, 1, 0, gl.DEPTH_COMPONENT, gl.UNSIGNED_SHORT, null)
PASS getError was expected value: INVALID_OPERATION : after evaluating: gl.texImage2D(gl.TEXTURE_2D, 0, gl.DEPTH_COMPONENT, 1, 1, 0, gl.DEPTH_COMPONENT, gl.UNSIGNED_SHORT, new Uint16Array(1))
PASS getError was one of: INVALID_VALUE or INVALID_ENUM or INVALID_OPERATION : after evaluating: gl.texImage2D(gl.TEXTURE_2D, 0, gl.DEPTH_COMPONENT, gl.DEPTH_COMPONENT, gl.UNSIGNED_SHORT, canvas2)
PASS getError was one of: INVALID_ENUM or INVALID_OPERATION : after evaluating: gl.copyTexImage2D(gl.TEXTURE_2D, 0, gl.DEPTH_COMPONENT, 0, 0, 1, 1, 0)
PASS getError was expected value: NO_ERROR : after evaluating: gl.texImage2D(gl.TEXTURE_2D, 0, gl.DEPTH_COMPONENT, 2, 2, 0, gl.DEPTH_COMPONENT, gl.UNSIGNED_SHORT, null)
PASS getError was expected value: INVALID_OPERATION : after evaluating: gl.texSubImage2D(gl.TEXTURE_2D, 0, 0, 0, 1, 1, gl.DEPTH_COMPONENT, gl.UNSIGNED_SHORT, new Uint16Array(1))
PASS getError was expected value: INVALID_OPERATION : after evaluating: gl.copyTexSubImage2D(gl.TEXTURE_2D, 0, 0, 0, 0, 0, 1, 1)
PASS getError was expected value: INVALID_OPERATION : after evaluating: gl.generateMipmap(gl.TEXTURE_2D)
PASS gl.getParameter(gl.DEPTH_BITS) is >= 16
PASS gl.getParameter(gl.STENCIL_BITS) is 0
PASS gl.checkFramebufferStatus(gl.FRAMEBUFFER) is gl.FRAMEBUFFER_COMPLETE
PASS At 0,0, expected within [0.198000000000000,0.202000000000000], was 0.200000000000000
FAIL At 1,0, expected within [0.200000000000000,0.600000000000000], was 0.200000000000000 min
FAIL At 2,0, expected within [0.200000000000000,0.600000000000000], was 0.600000000000000 max
PASS At 3,0, expected within [0.598000000000000,0.602000000000000], was 0.600000000000000
FAIL At 0,1, expected within [0.200000000000000,0.400000000000000], was 0.200000000000000 min
FAIL At 1,1, expected within [0.200000000000000,0.800000000000000], was 0.200000000000000 min
PASS At 2,1, expected within [0.200000000000000,0.800000000000000], was 0.600000000000000
FAIL At 3,1, expected within [0.600000000000000,0.800000000000000], was 0.600000000000000 min
FAIL At 0,2, expected within [0.200000000000000,0.400000000000000], was 0.400000000000000 max
PASS At 1,2, expected within [0.200000000000000,0.800000000000000], was 0.400000000000000
FAIL At 2,2, expected within [0.200000000000000,0.800000000000000], was 0.800000000000000 max
FAIL At 3,2, expected within [0.600000000000000,0.800000000000000], was 0.800000000000000 max
PASS At 0,3, expected within [0.398000000000000,0.402000000000000], was 0.400000000000000
FAIL At 1,3, expected within [0.400000000000000,0.800000000000000], was 0.400000000000000 min
FAIL At 2,3, expected within [0.400000000000000,0.800000000000000], was 0.800000000000000 max
PASS At 3,3, expected within [0.798000000000000,0.802000000000000], was 0.800000000000000


Appears to be a test error:
Message says "within [0.2, 0.6]" which appears to indicate closed interval.
The test fails fails for 0.2 because it tests for open interval. It's unclear why wouldn't the endpoints be ok.

     const text = `At ${xx},${yy}, expected within [${eMin.toFixed(15)},${eMax.toFixed(15)}], was ${was.toFixed(15)}`
     if (was <= eMin || was >= eMax) {
         func = testFailed;
     }

[Radar WebKit Bug Importer]

<rdar://problem/83044143>