Sven, maybe get the output of otool -l /path/to/lib
and compare the paths to linked libraries to the ones found in the plugin of the failing job. There might be a problem with the location of certain libraries. Or not… :) Cheers, Max On 11.08.2014, at 15:29, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > On 11 Aug 2014, at 15:21, Clément Bera <bera.clem...@gmail.com> wrote: > >> I suspect ContextPart>>#reading, that is a class extension from Xtreams in >> ContextPart to be the reason. >> >> It should now be an extension of Context and not ContextPart. > > Yes, that is something we should fix, I saw that while loading the code in a > fresh 4.0 > > However, that still does not explain why the failing tests pass on my Mac. > Weird. > >> 2014-08-11 14:35 GMT+02:00 Sven Van Caekenberghe <s...@stfx.eu>: >> It seems that the Xtreams build has been failing since june 30th for 4.0 and >> not 3.0: >> >> https://ci.inria.fr/pharo-contribution/job/Xtreams/ >> >> From the changes to 4.0 around that period I can't immediately see something >> obvious: >> >> https://github.com/pharo-project/pharo-core/commits/4.0?page=4 >> >> I just tried loading Xtreams in on my machine and all tests succeed. >> >> All errors on Jenkins seem to be related to primitives not being found in >> libCrypto: >> >> Error Message >> >> External module not found >> >> Stacktrace >> >> XTLibCryptoHash(Object)>>error: >> XTLibCryptoHash(Object)>>externalCallFailed >> XTLibCryptoHash>>EVP_MD_CTX_init: >> XTLibCryptoHash>>initialize >> XTHash class>>new >> XTHashTest>>testMD5 >> XTHashTest(TestCase)>>performTest >> >> So, is it possible there was a change in the VM ? >> >> The Xtreams source code itself has not been changed for months. >> >> Sven >> >> >> > >
