> | well that's what the fuel files are for... > | Can't you run the tests and copy the files to a safe location where > | you can analyze them offline? > > Nope.
seems to be doable: http://sleepycoders.blogspot.fr/2013/03/sharing-travis-ci-generated-files.html > > | Depending on stack traces to debug is definitely history ;) > > I guess I won't be porting Metacello to Pharo3.0 then either... Don't get me wrong, there still are stack traces, but most probably the bug you experience is more hidden. What I am trying to say is that should use the fuel files to debug failing tests instead of spending time deciphering dead text-based stack traces. And exactly in the case you describe theses fuel files can save you a lot of time since you can basically debug the same way you debug a local application. BTW: where do I see which tests fail under travis? clicking on the status badges on the filetree page doesn't lead me to the direct results. In any case I see 4 failing tests on our jenkins build: https://ci.inria.fr/pharo-contribution/job/FileTree/PHARO=30,VERSION=stable,VM=vm/lastCompletedBuild/testReport/ are these the same you have on travis?
