On 26 May 2012 02:33, David T. Lewis <[email protected]> wrote: > +1 > > Thanks Igor. >
yeah.. one of the problems, that we're running Pharo image tests on successfull build. But these tests are not including the tests for "optional" components, like OSProcess.. Because if we ship VM with PluginA, PluginB, apparently we should run tests which testing those plugins, to check that they are functional, even if they are not used by default into Pharo image(s). > Dave > > On Sat, May 26, 2012 at 02:13:34AM +0200, Igor Stasenko wrote: >> we should integrate the chdir fix to osprocess >> into jenkins vms >> >> On 25 May 2012 22:17, Sean P. DeNigris <[email protected]> wrote: >> > When OSProcess is integrated, we will have two different concepts of the >> > working directory: >> > ??fsPwd := '/Volumes/Sean''s Universe/sean/.jenkins/jobs/Dynabook/' >> > asFileReference. >> > ??[ FileSystem disk changeDirectory: fsPwd ] on: Exception do: []. >> > ??FileSystem disk workingDirectory = fsPwd. "true" >> > >> > ??ospPwd := '/Volumes/Sean''s >> > Universe/sean/.jenkins/jobs/Dynabook/workspace'. >> > ??OSProcess thisOSProcess chDir: ospPwd. >> > ??FileSystem disk workingDirectory = ospPwd. "false" >> > ??(PipeableOSProcess command: 'pwd') output trimRight = ospPwd "true" >> > >> > -- >> > View this message in context: >> > http://forum.world.st/Working-directory-tp4631865.html >> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. > -- Best regards, Igor Stasenko.
