[Pharo 7.0-dev] Build #899: 20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Pharo 7.0-dev] Build #899: 20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class

ci-pharo-ci-jenkins2
There is a new Pharo build available!
       
The status of the build #899 was: FAILURE.

The Pull Request #1356 was integrated: "20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class"
Pull request url: https://github.com/pharo-project/pharo/pull/1356

Issue Url: https://pharo.fogbugz.com/f/cases/20322
Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/899/
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 7.0-dev] Build #899: 20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class

Sean P. DeNigris
Administrator
ci-pharo-ci-jenkins2 wrote
> …name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class…

Hooray! One less newbie* gotcha :)

* Although I had fallen into this trap a few times even when not so new ;)



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Cheers,
Sean