Open okias opened 10 months ago
Since the Affects: doesn't mention color_clears, not sure if a bug or feature.
One thing that we noted recently (although we didn't bisect to that point) is that several EGL (and some GLES tests) now try to use RB10A0 and RGB10A2 formats, and several tests were not handling that correctly. Specifically ...
src/broadcom/ci/broadcom-rpi4-fails.txt
... those tests that you list there were failing for our case due that. During the past weeks several developers have been providing patches related to those formats, like for example:
https://github.com/KhronosGroup/VK-GL-CTS/commit/d7905ab6f4e3de817e5269f23461b0be197fb16d
Most of them are already on the main branch or at least on an opengl-es branch. So there are a fix for those tests.
But about the tags. Those fixes are not on the 1.3.7.3 tag, and I think that they will arrive first to the opengl-es-cts branches, as they belong there. This is something that I asked @jasuarez some time about about the Mesa CI, that it would make more sense to test the vulkan tests with a vulkan tag, and the gles/egl tests with a opengl-es tag, but that would make things more complex on the CI.
In other words, the fixes for the patches are there, so it would make sense to close the issue, but on the other side, it is true that they are not yet on a cts tag, and it is not clear when they will be cherry picked.
@rg3igalia do you know who we should CC to clarify my previous doubt?
In other words, the fixes for the patches are there, so it would make sense to close the issue, but on the other side, it is true that they are not yet on a cts tag, and it is not clear when they will be cherry picked.
@rg3igalia do you know who we should CC to clarify my previous doubt?
Since I normally don't work on OpenGL(ES) tests, I'm unsure about the policy regarding those branches. However, I see that recent and old-ish fixes for opengl-es-cts-3.2.9, while not present in most Vulkan branches, are present in main. This means they will eventually land in a vulkan-cts branch, indirectly, when it's forked to create a new stable release.
Pinging @debater and/or @lordalcol for confirmation.
that it would make more sense to test the vulkan tests with a vulkan tag, and the gles/egl tests with a opengl-es tag, but that would make things more complex on the CI.
That's a bit unfortunate, but I think it would make sense.
You are correct. The fixes will be part of the next release vulkan-cts-1.3.8.0, currently planned for end of January. We are currently working on other fixes for OpenGL(ES) but we do not currently have a planned release for that.
You are correct. The fixes will be part of the next release vulkan-cts-1.3.8.0, currently planned for end of January. We are currently working on other fixes for OpenGL(ES) but we do not currently have a planned release for that.
Thanks for confirming. So how vk-gl-cts handle this kind of issues? Should it still be open until that tag is released (so we can confirm if all those patches fixes those tests), or it would be better to close the issue as there is available a fix, that we know that fix those tests on one of those platforms?
Let's keep it open until it's released at least as part of a Vulkan tag.
Problem:
Bisected to the 79b25659bcbced0cfc2c3fe318951c585f682abe
Since the
Affects:
doesn't mentioncolor_clears
, not sure if a bug or feature.