Hi, One thing we definitely need to do is to commit the Change first to the Opal repository. This will trigger a build and in a second step this: https://ci.inria.fr/rmod/job/OpalRegression/ <https://ci.inria.fr/rmod/job/OpalRegression/> This recompiled the whole image and then runs all tests. It is broken right now due to timeout, but that is from the >500 failing dictionary tests, I think. So the build now in progress should be green again (I hope). Marcus
On 18 Aug 2015, at 11:12, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi guys,
In the quest to remove the old compiler from the map, we need to replace the references to ParseNode. Thing is that right now, the bytecode encoders opal compiler uses are subclasses of this ParseNode guy.
To solve this, we are integrating this in several steps:
- Integrate a copy of the encoders that are not subclass of ParseNode Already integrated, with no real side effects on the system. https://pharo.fogbugz.com/f/cases/16199/Introduce-OpalEncoders <https://pharo.fogbugz.com/f/cases/16199/Introduce-OpalEncoders>
- Make the system use the new encoders This change is critical as if the new encoders do not do the job, you may be unable to execute code again ^^. We need help in testing this. I ran the full tests of the image found some bugs but they do not look related. But, if you know some case, or you use the compiler in a special way, It would be good if you load the slice and test please :) https://pharo.fogbugz.com/f/cases/16250/Activate-new-Encoders <https://pharo.fogbugz.com/f/cases/16250/Activate-new-Encoders>
- A final step will be to rename the OpalEncoders* to Encoder* again (removing the Opal prefix) to be compatible with Squeak. But this one is rather easy and may have no risk.
Guille