From: Patchwork <patchwork@emeril.freedesktop.org>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/8] i915/gem_eio: Check that context create fails when wedged (rev2)
Date: Tue, 19 Feb 2019 17:36:40 -0000 [thread overview]
Message-ID: <20190219173640.5014.83650@emeril.freedesktop.org> (raw)
In-Reply-To: <20190217143556.9482-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [i-g-t,1/8] i915/gem_eio: Check that context create fails when wedged (rev2)
URL : https://patchwork.freedesktop.org/series/56807/
State : failure
== Summary ==
Applying: i915/gem_eio: Check that context create fails when wedged
Applying: i915/gem_eio: Check we only ban the context
Applying: lib: Restore the i915.reset modparam before cleaning up
Applying: i915/gem_create: Verify that all new objects are clear
Using index info to reconstruct a base tree...
M tests/i915/gem_create.c
Falling back to patching base and 3-way merge...
Auto-merging tests/i915/gem_create.c
CONFLICT (content): Merge conflict in tests/i915/gem_create.c
Patch failed at 0004 i915/gem_create: Verify that all new objects are clear
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".
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-02-19 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 14:35 [Intel-gfx] [PATCH i-g-t 1/8] i915/gem_eio: Check that context create fails when wedged Chris Wilson
2019-02-17 14:35 ` [igt-dev] [PATCH i-g-t 2/8] i915/gem_eio: Check we only ban the context Chris Wilson
2019-02-19 16:53 ` Antonio Argenziano
2019-02-19 17:05 ` Chris Wilson
2019-02-19 17:11 ` [Intel-gfx] [PATCH i-g-t] " Chris Wilson
2019-02-19 17:27 ` [igt-dev] " Antonio Argenziano
2019-02-17 14:35 ` [Intel-gfx] [PATCH i-g-t 3/8] lib: Restore the i915.reset modparam before cleaning up Chris Wilson
2019-02-19 18:22 ` [igt-dev] " Antonio Argenziano
2019-02-19 21:03 ` Chris Wilson
2019-02-17 14:35 ` [igt-dev] [PATCH i-g-t 4/8] i915/gem_create: Verify that all new objects are clear Chris Wilson
2019-02-17 14:35 ` [igt-dev] [PATCH i-g-t 5/8] i915/gem_exec_big: Add a single shot test Chris Wilson
2019-02-17 14:35 ` [Intel-gfx] [PATCH i-g-t 6/8] i915/gem_exec_parse: Switch to a fixed timeout for basic-allocations Chris Wilson
2019-03-06 11:50 ` [igt-dev] " Tvrtko Ursulin
2019-02-17 14:35 ` [igt-dev] [PATCH i-g-t 7/8] kms_fence_pin_leak: Ask for the GPU before use Chris Wilson
2019-02-17 14:35 ` [Intel-gfx] [PATCH i-g-t 8/8] kms_fence_pin_leak: Move beneath i915/ Chris Wilson
2019-02-18 13:37 ` [igt-dev] " Arkadiusz Hiler
2019-02-18 13:42 ` Chris Wilson
2019-02-18 13:43 ` Chris Wilson
2019-02-18 14:01 ` Arkadiusz Hiler
2019-02-18 14:08 ` Chris Wilson
2019-02-18 14:19 ` Arkadiusz Hiler
2019-02-17 15:22 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/8] i915/gem_eio: Check that context create fails when wedged Patchwork
2019-02-17 18:24 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-02-19 16:53 ` [igt-dev] [Intel-gfx] [PATCH i-g-t 1/8] " Antonio Argenziano
2019-02-19 17:36 ` 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=20190219173640.5014.83650@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
/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