<div dir="ltr"><div><div><div><div><div>Ah, no, the build is still failing!<br>Since <a href="http://build.squeak.org/job/SqueakTrunk/834/">http://build.squeak.org/job/SqueakTrunk/834/</a> it's another problem with:<br>
<pre>MCClassDefinition>>createClass</pre>I encountered this one while updating some of my old trunk images.<br>The definition changed in Monticello-cwp.589:<br>
+ inEnvironment: (CurrentEnvironment signal ifNil: [superClass environment])<br>
- inEnvironment: (EnvironmentRequest signal ifNil: [superClass environment])<br><br>But there is no EnvironmentRequest anymore when loading this definition, so we signal nil, and the load fails.<br>
</div><div>We would have expected this, it's just be renamed in:<br></div><div><br>Environments-cwp.47<br>
Time: 22 March 2014, 7:53:17.666 pm<br><div id=":2jl" class="">
Rename <span class="">EnvironmentRequest</span> to CurrentEnvironment and use it to implement <span class="">Environment</span> class>>current.<br><br></div>To be safe, the rename should have been performed in two stages:<br>
</div><div>1) create the new class and migrate customers from the old to the new one.<br></div><div>2) remove the old one<br></div><div>It would thus have required two updates.mcm and not a single one<br>(MC lacks a semantic #rename: so it does not work like in-image-tools)<br>
</div><div></div><div>Unfortunately, update-cwp.48 did perform the two operations at once...<br><br></div><div>Curiously, if I take an artefact from build server and update, the upgrade is then processing fine... Don't ask why.<br>
</div>Since no one complained, I told to myself that it was me not following the standard process, I patched my images manually and restarted the upgrade.<br>But I now see that it's not just me, there is a CI machine too using Squeak trunk (anyone else???)<br>
<br></div>I have to cheat again with mcm surgery:<br></div>- publish an Environments-nice.47 that adds the CurrentEnvironment, but not removes EnvironmentRequest<br></div>- patch update-cwp.48 to point to Environments-nice.47 rather than Environments-cwp.47<br>
</div><div>That'll be in a few minutes...<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-24 22:58 GMT+02:00 Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2014-05-24 22:36 GMT+02:00 Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>></span>:<div>
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hi,<br></div>it seems that most of the builds are red for 2 months.<br>
</div>I checked the last artefact for squeak trunk:<br><a href="http://build.squeak.org/job/SqueakTrunk/853/" target="_blank">http://build.squeak.org/job/SqueakTrunk/853/</a><br>
<br></div>It's still blocked with the [Warning signal: 'About to <span>serialize</span> an empty package.']<br></div>With this warning, a test never time out (I don't know why exactly, but it seems that theProcess monitored by the timeout watchdog is already suspended by the Warning)<br>
As a result, the tests do never complete and are aborted after 20 minutes...<br><br></div>Chris has fixed the problem since, but it seems that the CI does not upload latest trunk.<br></div>Why?<br></div>It seems to be the same problem as the TestRunner: updating triggers the same [Warning signal: 'About to <span>serialize</span> an empty package.']<br>
</div>Ah Chris, it's irony that it's you who precisely keep on fighting modal UI ;)<br><br></div>Now the question: how do we escape from this situation?<br></div>Shall I cheat and modify the update that is blocking?<br>
<div><div><br><br></div></div></div></blockquote></div></div><div>So I decided to cheat:<br></div><div>I brought update-eem.279 to the surgery block and reverted CommandLine-fbs.3 -> CommandLine-fbs.2<br>CommandLine-fbs.3 tried to be smart and workaround the Warning problem, but before it had a chance to load, it precisely triggered this Warning!!!<br>
</div><div>Since this update is also bringing Chris fix, let's defer CommandLine-fbs.3 to next update (eem-280) and cross fingers...<br></div></div><br></div></div>
</blockquote></div><br></div>