[Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-intel tree (rev2)

2018-07-12 Thread Patchwork
== Series Details ==

Series: linux-next: build failure after merge of the drm-intel tree (rev2)
URL   : https://patchwork.freedesktop.org/series/42839/
State : failure

== Summary ==

Applying: linux-next: build failure after merge of the drm-intel tree
Using index info to reconstruct a base tree...
M   drivers/gpu/drm/i915/gvt/kvmgt.c
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-intel tree

2018-05-08 Thread Arkadiusz Hiler
On Tue, May 08, 2018 at 11:40:52AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 08 May 2018 01:36:25 - Patchwork 
>  wrote:
> >
> > == Series Details ==
> > 
> > Series: linux-next: build failure after merge of the drm-intel tree
> > URL   : https://patchwork.freedesktop.org/series/42839/
> > State : failure
> 
> Blah, blah :-)
> 
> Can someone please arrange for my linux-next merge fix patches to not
> be fed into your patchwork/ci as they will never work out side
> linux-next ...

Hey,

Sorry for clotting your inbox with those mails but I have to ask how
annoying is getting those results?

If it's bearable I would prefer to not introduce special cases basing on
contents of the mbox and/or its author. As of our CI we are not really
that much concerned with wasting time on something that wasn't meant to
be tested - such patches are extremely rare.


If this is necessary - do you have any suggestion how it should be done?
Filtering by "linux-next" in the Subject? By your name? Email address?

Is it the case that linux-next can appear only in untestable patches?
Is silently ignoring such a patch by the CI really okay?

Maybe we should introduce [NOCI] subject tag?
Would you remember to include it?


As of instant solution - you can include "X-Patchwork-Hint: comment" in
the headers, so patchwork won't recognize your email as a patch.

-- 
Cheers,
Arek
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-intel tree

2018-05-08 Thread Saarinen, Jani
HI, 
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
> Stephen Rothwell
> Sent: tiistai 8. toukokuuta 2018 4.41
> To: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure 
> after
> merge of the drm-intel tree
> 
> Hi all,
> 
> On Tue, 08 May 2018 01:36:25 - Patchwork
> <patchw...@emeril.freedesktop.org> wrote:
> >
> > == Series Details ==
> >
> > Series: linux-next: build failure after merge of the drm-intel tree
> > URL   : https://patchwork.freedesktop.org/series/42839/
> > State : failure
> 
> Blah, blah :-)
> 
> Can someone please arrange for my linux-next merge fix patches to not be fed
> into your patchwork/ci as they will never work out side linux-next ...
Tomi, Arek? What can be done if any? 
> 
> --
> Cheers,
> Stephen Rothwell
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-intel tree

2018-05-07 Thread Stephen Rothwell
Hi all,

On Tue, 08 May 2018 01:36:25 - Patchwork  
wrote:
>
> == Series Details ==
> 
> Series: linux-next: build failure after merge of the drm-intel tree
> URL   : https://patchwork.freedesktop.org/series/42839/
> State : failure

Blah, blah :-)

Can someone please arrange for my linux-next merge fix patches to not
be fed into your patchwork/ci as they will never work out side
linux-next ...

-- 
Cheers,
Stephen Rothwell


pgppUO97yreq8.pgp
Description: OpenPGP digital signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-intel tree

2018-05-07 Thread Patchwork
== Series Details ==

Series: linux-next: build failure after merge of the drm-intel tree
URL   : https://patchwork.freedesktop.org/series/42839/
State : failure

== Summary ==

= CI Bug Log - changes from CI_DRM_4152 -> Patchwork_8931 =

== Summary - FAILURE ==

  Serious unknown changes coming with Patchwork_8931 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_8931, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  External URL: 
https://patchwork.freedesktop.org/api/1.0/series/42839/revisions/1/mbox/

== Possible new issues ==

  Here are the unknown changes that may have been introduced in Patchwork_8931:

  === IGT changes ===

 Possible regressions 

igt@kms_flip@basic-flip-vs-wf_vblank:
  fi-hsw-4200u:   PASS -> FAIL


== Known issues ==

  Here are the changes found in Patchwork_8931 that come from known issues:

  === IGT changes ===

 Issues hit 

igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
  fi-cnl-psr: PASS -> DMESG-WARN (fdo#104951)


 Possible fixes 

igt@kms_flip@basic-flip-vs-wf_vblank:
  fi-skl-6770hq:  FAIL (fdo#103928, fdo#100368) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#103928 https://bugs.freedesktop.org/show_bug.cgi?id=103928
  fdo#104951 https://bugs.freedesktop.org/show_bug.cgi?id=104951


== Participating hosts (41 -> 37) ==

  Missing(4): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-skl-6700hq 


== Build changes ==

* Linux: CI_DRM_4152 -> Patchwork_8931

  CI_DRM_4152: 06e15c0f055b8b8e326bb65fa83f69b1b7391e51 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4464: 1bb318b32db003a377da14715c7b80675a712b6b @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_8931: 3c1454cc91d53c9b6782b9fd72071fcf24e6fe3f @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4464: 33e58d5583eb7ed3966a1b905f875a1dfa959f6b @ 
git://anongit.freedesktop.org/piglit


== Linux commits ==

3c1454cc91d5 linux-next: build failure after merge of the drm-intel tree

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8931/issues.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx