Hi Clément: On 11 Mar 2014, at 09:58, Clément Bera <bera.clement@gmail.com> wrote:
Yesterday I had this problem that at startup a pharo image has several process running at priority 40. The problem is that my tests (run from command line) trigger #valueWithin:onTimeout: and the protected block (the block calling #valueWithin:onTimeout:) would always timed out for the first test as resuming the watchdog in #valueWithin:onTimeout: allows another runnable process at the same priority as the active process to be run.
I'm not very familiar with Pharo's process framework nor with processes in general so I would like to discuss the problem.
Question 1: Is it a bug ?
Just a brief answer: Processes on the same priority are scheduled cooperatively. So, no, it is not a bug. Only processes of different priority are scheduled preemptively. So, it is âby designâ and the expected behavior (which some parts of the system rely on). Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/