https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113085
Bug ID: 113085
Summary: New test case libgomp.c/alloc-pinned-1.c from
r14-6499-g348874f0baac0f fails
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:348874f0baac0f22c98ab11abbfa65fd172f6bdd, r14-6499-g348874f0baac0f
make -k check-target-libgomp RUNTESTFLAGS="c.exp=libgomp.c/alloc-pinned-1.c"
FAIL: libgomp.c/alloc-pinned-1.c execution test
# of expected passes 1
# of unexpected failures 1
commit 348874f0baac0f22c98ab11abbfa65fd172f6bdd (HEAD)
Author: Andrew Stubbs <a...@codesourcery.com>
Date: Tue Jan 4 12:22:01 2022 +0000
libgomp: basic pinned memory on Linux
spawn [open ...]
unsufficient lockable memory; please increase ulimit
FAIL: libgomp.c/alloc-pinned-1.c execution test
"Unsufficient"? Is that a typo?
In any case I don't think a test should require an unusual ulimit setting.
seurer@ltcden2-lp1:~/gcc/git/build/gcc-test$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 3909068
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 3909068
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
