Cubemap test failures in Chrome on Linux
Open
Nobody has claimed this yet.
test failure
- Dominant language
- JavaScript
- Stars
- 15.8k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
I'm seeing two test failures in the 1.77 release process consistently in Chrome 87.0.4280.88 for Linux, on both Intel and Nvidia:
Renderer/CubeMap creates a cube map with floating-point textures and linear filtering
Expected context to render 0,255,128,255, but rendered: 0,255,0,255
Renderer/CubeMap creates a cube map with half floating-point textures and linear filtering
Expected context to render 102,102,102,255, but rendered: 153,102,51,255
WebGL reports to follow in comments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the two named Renderer/CubeMap tests in Chrome on Linux and review the WebGL reports in the issue comments. Compare the floating-point and half floating-point texture results with the expected values. Done means the two reported test failures are resolved and the expected render output is restored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100