[Pharo-project] fuelized test failures
Mariano Martinez Peck
marianopeck at gmail.com
Tue Jul 24 14:54:04 EDT 2012
THere is something I don't understand. If I see:
it seems it is independent of a particular build. What does it mean? that
we only have the .fuel of the last build? if this is the case, then it is
not very helpful at all.
On Tue, Jul 24, 2012 at 7:57 PM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:
> On Tue, Jul 24, 2012 at 4:35 PM, Camillo Bruni <camillobruni at gmail.com>wrote:
>> On 2012-07-24, at 16:29, Mariano Martinez Peck wrote:
>> > On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni <camillobruni at gmail.com
>> >> From now on all the test-failures are serialized on the build server.
>> >> This allows us to quickly find the cause of a failing test:
>> >> - download the .fuel file for the failing test
>> >> - materialize the .fuel in the image and debug the code
>> >> | aContext |
>> >> aContext := FLMaterializer materializeFromFileNamed:
>> >> 'PharoDebug.fuel'.
>> >> Debugger openContext: aContext label: 'This is the new
>> >> contents: nil
>> > does it really work for you?? I am trying to materialize, for example,
>> > and I get:
>> > FLClassNotFound: Materialization error. Class named #HDTestReport not
>> > That happens because during serialization the graph somehow reached the
>> > class HDTestReport (probably a sender at some point in the stack). But
>> > when materializing, such class is not present. So...is there in the
>> > workspace an image with the jenkins stuff?
>> > Anyway, the idea was to include this directly in Pharo, wasn't it?
>> I suggest you use the image in the same directory, cause we install
>> some Hudson tools (which IMO should be included by default).
> +1 I remember there was an issue for that...I tried to find it but I
> Do you remember?
>> I don't
>> really like that we have to load stuff for running the test, meaning
>> that this might affect the outcome of the results...
>> So for now either take the following image:
> ok, thanks!
>> or manually install the hudson tools:
>> "Load Hudson Build Tools"
>> Gofer new
>> url: 'http://ss3.gemstone.com/ss/CISupport';
>> package: 'HudsonBuildTools20';
>> then everything should work I think.
> yes, it works. And it is really cool :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev