I tried for one hour yesterday to understand the problem :). This
morning my priority was to not lose my code because I noticed the bug a
couple of hours after my commits... Thanks I remembered to save my image
and that the good old fileout in .st is working!
I'll keep trying to reproduce and keep you posted
On 02/04/2016 10:21 AM, stepharo wrote:
Hi guille
Esteban got some problems with MC recently
so it would be good to have a reproducible case.
Stef
Le 4/2/16 10:07, Guille Polito a écrit :
Ok, I am puzzled. I downloaded a new fresh image, in a fresh
directory, worked on something else, committed, and my commit is
completely broken.
Attached screenshot of what monticello shows me.
I'm on debian jessie 64bits. Maybe it has something to do?
On 02/03/2016 03:41 PM, Guille Polito wrote:
Hi all,
I'm finally back, rechecking this issue:
https://pharo.fogbugz.com/f/cases/7241/Object-name-should-best-be-removed
I remade the Slice to load in latest Pharo5 with the new Spur
changes, plus some fixes proposed by Nicolai. I can load the slice
in a new image and everything looks ok. So far so good.
Now, the monkey starts checking the Slice and somehow it cannot load
the Slice due to "dependencies to some classes". Of course, the
slice I submitted does not depend on the packages on the complaint,
and locally it loads well. Moreover, I never had/worked with those
classes, nor they were installed in my system. Even, I have a new
machine which is clean so I cannot believe I have some interference
due to some package cache...
The message of the monkey is here:
https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/26128//artifact/validationReport.html
Did somebody find some similar problem or it is just me? I believe
the problem is on the monkey side, but I have no clue... Maybe
somebody has a better idea.
Thanks!
Guille
