Hi everyone,
As part of our stable CI process at Intel, we lock the version of piglit, deqp,
and the Khronos CTSes at branchpoint. If you nominate a patch for stable and
there is a corresponding change to one of those test suites, can you please
mention it in the commit message? This is a huge
Michel Dänzer writes:
> On 2019-11-15 4:02 p.m., Mark Janes wrote:
>> Michel Dänzer writes:
>>
>>> Now that the GitLab CI pipeline tests a snapshot of piglit with llvmpipe
>>> (https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2468), the
>>> question has come up how to deal with
On 2019-11-15 4:02 p.m., Mark Janes wrote:
> Michel Dänzer writes:
>
>> Now that the GitLab CI pipeline tests a snapshot of piglit with llvmpipe
>> (https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2468), the
>> question has come up how to deal with inter-dependent Mesa/piglit
>> changes
Michel Dänzer writes:
> Now that the GitLab CI pipeline tests a snapshot of piglit with llvmpipe
> (https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2468), the
> question has come up how to deal with inter-dependent Mesa/piglit
> changes (where merging only one or the other causes some
Now that the GitLab CI pipeline tests a snapshot of piglit with llvmpipe
(https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2468), the
question has come up how to deal with inter-dependent Mesa/piglit
changes (where merging only one or the other causes some piglit
regressions).
First of
