All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Jeremy Huddleston <jeremyhu@freedesktop.org>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org
Subject: Re: libdrm fails 'make check' in tinderbox (was Re: [ANNOUNCE] libdrm 2.4.30)
Date: Sat, 28 Jan 2012 17:55:28 -0800	[thread overview]
Message-ID: <87ehuj5l2n.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <F0F4CF1A-05AA-4FD0-8344-0423DA0441F3@freedesktop.org>


[-- Attachment #1.1: Type: text/plain, Size: 680 bytes --]

On Sat, 28 Jan 2012 12:57:10 -0800, Jeremy Huddleston <jeremyhu@freedesktop.org> wrote:
> libdrm is still failing 'make check':
> 
> Linux/ppc   - http://tinderbox.x.org/builds/2012-01-28-0007/logs/libdrm/#check
> Linux/ppc64 - http://tinderbox.x.org/builds/2012-01-28-0013/logs/libdrm/#check
> 
> I bisected it to the commit below (which added the failing tests).
> Are these tests broken?  Can they please be disabled until they are
> working?

Not just the tests, but the whole intel DRM implementation should be
disabled on non-intel architectures.  I don't have any myself -- care to
try it on your own?  Or I could try to blindly write a patch for you to
try.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2012-01-29  1:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 16:54 libdrm 2.4.30 Eric Anholt
2012-01-07 19:22 ` [ANNOUNCE] " Jeremy Huddleston
2012-01-08  2:49   ` Eric Anholt
2012-01-08  8:48     ` Jeremy Huddleston
2012-01-09 16:15       ` Eric Anholt
2012-01-28 20:57   ` libdrm fails 'make check' in tinderbox (was Re: [ANNOUNCE] libdrm 2.4.30) Jeremy Huddleston
2012-01-29  1:55     ` Eric Anholt [this message]
2012-01-29  3:30       ` Jeremy Huddleston
2012-01-29 12:16         ` Daniel Vetter
2012-01-29 17:58           ` Jeremy Huddleston
2012-01-30 16:26         ` Eric Anholt
2012-01-30 23:25           ` [PATCH] Don't build Intel DRM if $CHOST is not i?86-* or x86_64-* Jeremy Huddleston
2012-01-31 16:59             ` Eric Anholt
2012-01-31 18:34               ` Jeremy Huddleston
2012-01-31 21:12                 ` Eric Anholt
2012-02-01 20:43             ` Julien Cristau
2012-02-01 21:01               ` Jeremy Huddleston
2012-02-01 21:56                 ` Julien Cristau
2012-02-01 21:59                   ` Jeremy Huddleston
2012-02-01 22:04                   ` Alan Coopersmith

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=87ehuj5l2n.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeremyhu@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 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.