I got the problem, ZeroConf scripts use the find command and there was a PATH problem on the slave running your job. It used the windows find command and not the mingw one. It is now fixed and your job is now better ... but not yet green. It misses the test XML output file. It may be to a wrong regexp OSWindows.* for your test packages.
Regards, Christophe. Le 20 sept. 2013 à 09:55, Christophe Demarey a écrit : > Hello, > > To see what happens, you need to first click on a specific build in the > matrix job, then you can browse a particular build and is console output. > ex: > https://ci.inria.fr/pharo-contribution/job/OSWindows/12/PHARO=30,VERSION=stable,VM=vm,Windows%20Slaves%20only=win/console > Here the problem seems to come from the definition of the "Windows Slaves > label" that generates a directory with this name. > > I would rather put a fixed value and replace > export JOB_NAME=`dirname $JOB_NAME` > by > export JOB_NAME=OSWindows > > I did some changes and triggered a new build manually. > But it also failed. It looks like the zeroConf script is broken on windows. > We will take a look at it. > > Regards, > Christophe. > > > Le 20 sept. 2013 à 09:31, Torsten Bergmann a écrit : > >> I created a CI project for "OS-Windows" according to the written >> steps on the creation page. >> >> It failed - and I checked the CI scripts. Since it was named "OS-Windows" >> and there was a $JOB_NAME variable in the script I better changed the script >> to use "OSWindow" for image name, ... (to avoid problems with character "-". >> >> https://ci.inria.fr/pharo-contribution/job/OSWindows/ >> >> Still it fails - telling me something about "no workspace". I now renamed >> it to "OSWindows" and situation is the same. Note that the tests should >> run only on Pharo 3.0 with a windows slave - that is how the configuration >> is currently setup. >> >> There is a ConfigurationOfOSWindows with #stable and #development, so >> >> ConfigurationOfOSWindows project version: #development >> ConfigurationOfOSWindows project version: #stable >> >> return something to load. Also the repo is correctly setup. >> >> Dont know what's missing - maybe someone with access can have a look. >> >> Thanks >> T. >> >> >
smime.p7s
Description: S/MIME cryptographic signature
