Ben can you open a bug entry because we should really try your change now. And probably remove after the Experimental from the name. Stef Le 1/9/15 19:15, Ben Coman a écrit :
Do you want to try a post-load... Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler
which fixes the "super fast delay" on virtual machines reported here... http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873
Its named "experimental" only since it was integrated just before Pharo 4 release and did not have wide spread community testing, but its complete and working. There is some further overall streamlining of the DelayScheduler hierarchy I'd like to do later, but it would be good to give this one a run as the default for a while to see how it impacts the issue. (It would be good to get rough "CIAndRule: Timeout" before and after statistics.)
btw, is that CI error indicating it times out after one hour? Are there any other timestamps present in the log that indicate if 1 hour really passed?
cheers -ben
On Tue, Sep 1, 2015 at 11:23 PM, Peter Uhnák <i.uhnak@gmail.com> wrote:
This is different issue, same problem https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12442//artifact/vali...
I'm blaming CI.
On Tue, Sep 1, 2015 at 5:22 PM, Peter Uhnák <i.uhnak@gmail.com> wrote:
Hi,
CI is failing on
a CIAndRule: Timeout (after 0:01:00:00) occured
https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12440//artifact/vali...
Because the validation before it was ok and I just changed a protocol. Is this my problem? Is this issue in CI?
Thanks, Peter