Wow! This is truly science fiction. Cheers, Doru On 20 Jul 2012, at 18:09, Camillo Bruni wrote:
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 debugger!' contents: nil
The serialized stack trace is very limited (generally only 2 contexts) but they are enough to get a decent view on what the variables are
-- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."