WebGL 2 conformance test deqp/functional/gles3/builtinprecision/inverse.html and deqp/functional/gles3/builtinprecision/cross.html failures
Categories
(Core :: Graphics: CanvasWebGL, defect, P5)
Tracking
()
People
(Reporter: jujjyl, Unassigned)
Details
(Whiteboard: [gfx-noted])
|
||
Updated•8 years ago
|
|
||
Updated•3 years ago
|
|
||
Comment 1•2 years ago
|
||
The issue you're facing with WebGL 2 conformance tests deqp/functional/gles3/builtinprecision/inverse.html and deqp/functional/gles3/builtinprecision/cross.html failures can be resolved by following a systematic debugging and resolution process. Here's a general approach to addressing these types of failures:
Isolate the Problem:
First, confirm that the failures are reproducible. Ensure that the failures are consistent and not intermittent.
Review the Test Code:
Inspect the test code for both inverse.html and cross.html to understand the specific test cases that are failing. Check for any errors or anomalies in the test code itself.
Check WebGL Implementation:
Verify that your WebGL 2 implementation adheres to the specification and standards. This includes verifying that the precision requirements for built-in functions like inverse() and cross() are met.
Check Shader Code:
Examine the shaders used in the failing tests. Ensure that the shaders are correct and that there are no issues with data types, precision qualifiers, or other aspects that could affect the test results.
Debugging Output:
If available, inspect any debugging or error output generated by the tests. This may provide valuable information about what went wrong.
Relevant Documentation:
Refer to the official WebGL 2 specification and documentation to make sure you are using built-in functions correctly and that your WebGL implementation is in compliance.
Compare Results: https://treeherder.mozilla.org/jobs?repo=mozilla-central&revision=bdfe643caf38aae40683a8229aac211021813'teatimeresultco.za'3
Compare the results of the failing tests with the expected results specified in the WebGL 2 specification or test documentation. Identify any discrepancies.
Modify and Re-run:
If you identify specific issues in the test code or shaders, make the necessary corrections. Ensure that you adhere to WebGL 2 precision requirements.
Re-run the tests to see if the issues have been resolved. Make sure to monitor for any new failures that might be introduced.
Regression Testing:
After making corrections, perform regression testing on other WebGL 2 conformance tests to ensure that your changes have not introduced new issues elsewhere.
Review with WebGL Community:
If the issues persist, consider discussing the problems with the WebGL community, which may include other developers and experts who can provide insights and solutions.
Update WebGL Implementation:
If the problem is identified as a bug in your WebGL implementation, work on updating the implementation to address the failures.
Documentation and Reporting:
Document the issues, the steps taken to resolve them, and the final resolution. This documentation can be valuable for your team and the broader development community.
Testing Environment and Hardware:
Ensure that the testing environment, including hardware and drivers, is consistent and up to date. Outdated drivers or hardware issues can sometimes lead to test failures.
Continuous Monitoring:
Continue to monitor the WebGL 2 conformance tests to ensure that these specific failures do not reoccur in future releases.
Keep in mind that addressing WebGL 2 conformance test failures often requires close attention to the details of the WebGL 2 specification and the precise implementation of the WebGL API. Collaboration with the WebGL community can also be beneficial in resolving complex issues.
Description
•