Test makes assumptions about expiry of current texture

[sagudev]

Here

cts/src/webgpu/web_platform/canvas/getCurrentTexture.spec.ts

Line 165 in f6b22c0

g.test('multiple_frames')

we do getCurrentTexture in:

JS
rAF
rAF
rAF
rAF
rAF

Per spec it's clear that each rAF should have different texture then previous, but same does not hold true for first pair (JS rAF case), although test expects it to.

Let's say the next task after JS code, that created texture (getCurrentTexture) is HTML Update The Rendering. We will also assume we did not implement any expiry task (we only expire on update the rendering).
In update the rendering:

• There is microtask checkpoint in step 11, but that does not bother us (texture is still valid)
• rAF is get run in step 14 (texture is still valid)
• step 22 (For each doc of docs, update the rendering or user interface of doc) we run WebGPU Update The Rendering which in turn runs expire texture.

[sagudev]

Related, in this test

cts/src/webgpu/web_platform/canvas/getCurrentTexture.spec.ts

Line 327 in f6b22c0

g.test('expiry')

we expect microtask checkpoint between rAF (frame is not a (micro)task) and WebGPU Update The Rendering, but I did not find it in spec.