From: Matthew Auld <matthew.william.auld@gmail.com>
To: George Spelvin <lkml@sdf.org>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drivers/gpu/drm/i915/selftests/i915_buddy.c: Fix bug
Date: Fri, 27 Mar 2020 10:45:20 +0000 [thread overview]
Message-ID: <CAM0jSHOk45jFh5p_54Yx8UQA0jmpR8=oCLbXjCScn3pe02Ck+Q@mail.gmail.com> (raw)
In-Reply-To: <20200326202121.GC15115@SDF.ORG>
On Thu, 26 Mar 2020 at 20:21, George Spelvin <lkml@sdf.org> wrote:
>
> On Thu, Mar 26, 2020 at 05:04:43PM +0000, Matthew Auld wrote:
> > Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
> Thank you! I got some incomprehensible error emails (reproduced at
> https://patchwork.freedesktop.org/series/75090/) from the patchwork
> daemon, complaining about additional test failures. Obviously, I care,
> but I can't tell if this is a genuine error, or just a flaky test being
> sensitive to the exact random number generation algorithm.
>
> If you understand these messages, do they look like I broke something?
No, doesn't seem to be related to your change.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17090/shards-all.html?testfilter=buddy
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-27 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 19:24 [Intel-gfx] [PATCH] drivers/gpu/drm/i915/selftests/i915_buddy.c: Fix bug George Spelvin
2020-03-25 23:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-03-25 23:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-26 3:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-03-26 17:04 ` [Intel-gfx] [PATCH] " Matthew Auld
2020-03-26 20:21 ` George Spelvin
2020-03-27 10:45 ` Matthew Auld [this message]
2020-08-06 16:02 ` Chris Wilson
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='CAM0jSHOk45jFh5p_54Yx8UQA0jmpR8=oCLbXjCScn3pe02Ck+Q@mail.gmail.com' \
--to=matthew.william.auld@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lkml@sdf.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 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.