From: Patchwork <patchwork@emeril.freedesktop.org>
To: Petri Latvala <petri.latvala@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for Run gem_eio@in-flight-suspend on farm1
Date: Thu, 19 Oct 2017 13:41:31 -0000 [thread overview]
Message-ID: <20171019134131.20930.27390@emeril.freedesktop.org> (raw)
In-Reply-To: <1508418656-2006-1-git-send-email-petri.latvala@intel.com>
== Series Details ==
Series: Run gem_eio@in-flight-suspend on farm1
URL : https://patchwork.freedesktop.org/series/32296/
State : success
== Summary ==
IGT patchset tested on top of latest successful build
abc08cba366a64a07f7f4deb167ae7d6ae059958 lib: Free all internal buffers before measuring available memory
with latest DRM-Tip kernel build CI_DRM_3265
93f001963c99 drm-tip: 2017y-10m-19d-10h-52m-17s UTC integration manifest
No testlist changes.
Test gem_eio:
Subgroup in-flight-suspend:
notrun -> INCOMPLETE (fi-snb-2600)
fi-bdw-5557u total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:21s
fi-bdw-gvtdvm total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:23s
fi-blb-e6850 total:1 pass:0 dwarn:1 dfail:0 fail:0 skip:0 time:15s
fi-bsw-n3050 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:22s
fi-bwr-2160 total:1 pass:0 dwarn:1 dfail:0 fail:0 skip:0 time:15s
fi-bxt-dsi total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:21s
fi-bxt-j4205 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:22s
fi-byt-j1900 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:16s
fi-byt-n2820 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:24s
fi-cfl-s total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:21s
fi-elk-e7500 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:15s
fi-glk-1 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:21s
fi-hsw-4770 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:14s
fi-hsw-4770r total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:14s
fi-ilk-650 total:1 pass:0 dwarn:1 dfail:0 fail:0 skip:0 time:18s
fi-ivb-3520m total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:23s
fi-ivb-3770 total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:14s
fi-kbl-7500u total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:22s
fi-kbl-7560u total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:23s
fi-kbl-7567u total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:20s
fi-kbl-r total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:24s
fi-pnv-d510 total:1 pass:0 dwarn:1 dfail:0 fail:0 skip:0 time:15s
fi-skl-6260u total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:21s
fi-skl-6700hq total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:24s
fi-skl-6700k total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:29s
fi-skl-6770hq total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:22s
fi-skl-gvtdvm total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:20s
fi-snb-2520m total:1 pass:1 dwarn:0 dfail:0 fail:0 skip:0 time:20s
fi-snb-2600 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_388/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-19 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 13:10 [CI PATCH i-g-t] Run gem_eio@in-flight-suspend on farm1 Petri Latvala
2017-10-19 13:41 ` Patchwork [this message]
2017-10-19 14:23 ` ✗ Fi.CI.IGT: warning for " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171019134131.20930.27390@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox