All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: priyanka.dandamudi@intel.com
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BUILD: failure for HAX add description to gem_close_race (rev3)
Date: Wed, 15 Jun 2022 08:42:18 -0000	[thread overview]
Message-ID: <165528253877.14602.15335286213227669149@emeril.freedesktop.org> (raw)
In-Reply-To: <20220615055147.1175944-1-priyanka.dandamudi@intel.com>

== Series Details ==

Series: HAX add description to gem_close_race (rev3)
URL   : https://patchwork.freedesktop.org/series/104408/
State : failure

== Summary ==

Applying: i915/gem_close_race: added description for test case
Applying: HAX: don't do full run
Using index info to reconstruct a base tree...
M	tests/intel-ci/fast-feedback.testlist
Falling back to patching base and 3-way merge...
Auto-merging tests/intel-ci/fast-feedback.testlist
CONFLICT (content): Merge conflict in tests/intel-ci/fast-feedback.testlist
Patch failed at 0002 HAX: don't do full run
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".


      parent reply	other threads:[~2022-06-15  8:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  5:51 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_close_race priyanka.dandamudi
2022-06-15  5:51 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_close_race: added description for test case priyanka.dandamudi
2022-06-15 15:35   ` Kamil Konieczny
2022-06-15  5:51 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run priyanka.dandamudi
2022-06-15  8:42 ` Patchwork [this message]

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=165528253877.14602.15335286213227669149@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=priyanka.dandamudi@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.