On 08 Jan 2014, at 13:09, Marcus Denker <marcus.denker@inria.fr> wrote:
On 08 Jan 2014, at 11:34, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 08 Jan 2014, at 10:17, Marcus Denker <marcus.denker@inria.fr> wrote:
On 08 Jan 2014, at 10:14, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 08 Jan 2014, at 09:48, Marcus Denker <marcus.denker@inria.fr> wrote:
12377 ZnHTTPSTests.>>testGetPharoVersion fails on Windows slave https://pharo.fogbugz.com/f/cases/12377
And this is just a build server artefact⦠(windows slave firewall problem).
I wonder what to do⦠maybe we could just skip it on windows when running on the build slave ;-)
Marcus
Yes, either that (BTW, is it possible to know you are running on a slave ?)
We could add a check for an environment variable that Jenkins sets.
And then access it with
OSPlatform current environment
right ?
What environment variables are already set by Jenkins (on all platforms) ? Which one should we test for ?
Right now we do not set any special one⦠but we could
There is right now on all slaves: (here with values for win):
OS = win Architecture = 32 TERM = xterm-color LC_ALL = en_US.UTF-8
We can add moreâ¦
Well, it should be something like: JENKINS = ci.inria.fr Then the guard for the unit test could be (OSPlatform current environment at: #JENKINS ifAbsent: [ '' ]) = 'ci.inria.fr' ifTrue: [ ^ self ] to skip the test only on the INRIA CI servers. Maybe CI instead of JENKINS is a more general name.