On Fri, Mar 31, 2017 at 7:17 AM, Petr Fischer petr.fischer@me.com wrote:
On Fri, Feb 24, 2017 at 11:57 AM, Holger Freyther holger@freyther.de
wrote:
Hi!
Now, this heartbeat threaded VM is the recommended in the README
file, and we see that OSSubprocess generates the exact issue stated. The main problem remains for the moment since Pharo's default download includes not this VM but the itimer one. I talked with Esteban about it and he was aware of these two VM flavours, and the reason why we are using the itimer one is the need to deploy those permission files in /etc, which makes installation a bit less automatic.
It is not a matter of configuration, e.g. more infrastructure is
migrated into docker containers (I run the CI with docker containers) and even as root inside the container you might not be allowed to use realtime priority. And you might not be able to influence how your container is being executed.
holger
PS: Have you seen the fix David Lewis made to the UnixProcess plugin,
maybe it already helps with your bug as well?
If these two commits work out, the threaded VM may become a viable default option... https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/
32f321583c69ca27e61ffaff6decc2a3e4b6ca5e
5418a415e9297f601f6d57ee732fd7fd942da08c
cheers -ben
Are these commits immediatelly available in pharo-vm GitHub repository, or I need to compile directly from opensmalltalk-vm?
I'm not clear on the process Esteban uses to keep pharo-vm up to date with opensmalltalk-vm, but I believe its in. Its easy to test. Just download latest VM and run without the limits conf.
Is it really safe to run VM with normal priority heartbeat?
Of course user testing is required, but considering how Linux operates with dynamic thread priorities I believe it is safe.
cheers -ben