I love that scenario :) This is great that powerful tools let us imagine and build solutions that would not be possible before. Power to imagination⦠It fits perfectly with one of the motto of Pharo: Inventing the future. On Jul 20, 2012, at 6:09 PM, 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