From: Cyril Hrubis <chrubis@suse.cz>
To: CKI Project <cki-project@redhat.com>
Cc: Linux Stable maillist <stable@vger.kernel.org>,
Jianwen Ji <jiji@redhat.com>, Hangbin Liu <haliu@redhat.com>,
Memory Management <mm-qe@redhat.com>,
Jianlin Shi <jishi@redhat.com>,
LTP Mailing List <ltp@lists.linux.it>,
William Gomeringer <wgomeringer@redhat.com>
Subject: Re: [LTP] ??? FAIL: Test report for kernel 5.4.12-rc1-5c903e1.cki (stable)
Date: Thu, 16 Jan 2020 17:02:44 +0100 [thread overview]
Message-ID: <20200116160244.GC558@rei> (raw)
In-Reply-To: <cki.04B50782AB.76013V5U5A@redhat.com>
Hi!
This looks like max_map_count failure again.
...
<<<test_output>>>
tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s
mem.c:817: INFO: set overcommit_memory to 2
mem.c:817: INFO: set max_map_count to 1024
max_map_count.c:198: PASS: 1024 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 2048
max_map_count.c:198: PASS: 2048 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 4096
max_map_count.c:198: PASS: 4096 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 8192
max_map_count.c:198: PASS: 8192 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 16384
max_map_count.c:198: PASS: 16384 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 32768
max_map_count.c:198: PASS: 32768 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 65536
max_map_count.c:201: FAIL: 65273 map entries in total, but expected 65536 entries
mem.c:817: INFO: set max_map_count to 1024
max_map_count.c:198: PASS: 1024 map entries in total as expected.
...
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2020-01-16 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 6:06 ❌ FAIL: Test report for kernel 5.4.12-rc1-5c903e1.cki (stable) CKI Project
2020-01-16 16:02 ` Cyril Hrubis [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=20200116160244.GC558@rei \
--to=chrubis@suse.cz \
--cc=cki-project@redhat.com \
--cc=haliu@redhat.com \
--cc=jiji@redhat.com \
--cc=jishi@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mm-qe@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wgomeringer@redhat.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;
as well as URLs for NNTP newsgroup(s).