From: Andi Shyti <andi.shyti@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] runner: Produce json with results_version=10
Date: Wed, 5 Dec 2018 14:23:27 +0200 [thread overview]
Message-ID: <20181205122327.GA2397@intel.intel> (raw)
In-Reply-To: <20181205121224.13529-1-petri.latvala@intel.com>
Hi Petri,
On Wed, Dec 05, 2018 at 02:12:24PM +0200, Petri Latvala wrote:
> New piglit bumped its results_version to 10, making glxinfo and pals
> optional in practice, not just by accident. Unfortunately reading
> results with newer piglit attempts to convert the results to version
> 10, reading glxinfo and pals, and thus fails. In a hilarious summary:
> A commit to piglit making glxinfo optional makes it mandatory for us.
>
> Reported-by: Andi Shyti <andi.shyti@intel.com>
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Andi Shyti <andi.shyti@intel.com>
thank you! it works!
Tested-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-12-05 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 12:12 [igt-dev] [PATCH i-g-t 1/1] runner: Produce json with results_version=10 Petri Latvala
2018-12-05 12:23 ` Andi Shyti [this message]
2018-12-05 12:48 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/1] " Patchwork
2018-12-05 12:53 ` [igt-dev] [PATCH i-g-t v2 1/1] " Petri Latvala
2018-12-05 13:49 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/1] runner: Produce json with results_version=10 (rev2) Patchwork
2018-12-05 17:54 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-12-11 13:33 ` [igt-dev] [PATCH i-g-t 1/1] runner: Produce json with results_version=10 Arkadiusz Hiler
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=20181205122327.GA2397@intel.intel \
--to=andi.shyti@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox