On 7 July 2012 15:37, David T. Lewis <lewis@mail.msen.com> wrote:
On Fri, Jul 06, 2012 at 08:48:08PM -0700, Sean P. DeNigris wrote:
David T. Lewis wrote
There might be some plugin version issues too. ... OSProcess accessor osppModuleVersionString ==> '4.3.3 Cog'
My failing image was running on the latest Jit Cocoa Cog VM from Jenkins and had the same outdated plugin
It's not necessarily out of date, it's just a different version from my "trunk" OSProcessPlugin. I use the versionString to keep track of the change level. '4.3.3' means that it came from one of the files in the oscog branch, but I'm not sure which one.
I should also say that is it entirely possible that there are timing-related bugs in the OSProcess test suite that get exposed by Cog, which is much faster than an interpreter VM. I guess the way to find out would be to build a Cog VM with the "trunk" OSPP and see if the problems go away. I cannot try this right now but I'll look into it in a couple of days if no one else gets to it first (we have a lot of new people who know how to build VMs these days, so someone should give it a try, hint, hint ;)
yeah.. it is a matter of changing the package version in configurationofcog
Dave
-- Best regards, Igor Stasenko.