Also a couple runs earlier in gem_eio/in-flight-suspend. The check says that the fence completed normally and was not detected as causing a hang (corresponds with the test completing far too quickly as well). So the spinner didn't spin? Fishy.

Also,
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4151/shard-hsw1/igt@gem_eio@in-flight.html

(gem_eio:1741) CRITICAL: Test assertion failure function test_inflight, file gem_eio.c:222:
(gem_eio:1741) CRITICAL: Failed assertion: sync_fence_status(fence[n]) == -5
(gem_eio:1741) CRITICAL: error: 1 != -5
Subtest in-flight failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3639/shard-hsw7/igt@gem_eio@in-flight-suspend.html

(gem_eio:1876) CRITICAL: Test assertion failure function test_inflight_suspend, file gem_eio.c:268:
(gem_eio:1876) CRITICAL: Failed assertion: sync_fence_status(fence[n]) == -5
(gem_eio:1876) CRITICAL: error: 1 != -5
Subtest in-flight-suspend failed.

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4148/shard-hsw6/igt@gem_eio@in-flight-external.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4153/shard-hsw3/igt@gem_eio@in-flight-suspend.html

Having no luck yet catching this for myself. Nothing obviously looks wrong, but the test is complaining that the wedging didn't occur. The dmesg concurs in that there doesn't appear to be a reset in the middle of the test...

Swapped out the quick hang injection for a slow spinner, seems to have fixed this on hsw, but found a whole new issue on execlists. (Seems to be that the CS interrupt is firing and kicking off the execlists as we are trying to prune it. tasklet_kill() where are you?)

commit 9ba3717a86553e15aa6e4aec8a77c2e3460fd4d3
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Feb 6 22:55:33 2018 +0000

    igt/gem_eio: Use slow spinners to inject hangs
    
    One weird issue we see in bug 104676 is that the hangs are too fast on
    HSW! So force the use of the slow spinners that do not try to trigger
    a hang by injecting random bytes into the batch.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104676
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Closing this bug report for cibuglog, Marta will you file a new one for the incompletes?

(In reply to Chris Wilson from comment #6)
> Swapped out the quick hang injection for a slow spinner, seems to have fixed
> this on hsw, but found a whole new issue on execlists. (Seems to be that the
> CS interrupt is firing and kicking off the execlists as we are trying to
> prune it. tasklet_kill() where are you?)
> 
> commit 9ba3717a86553e15aa6e4aec8a77c2e3460fd4d3
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Tue Feb 6 22:55:33 2018 +0000
> 
>     igt/gem_eio: Use slow spinners to inject hangs
>     
>     One weird issue we see in bug 104676 is that the hangs are too fast on
>     HSW! So force the use of the slow spinners that do not try to trigger
>     a hang by injecting random bytes into the batch.
>     
>     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104676
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> 
> Closing this bug report for cibuglog, Marta will you file a new one for the
> incompletes?

OK, I will monitor this over the weekend. As far as I can see there are no incompletes on igt@gem_eio@in-flight* on HSW.

The GLK, KBL, APL igt@gem_eio@in-flight* incompletes are on bug 104945. However, I am wondering if KBL is hitting a new issue now.

The fix was already in CI_DRM_3815, all green on HSW, but is maybe the recent increase in incompletes on APL and KBL related? bug 104945