From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [igt-dev] ✓ Fi.CI.IGT: success for series starting with [1/4] lib/igt_kmod: simplify check for loaded module
Date: Mon, 8 Apr 2019 14:56:52 +0300 [thread overview]
Message-ID: <20190408115652.GD22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190405192947.28297.56171@emeril.freedesktop.org>
On Fri, Apr 05, 2019 at 07:29:47PM +0000, Patchwork wrote:
> * igt@gem_exec_parallel@default-fds:
> - shard-hsw: PASS -> SKIP [fdo#109271] +3
Now that patch 4 got merged, we have the -fds tests skipping on hsw
and icl shards, due to EPERM from setrlimit. The code attempts to set
RLIMIT_NOFILE to /proc/sys/fs/file-max when the documented limit for
RLIMIT_NOFILE is /proc/sys/fs/nr_open.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-08 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 22:39 [igt-dev] [PATCH 1/4] lib/igt_kmod: simplify check for loaded module Lucas De Marchi
2019-04-04 22:39 ` [igt-dev] [PATCH 2/4] gem_exec_parallel: do not special case the default Lucas De Marchi
2019-04-04 22:57 ` Chris Wilson
2019-04-04 22:39 ` [igt-dev] [PATCH 3/4] lib: add igt_allow_unlimited_files() Lucas De Marchi
2019-04-04 23:00 ` Chris Wilson
2019-04-04 22:39 ` [igt-dev] [PATCH 4/4] gem_exec_parallel: allow unlimited open files Lucas De Marchi
2019-04-04 23:01 ` Chris Wilson
2019-04-04 23:19 ` [igt-dev] [PATCH 1/4] lib/igt_kmod: simplify check for loaded module Chris Wilson
2019-04-05 16:33 ` Lucas De Marchi
2019-04-04 23:39 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [1/4] " Patchwork
2019-04-05 19:29 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-04-08 11:56 ` Petri Latvala [this message]
2019-04-30 17:09 ` Lucas De Marchi
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=20190408115652.GD22949@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@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