Can someone help me with this issue 12469 (Sometimes an empty protocol is created)
I tried a dozen times to create a slice for the fix. Every time the slice marks the all classes and methods as changed, even so, I only changed some methods. Now I have finally uploaded a slice with only my changes but.. The Validator chooses an older slice for validation ? ( https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/valid... ) I don't know anymore, what I can do, I despair. Nicolai
I believe Marcus said that the validator takes the highest numbered version. Yours is .2 and Ben's is .3 even though it is older. You can save a .4 one by manually editing the name just before saving. On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess@web.de> wrote:
I tried a dozen times to create a slice for the fix. Every time the slice marks the all classes and methods as changed, even so, I only changed some methods.
Now I have finally uploaded a slice with only my changes but.. The Validator chooses an older slice for validation ? (https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/valid...)
I don't know anymore, what I can do, I despair.
Nicolai
2014-02-01 Sven Van Caekenberghe <sven@stfx.eu>:
I believe Marcus said that the validator takes the highest numbered version. Yours is .2 and Ben's is .3 even though it is older. You can save a .4 one by manually editing the name just before saving.
On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess@web.de> wrote:
I tried a dozen times to create a slice for the fix. Every time the slice marks the all classes and methods as changed, even so, I only changed some methods.
Now I have finally uploaded a slice with only my changes but.. The Validator chooses an older slice for validation ? ( https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/valid... )
I don't know anymore, what I can do, I despair.
Nicolai
I don't know how to do it. If I choose save I get a MCPermissionDenied error. :(
I looked at your slice while integrating some other changes - it looked clean. Are you going to try to rename it or should I give it a try ? On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess@web.de> wrote:
I tried a dozen times to create a slice for the fix. Every time the slice marks the all classes and methods as changed, even so, I only changed some methods.
Now I have finally uploaded a slice with only my changes but.. The Validator chooses an older slice for validation ? (https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/valid...)
I don't know anymore, what I can do, I despair.
Nicolai
Nicolai Hess wrote
Every time the slice marks the all classes and methods as changed,
I've experienced that when viewing changes for a whole slice. If you view the changes for each package individually instead, you should see it is fine. I see Sven has created a new slice for the monkey... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Can-someone-help-me-with-this-issue-12469-Sometimes-an... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 01 Feb 2014, at 23:03, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
Every time the slice marks the all classes and methods as changed,
I've experienced that when viewing changes for a whole slice. If you view the changes for each package individually instead, you should see it is fine.
Yeah, it seems to be a fluke, very confusing though.
I see Sven has created a new slice for the monkey...
And it seemed to have passed.
Thank you. 2014-02-01 Sven Van Caekenberghe <sven@stfx.eu>:
On 01 Feb 2014, at 23:03, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
Every time the slice marks the all classes and methods as changed,
I've experienced that when viewing changes for a whole slice. If you view the changes for each package individually instead, you should see it is fine.
Yeah, it seems to be a fluke, very confusing though.
I see Sven has created a new slice for the monkey...
And it seemed to have passed.
Thank you, Nicolai, for the fix ! On 02 Feb 2014, at 19:12, Nicolai Hess <nicolaihess@web.de> wrote:
Thank you.
2014-02-01 Sven Van Caekenberghe <sven@stfx.eu>:
On 01 Feb 2014, at 23:03, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
Every time the slice marks the all classes and methods as changed,
I've experienced that when viewing changes for a whole slice. If you view the changes for each package individually instead, you should see it is fine.
Yeah, it seems to be a fluke, very confusing though.
I see Sven has created a new slice for the monkey...
And it seemed to have passed.
sorry for this situation. It is not the one we dream about believe me. Stef On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess@web.de> wrote:
I tried a dozen times to create a slice for the fix. Every time the slice marks the all classes and methods as changed, even so, I only changed some methods.
Now I have finally uploaded a slice with only my changes but.. The Validator chooses an older slice for validation ? (https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/valid...)
I don't know anymore, what I can do, I despair.
Nicolai
participants (4)
-
Nicolai Hess -
Pharo4Stef -
Sean P. DeNigris -
Sven Van Caekenberghe