After a long debugging process, we finally reached an acceptable solution to
the problem of running sequential subtests of IGT tests involving CRC capture
using the VKMS.
In March, I inspected the coverage of kms_cursor_crc on VKMS to develop my
GSoC project proposal.
Using piglit, I present the evolution of this coverage so far:
The first round just passed so fast, and what I did?
I spent the last week investigating the cause of two problems between VKMS and IGT that I have faced and reported in the development phase of my GSoC project proposal. One of the issues was a weird behavior, that I described as unstable, in the sequential execution of the kms\ _cursor\ _crc subtests or running the same subtest twice in a row: a subtest that passed in the first run failed in the second and returned to succeed in the third (and so on).
In this post, I describe the steps involved in the execution of a
kms_cursor_crc subtest. In my approach, I chose a subtest
(pipe-A-cursor-alpha-transparent) as a target and examined the code from the
beginning of the test (igt main) until reaching the target subtest and