Access level:
System for which access is needed: test-macstadium-macos1014-x64-3
I'm trying to explicitly set max user processes for a system test which fails on linux if < 1500 or so (https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1851). The command does not work on osx - there are no error messages, but ulimit -u returns the original value after running the command to modify it.
Max user processes is modified as expected on a local Mac laptop - I would like to check the ulimit behaviour on a Jenkins test machine.
Access granted to [email protected] ... The machine has been marked offline in jenkins
FYI for future reference if you remove the space before the x in the main message i.e. use [x] instead of [ x] then it'll show up as a correctly checked tickbox - looks a bit nicer :-)
So - ulimit -u does get ignored on the Jenkins test machine with eithe rthe default shell or the gnu bash shell. The gnu bash shell also gives an error message.
Default shell:
test-macstadium-macos1014-x64-3:~ jenkins$ launchctl limit
cpu unlimited unlimited
filesize unlimited unlimited
data unlimited unlimited
stack 8388608 67104768
core 0 unlimited
rss unlimited unlimited
memlock unlimited unlimited
maxproc 1418 2128
maxfiles 256 unlimited
test-macstadium-macos1014-x64-3:~ jenkins$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 1418
virtual memory (kbytes, -v) unlimited
test-macstadium-macos1014-x64-3:~ jenkins$ ulimit -u 2048
test-macstadium-macos1014-x64-3:~ jenkins$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 1418
virtual memory (kbytes, -v) unlimited
With /usr/local/bin/bash
bash-5.0$ launchctl limit
cpu unlimited unlimited
filesize unlimited unlimited
data unlimited unlimited
stack 8388608 67104768
core 0 unlimited
rss unlimited unlimited
memlock unlimited unlimited
maxproc 1418 2128
maxfiles 256 unlimited
bash-5.0$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 1418
virtual memory (kbytes, -v) unlimited
bash-5.0$ ulimit -u 2048
bash: ulimit: max user processes: cannot modify limit: Operation not permitted
bash-5.0$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 1418
virtual memory (kbytes, -v) unlimited
The command was run successfully on a local Mac laptop (running 10.15.7), though I don't know if that user has priveleges the Jenkins user does not.
The test which fails on Linux with a low-ish max user processes does not also fail on osx - so we can just not run the command on osx or run it and let it fail,
I think I prefer not running it with an appropriate comment in the code.
Unless there's more investigation required (and a suggestion as to what investigation to do), I no longer need the machine access.