Thanks Max!

So you finally implemented the prunning? �If true, what about opening an issue to prune the stack in Pharo when:

1) we export from a debugger
2) the jenkins CI saves the failed test�

?

Thanks!!!


On Thu, Jan 23, 2014 at 6:47 PM, Max Leske <maxleske@gmail.com> wrote:
Hi guys

So apparently somehow the problems we�ve had with the builds are now gone. I�ve reenabled failure e-mails for failed / broken builds.

Here�s what�s on my list and what I will work on (in that order):
- fix last failing test for 3.0
- prepare compatibility packages for Squeak4.5 (see https://code.google.com/p/fuel/issues/detail?id=204&colspec=ID%20Type%20Status%20Priority%20Milestone%20Component%20Owner%20Summary)
- implement truncation (see https://code.google.com/p/fuel/issues/detail?id=203&colspec=ID%20Type%20Status%20Priority%20Milestone%20Component%20Owner%20Summary)

Cheers,
Max



--
Mariano
http://marianopeck.wordpress.com