[Bug 110581] [CI][SHARDS] shards have a 10 minutes timeout which kills them early!

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 2 09:40:41 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=110581

--- Comment #6 from CI Bug Log <cibuglog at gmail.com> ---
A CI Bug Log filter associated to this bug has been updated:

{- SKL all tests - incomplete -}
{+ all machines: all tests - incomplete +}

New failures caught by the filter:

  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cml-u2/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-mmap-wc.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-gdg-551/igt@gem_persistent_relocs@forked-thrashing.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-hsw-peppy/igt@gem_exec_whisper@normal.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-hsw-peppy/igt@kms_flip@flip-vs-suspend.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-kbl-7500u/igt@kms_cursor_crc@cursor-256x85-offscreen.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-kbl-x1275/igt@kms_flip@flip-vs-suspend.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-bdw-5557u/igt@kms_cursor_legacy@pipe-a-single-bo.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cfl-8109u/igt@kms_flip@2x-wf_vblank-ts-check.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cfl-8109u/igt@kms_flip_tiling@flip-changes-tiling-y.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cfl-8109u/igt@kms_flip@flip-vs-panning-vs-hang-interruptible.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cfl-8109u/igt@kms_busy@extended-modeset-hang-oldfb-with-reset-render-c.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u/igt@kms_universal_plane@cursor-fb-leak-pipe-b.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u/igt@prime_busy@wait-after-vebox.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u/igt@kms_atomic_transition@1x-modeset-transitions-fencing.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u2/igt@gem_exec_blt@cold-min.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u2/igt@prime_busy@wait-after-vebox.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u2/igt@drm_import_export@import-close-race-flink.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-cml-u2/igt@gem_exec_schedule@preempt-queue-contexts-render.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-hsw-peppy/igt@kms_cursor_crc@cursor-256x256-offscreen.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-hsw-peppy/igt@gem_softpin@noreloc-s3.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-ilk-650/igt@kms_cursor_legacy@pipe-a-single-bo.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-kbl-7500u/igt@kms_vblank@pipe-b-query-busy-hang.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-kbl-x1275/igt@kms_cursor_legacy@pipe-a-single-bo.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-bsw-kefka/igt@gem_ringfill@basic-default-hang.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cfl-8109u/igt@kms_cursor_crc@cursor-128x42-offscreen.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cfl-8109u/igt@kms_flip@flip-vs-suspend.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cfl-8109u/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cml-u/igt@kms_flip@wf_vblank-ts-check.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cml-u/igt@gem_pipe_control_store_loop@reused-buffer.html
  *
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-cml-u2/igt@kms_flip@wf_vblank-ts-check.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190502/a147234d/attachment-0001.html>


More information about the intel-gfx-bugs mailing list