<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div>Stephane, that's my fault and I apologize.This time, i've not put enough effort before the commit.<br>Instead i've put excessive confidence in the simulator and my previous work in own branch.<br></div><div>I can only commit nightly, so effectively, it can cost a day before I correct my mistakes.<br><br></div>HOWEVER, may I remind you the combinatorial:<br> (spur,v3) x (interpreter,cogit) x (32,64bits) x (mac,win,linux,...) x (squeak,pharo,newspeak)<br>not speaking of ARM, android free bsd etc...<br></div>How do you conceivably expect that a single contributor like me would perform tests for each and every configuration?<br></div><div>You naturally put YOUR build above every other, but to me this has no more value than anyone else bias.<br></div><div><br></div>Performing that bunch of tests is not human, only a bot can do it.<br></div>Isn't it what the Jenkins architecture is all about?<br></div>Incorrect commit are correctly detected and should remain unused.<br>The commiter should be notified, and that was the case.<br></div><div>So what do you want more?<br></div><div>Everyone else duplicating this effort?<br></div><div><br></div><div>Ggit would help managing development with branches, but we are not there currently, so please revise your standards.<br></div><br></div></div><div>You know that I'm not found of the break it first, fix it later strategy.<br></div><div>Though it sometimes happen that I get caught.<br></div><div>Here it sounds like you are not granting to me this right to break things when in the same time this right is totally abused in every day Pharo development...<br></div><div>So despite the fact that you are completely right this time, I'd say that I would have been more inclined to take the lesson I deserved from say Eliot ;)<br></div></div></div></div><br></div>I'm taking too much time writing this when there's probably more trouble with the spur VM currently and that ain't good.<br></div><div>Stephane, I like your energy, and I wish I could use and promote Pharo, but please, keep it positive :)<br></div><div>Tonight, you gave me bad vibrations :(<br><br></div><div>Nicolas<br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-18 22:13 GMT+01:00 stephane ducasse <span dir="ltr"><<a href="mailto:stephane.ducasse@gmail.com" target="_blank">stephane.ducasse@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I wonder why you do not check our builds before pushing a change. Staging changes can make sure that<br>
we control the propagation of errors. And as you know, error = time = money.<br>
This is always difficult for someone to try to understand error that he had no clue from where they come.<br>
<br>
Stef</blockquote></div><br></div>