From: Tomi Sarvela <tomi.p.sarvela@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>,
Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: ✓ Fi.CI.BAT: success for series starting with [CI,1/9] drm/i915: Extract intel_get_cagf
Date: Wed, 22 Nov 2017 13:34:22 +0200 [thread overview]
Message-ID: <d9483af2-0254-5ddf-2a3a-b7a1eed5335f@intel.com> (raw)
In-Reply-To: <fbd91a79-9542-fda7-5734-3084cbc6c71a@linux.intel.com>
On 22/11/17 13:31, Tvrtko Ursulin wrote:
>
> On 21/11/2017 18:40, Patchwork wrote:
>> == Series Details ==
>>
>> Series: series starting with [CI,1/9] drm/i915: Extract intel_get_cagf
>> URL : https://patchwork.freedesktop.org/series/34186/
>> State : success
>>
[...]
> Pushed, but only then noticed this failed to collect log from skl-6700k.
> How to figure out what happened there - Tomi would you be able to have a
> look?
This is something I like to call 'Jenkins slave connector issue' (link
wrong, I'll fix): Jenkins noticed connection issue only when it tried to
run the test on the host.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7225/fi-skl-6700k/run0.log
Tomi
--
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-22 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 18:18 [CI 1/9] drm/i915: Extract intel_get_cagf Tvrtko Ursulin
2017-11-21 18:18 ` [CI 2/9] drm/i915/pmu: Expose a PMU interface for perf queries Tvrtko Ursulin
2017-12-01 1:01 ` Rodrigo Vivi
2017-12-01 9:51 ` Tvrtko Ursulin
2017-11-21 18:18 ` [CI 3/9] drm/i915/pmu: Suspend sampling when GPU is idle Tvrtko Ursulin
2017-11-21 18:18 ` [CI 4/9] drm/i915: Wrap context schedule notification Tvrtko Ursulin
2017-11-21 18:18 ` [CI 5/9] drm/i915: Engine busy time tracking Tvrtko Ursulin
2017-11-21 18:18 ` [CI 6/9] drm/i915/pmu: Wire up engine busy stats to PMU Tvrtko Ursulin
2017-11-21 18:18 ` [CI 7/9] drm/i915/pmu: Add interrupt count metric Tvrtko Ursulin
2017-11-21 18:18 ` [CI 8/9] drm/i915: Convert intel_rc6_residency_us to ns Tvrtko Ursulin
2017-11-21 18:18 ` [CI 9/9] drm/i915/pmu: Add RC6 residency metrics Tvrtko Ursulin
2017-11-21 18:40 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/9] drm/i915: Extract intel_get_cagf Patchwork
2017-11-22 11:31 ` Tvrtko Ursulin
2017-11-22 11:34 ` Tomi Sarvela [this message]
2017-11-21 19:37 ` ✗ Fi.CI.IGT: warning " 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=d9483af2-0254-5ddf-2a3a-b7a1eed5335f@intel.com \
--to=tomi.p.sarvela@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=tursulin@ursulin.net \
--cc=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.