From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for drm: connector firmware nodes
Date: Wed, 27 Mar 2019 17:38:27 +0200 [thread overview]
Message-ID: <20190327153827.GA1027@kuha.fi.intel.com> (raw)
In-Reply-To: <43D4F724E12AB6478FC1572B3FBE89D0765D35F1@IRSMSX106.ger.corp.intel.com>
Hi Jani,
On Tue, Mar 26, 2019 at 03:16:29PM +0000, Saarinen, Jani wrote:
> > -----Original Message-----
> > From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of Heikki
> > Krogerus
> > Sent: tiistai 26. maaliskuuta 2019 10.32
> > To: intel-gfx@lists.freedesktop.org
> > Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm: connector firmware nodes
> >
> > On Mon, Mar 25, 2019 at 08:57:44PM -0000, Patchwork wrote:
> > > == Series Details ==
> > >
> > > Series: drm: connector firmware nodes
> > > URL : https://patchwork.freedesktop.org/series/58531/
> > > State : failure
> > >
> > > == Summary ==
> > >
> > > CI Bug Log - changes from CI_DRM_5810_full -> Patchwork_12592_full
> > > ====================================================
> > >
> > > Summary
> > > -------
> > >
> > > **FAILURE**
> > >
> > > Serious unknown changes coming with Patchwork_12592_full absolutely need to
> > be
> > > verified manually.
> > >
> > > If you think the reported changes have nothing to do with the changes
> > > introduced in Patchwork_12592_full, please notify your bug team to allow them
> > > to document this new failure mode, which will reduce false positives in CI.
> > >
> > >
> > >
> > > Possible new issues
> > > -------------------
> > >
> > > Here are the unknown changes that may have been introduced in
> > Patchwork_12592_full:
> > >
> > > ### IGT changes ###
> > >
> > > #### Possible regressions ####
> > >
> > > * igt@perf_pmu@idle-no-semaphores-bcs0:
> > > - shard-iclb: PASS -> INCOMPLETE
> >
> >
> > I have not idea what this is about? Is there something I need to do?
> Do you see from logs if relevant to your patche(s) ?
Sorry, but I can't really say, as I don't know how to interpret the
logs. I don't understand what that test is doing.
I'm assuming this log shows the failure:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12592/shard-iclb8/run7.log
The failure happens when running test (I'm guessing):
"[30/82] (859s left) gem_tiled_swapping (non-threaded)"
In the log there is a line that says:
"FATAL: Unable to delete script file /tmp/jenkins7657231043286309557.sh"
That certainly does not sound like anything that these patches would
affect, but since I really have no idea what the test is doing, I
can't really be sure.
thanks,
--
heikki
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-27 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 13:16 [PATCH 0/2] drm: connector firmware nodes Heikki Krogerus
2019-03-25 13:16 ` [PATCH 1/2] drm: Add fwnode member to the struct drm_connector Heikki Krogerus
2019-03-25 13:16 ` [PATCH 2/2] drm/i915: Associate ACPI connector nodes with connector entries Heikki Krogerus
2019-03-25 13:47 ` ✓ Fi.CI.BAT: success for drm: connector firmware nodes Patchwork
2019-03-25 20:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-26 8:32 ` Heikki Krogerus
2019-03-26 15:16 ` Saarinen, Jani
2019-03-27 15:38 ` Heikki Krogerus [this message]
2019-03-27 15:59 ` Tvrtko Ursulin
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=20190327153827.GA1027@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@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.