The execution time of the igt@gem_exec_suspend@basic-s3 test on fi-ctg-l9400 went from 29.68s to 93.66s between CI_DRM_2605 and CI_DRM_2606. This is a separate problem from https://bugs.freedesktop.org/show_bug.cgi?id=101074 because it appeared a before.
Because of this problem, the IGT runs now randomly time out.
Here is the list of commits that were made between them: https://intel-gfx-ci.01.org/CI/CI_DRM_2606/commits_short.log
Question: if this is a BAT bug should not be Highest? or because is random is considered only Medium?
Good observation Ricardo, I just forgot to make the change or to press "Save Changes"!
Investigated this with a ctg-l9400 that was supposed to be an identical machine. Couldn't reproduce the issue at all.
With further investigation it was revealed that the suspend on the farm's ctg machine did not in fact take more time, but the machine itself had a clock skew during suspend. The CI timeouts are unrelated to the reported runtime changes.
Something happened in the kernel between CI_DRM_2605 and CI_DRM_2606 that caused the reported times to increase, but as even the reported time before was incorrect, the ctg in the CI farm has now been replaced with another one to unblock CI usage.
Marking this bug as NEEDINFO for bisecting the time increase between 2605 and 2606.
*** Bug 101074 has been marked as a duplicate of this bug. ***
Good afternoon, I noticed there is no update on this case since May. Is there any advance with this case? Thank you.
(In reply to Petri Latvala from comment #3)
> ...Something happened in the kernel between CI_DRM_2605 and CI_DRM_2606 that
> caused the reported times to increase, but as even the reported time before
> was incorrect, the ctg in the CI farm has now been replaced with another one
> to unblock CI usage.
> Marking this bug as NEEDINFO for bisecting the time increase between 2605
> and 2606.
Marking wontfix, the original issue is gone and bisecting the change in reported times without the affected hardware.