KhronosGroup / KhronosGroup/WebGL

[webGL2.0] [firefox] qualification_order failed in AMD/NV graphics for OpenGL rendering

Open
#2,035 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
2.9k
Forks
704
Avg merge
2d 9h
Merged PRs (30d)
4

Description

OS: w10
Graphics: AMD asic / NV asic
browser: firefox
config: enable webGL2.0, enable OpenGL rendering

steps:

  1. run firefox, enable webGL2.0
  2. visit "https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html?version=2.0.0"
  3. find test "all/deqp/data/gles3/Shaders/qualification_order" and run

expected: test pass
actually: failed: qualification_order.variables.valid.invariant_interp_storage_precision: expected shaders to compile and link properly, but failed to link.

Modify webGL/sdk/tests/deqp/modules/shared/glsShaderLibraryCase to run only the first test case:

glsShaderLibraryCase.runTestCases = function() {
var state = tcuTestCase.runner;
if (state.next()) {
try {
glsShaderLibraryCase.init();
glsShaderLibraryCase.execute();
} catch (err) {
bufferedLogToConsole(err);
}
// tcuTestCase.runner.runCallback(glsShaderLibraryCase.runTestCases); //comment out this line
} else
tcuTestCase.runner.terminate();

};

root cause:
app doesn't call glLinkProgram, glUseProgram in test

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in webGL/sdk/tests/deqp/modules/shared/glsShaderLibraryCase at runTestCases, then reproduce the qualification_order failure using the linked WebGL 2.0 conformance test in Firefox with OpenGL rendering enabled. Check the reported shader-linking path and the existing test-case runner behavior; done means the qualification_order test runs with the intended cases and passes without the reported link failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.