From: Petri Latvala <petri.latvala@intel.com>
To: Ryszard Knop <ryszard.knop@intel.com>
Cc: Development mailing list for IGT GPU Tools
<igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 0/3] Use Jansson instead of json-c in igt_runner
Date: Thu, 11 Aug 2022 12:14:54 +0300 [thread overview]
Message-ID: <YvTIjlCyxzJft4PF@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20220810135530.992455-1-ryszard.knop@intel.com>
On Wed, Aug 10, 2022 at 03:55:27PM +0200, Ryszard Knop wrote:
> The json-c library has a hard limit of 2GB of its output. While normally
> it's not a problem, some very verbose edge cases make the results.json
> output go past that limit.
>
> This series converts igt_runner's json-c usage to Jansson.
>
>
I haven't been able to review this thoroughly yet, but an initial
comment can be made:
Absolute blockers for this series are having gitlab CI correctly set
up so it builds there (should be just a matter of adding the packages
to the dockerfiles), and having the required libs installed in our
CI. Latter we're able to see fully done by having a successful
premerge on this series.
--
Petri Latvala
prev parent reply other threads:[~2022-08-11 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 13:55 [igt-dev] [PATCH i-g-t 0/3] Use Jansson instead of json-c in igt_runner Ryszard Knop
2022-08-10 13:55 ` [igt-dev] [PATCH i-g-t 1/3] runner: Use Jansson in resultgen instead of json-c Ryszard Knop
2022-08-10 13:55 ` [igt-dev] [PATCH i-g-t 2/3] runner/tests: Fix JSON test data Ryszard Knop
2022-08-10 13:55 ` [igt-dev] [PATCH i-g-t 3/3] runner: Add an on-demand test for large files Ryszard Knop
2022-08-10 15:23 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Use Jansson instead of json-c in igt_runner Patchwork
2022-08-11 9:14 ` Petri Latvala [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=YvTIjlCyxzJft4PF@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ryszard.knop@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.